Workspaces
The top-level container for your projects and the unit of billing.
A workspace is the outermost organisational unit in Appentic. Everything you create (projects, services, databases, caches, background jobs) lives inside exactly one workspace. Workspaces are also the billing boundary: each one receives its own invoices and usage reports, so they line up neatly with how most teams already think about cost ownership.
When to use multiple workspaces
Most teams start with a single workspace and never need another one. You'll want more than one in a few specific cases:
- Separate billing. Different clients, business units, or side projects that each need their own invoice.
- Environment isolation. A personal workspace for experiments and a work workspace for production, so nothing can accidentally leak between them.
- Agency setups. One workspace per client, each invoiced separately, each with only the client's own team as members.
If you only need to separate staging from production and don't mind them sharing members and billing, you can keep them in the same workspace under different projects instead. That's usually the lower-friction option.
Members and access
Each workspace has its own member list. Anyone you invite can see and operate every project and service in that workspace. There's intentionally no role system within a workspace: if you trust someone with one production service, you trust them with the rest. If you need to limit who can touch what, split into separate workspaces.
Switching workspaces
The workspace switcher lives in the top-left of the dashboard. Switching is instant and updates every tab in your browser, so you don't end up accidentally shipping to the wrong environment.