feat: tenant registry and tenant-scoped requests (multi-tenant foundation, part 1) #7

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

The Studio serves one company per instance. The target is one instance shared by several tenants, logically separated.

First part of the foundation:

  • an instance PostgreSQL database for administrative data, with SQL migrations;
  • the tenant registry (tenants, memberships with roles), on @quatrain/tenancy;
  • the tenant of a request read from the path (/t/<tenant>/...) and checked against the membership in the database, never taken from identity provider claims;
  • roles inside a tenant taken from the membership;
  • a command to create a tenant and add a member.

The instance keeps working without a database, as today, until the following parts land.

Next parts (separate issues): local accounts and a generic OpenID Connect client in place of the current provider; per-tenant resources (git repository, object storage, AI provider) in place of process-wide registries; tenant-owned data with row isolation.

The Studio serves one company per instance. The target is one instance shared by several tenants, logically separated. First part of the foundation: - an instance PostgreSQL database for administrative data, with SQL migrations; - the tenant registry (tenants, memberships with roles), on `@quatrain/tenancy`; - the tenant of a request read from the path (`/t/<tenant>/...`) and checked against the membership in the database, never taken from identity provider claims; - roles inside a tenant taken from the membership; - a command to create a tenant and add a member. The instance keeps working without a database, as today, until the following parts land. Next parts (separate issues): local accounts and a generic OpenID Connect client in place of the current provider; per-tenant resources (git repository, object storage, AI provider) in place of process-wide registries; tenant-owned data with row isolation.
Sign in to join this conversation.
No labels
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
modaka/studio#7
No description provided.