Keep your client projects organized.
Build clear project boundaries instead of maintaining scattered servers and password lists for every client.
What matters for your application
Teams building APIs for several customers
Separate resources and secrets between customers.
Agencies delivering mobile apps and admin consoles
Record domain ownership, access handover and maintenance responsibilities.
Organizing backend configuration for inherited projects
Avoid promising unavailable services or guarantees.
Where it fits
Build clear project boundaries instead of maintaining scattered servers and password lists for every client. Separate your development workflow from customer ownership and operational responsibilities.
- Teams building APIs for several customers
- Agencies delivering mobile apps and admin consoles
- Organizing backend configuration for inherited projects
Its place in your application
Model client applications as separate projects, with service-specific environment values and domains. Give clients a clear scope for releases, access handover and maintenance.
Before you begin
Choose services around the actual needs of your application. Include these points in your development and release plan.
- Separate resources and secrets between customers.
- Record domain ownership, access handover and maintenance responsibilities.
- Avoid promising unavailable services or guarantees.
Common questions
Are team invitations and customer handover available?
The organization permission model exists, while invitation and handover interfaces are still being developed. This page describes the intended workflow without selling unfinished capabilities.
Can I provision a live resource now?
Not yet. New registration and customer allocation are closed on the live site. Product guides are published; local development simulation does not create real services.