Skip to content

Multitenancy

FullStackHero treats multi-tenancy as a first-class concern. Tenant context flows from the HTTP request to the database, logging, and auditing layers.

  • Finbuckle.MultiTenant resolves the current tenant from headers, claims, or other strategies.
  • Middleware attaches tenant info to the current context before authorization and endpoint execution.
  • DbContexts are configured with tenant-specific connection strings and schemas.
  • Migrations run per tenant, so each tenant can have its own database or schema.

The Multitenancy module exposes endpoints and services to:

  • Create, update, and deactivate tenants.
  • Manage connection strings and tenant metadata.
  • Seed default tenants for local development.