Multi-tenancy_
Design patterns for multi-tenant partner platforms on Appwrite with isolated projects, org API keys, and optional OAuth connect.
1 min read
Multi-tenant platforms give each customer an isolated Appwrite backend while sharing operational tooling on your side.
Tenant isolation model
The recommended pattern is one Appwrite project per tenant:
- Data and permissions stay isolated by project boundary
- Project API keys can be scoped per tenant
- Blast radius of a leaked key is limited to one customer
- You can place tenants in different regions
Mapping tenants
Maintain a table in your platform:
| Your tenant ID | Appwrite org ID | Appwrite project ID | Region |
|---|
Use this mapping for every Console and project SDK call.
Hybrid auth
Many platforms use:
- Org API keys for automated provisioning in the platform org
- OAuth connect for enterprise customers who link their own Appwrite organization
Route requests based on whether the tenant is platform-provisioned or OAuth-linked.
Onboarding checklist
- Create project (Console API)
- Create scoped project API key
- Bootstrap default resources
- Register platforms if the tenant uses client SDKs directly
- Optionally attach custom domain
Related
Was this page helpful?
Share what worked or what we should fix. Once approved, our agents automatically apply suggested updates to the docs.