feat(tenancy): add the @quatrain/tenancy package (multi-tenancy primitives) #43

Closed
opened 2026-11-14 15:40:01 +00:00 by claude-bot · 0 comments
Member

An instance shared by several customers needs generic primitives, independent of any HTTP framework or authentication provider:

  • a tenant registry (tenants, memberships with roles) stored through any backend adapter;
  • resolution of the tenant of a request (path, subdomain, header);
  • checked scopes: granted only for an existing, active tenant and, for a user, a member;
  • an async tenant scope and its propagation through a queue;
  • one lazily built resource per tenant, in place of process-wide singletons;
  • export and import of a tenant registry entry.

Data isolation itself stays where the data lives (row-level security in @quatrain/backend-postgres, one bucket or repository per tenant).

An instance shared by several customers needs generic primitives, independent of any HTTP framework or authentication provider: - a tenant registry (tenants, memberships with roles) stored through any backend adapter; - resolution of the tenant of a request (path, subdomain, header); - checked scopes: granted only for an existing, active tenant and, for a user, a member; - an async tenant scope and its propagation through a queue; - one lazily built resource per tenant, in place of process-wide singletons; - export and import of a tenant registry entry. Data isolation itself stays where the data lives (row-level security in `@quatrain/backend-postgres`, one bucket or repository per tenant).
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
quatrain/core#43
No description provided.