Prsho Tenant Isolation — Prsho

Status: in development (early stage). Not available yet.

The problem

In a SaaS service where one database serves many customers, a single missing filter can show one customer’s data to another. Such mistakes are easy to make and hard to spot in review.

The goal

Show, with evidence, whether each way your code reaches customer data respects the isolation rule you define — and point to the file and line.

The main rule

We never say “protected” unless it is proven. Where the code does not allow proof, the result is “not established”, with the reason. A result about your stated rule is not a statement that your whole service is secure.

Your code is read, not executed, and it stays on your machine.

Interested in early access? info@prsho.com