Database per organization
Each organization receives a dedicated Postgres database instead of sharing customer rows in one application table.
Tenant isolation
Keep each organization’s operational data behind a dedicated database boundary.
Relpin gives every organization a dedicated Postgres database. Trusted runtime context selects the organization and environment before schema-qualified server-side queries run.
assignments · dev 12 columns · 5 rows
| Employee | Project | Status | Alloc |
|---|---|---|---|
| Mina Alvarez | Northwind Rollout | ACTIVE | 40% |
| Jonah Kim | Atlas Migration | ACTIVE | 75% |
| Priya Nwosu | Northwind Rollout | PLANNED | 30% |
| Lena Richter | Mercury Support | BLOCKED | 55% |
server-side SQL · statement + lock timeouts on every transaction
The isolation problem
A tenant ID in a browser request is not a data boundary.
Authentication identifies a user. Authorization limits permitted actions. Tenant isolation separately ensures that runtime work reaches only the organization and environment selected by trusted server-side context.
Isolation layers
Separate organization data before application code reaches it.
Relpin combines a dedicated organization database, explicit environment scope, and governed server-side access.
Environment-scoped schemas
DEV, TEST, and PROD use explicit schemas inside the organization database by default, with every query qualified to the selected environment.
Trusted tenant context
The runtime resolves organization and environment scope on the server before data access, rather than accepting them from untrusted browser headers.
Runtime path
Resolve scope, qualify access, then execute.
The isolation path stays explicit from the authenticated organization context to the final database statement.
- 01
Resolve the organization
Relpin verifies the session and organization membership at the trusted dispatch boundary before runtime code receives context.
- 02
Select the environment
The runtime binds the request to DEV, TEST, or PROD and applies the corresponding schema and operational limits.
- 03
Execute server-side
Queries use schema-qualified identifiers and parameterized values against the resolved organization database.
Isolation evidence
Dedicated Postgres per organization
Explicit DEV/TEST/PROD scope
Schema-qualified server-side SQL
Trusted runtime identity context
Isolation questions
How Relpin separates tenant data and environment scope.
Is authentication the same as tenant isolation?
No. Authentication proves identity and authorization checks permissions. Tenant isolation separately constrains which organization database and environment schema runtime work can reach.
Does every environment receive a separate database?
Not by default. Each organization receives a dedicated database, while DEV, TEST, and PROD are separated by explicit schemas. Database-per-environment is an enterprise isolation option, not the default claim.
Can application code select another organization by changing a header?
No. The trusted dispatch boundary strips untrusted Relpin context headers and supplies verified organization, user, and environment context to the runtime.
Isolation before application logic
Build internal tools on an organization-specific data boundary.
Keep tenant routing, environment scope, and database access on one governed server-side path.
Open beta · No SLA