ormDB for Multi-Tenant Platforms
ormDB provides database-level multi-tenant isolation through row-level security policies enforced on every query. Combined with safe migrations (A-D grading) for shared schemas and query budgets to prevent noisy-neighbor problems, ormDB is purpose-built for multi-tenant platforms.
The multi-tenancy challenge
Multi-tenant platforms share database infrastructure across tenants. The two critical requirements are: tenant data must never leak, and one tenant must never impact another’s performance.
Traditional approaches rely on application-level WHERE clauses for isolation — a single missed filter means a data breach. See how this compares to PostgreSQL’s RLS approach. And without query budgets, a single heavy tenant can degrade performance for everyone.
ormDB’s approach
ormDB is a relational database engine that enforces multi-tenancy at the database level. Row-level security policies are part of the schema, not your application code. Every query — including graph fetches across relations — automatically respects tenant boundaries.
Query budgets prevent noisy-neighbor problems. See the performance optimization guide for details. Set limits on max depth, fanout, total rows, and execution time per query. No tenant can run a query that impacts the shared infrastructure.
Safe migrations with A-D grading ensure schema changes to the shared database never cause unexpected downtime. You know exactly what a migration will do before you run it.
Frequently Asked Questions
How does ormDB isolate tenant data?
ormDB's row-level security policies are enforced at the database level, not the application level. Every query automatically filters by tenant context, making data leaks between tenants structurally impossible.
Can ormDB handle thousands of tenants?
Yes. ormDB uses a shared-schema multi-tenant model with row-level security. There's no per-tenant database overhead. Query budgets prevent any single tenant from consuming excessive resources.