Workspaces
Workspaces are the top-level container for apps, domains, and billing scope. Use them to separate personal projects, staging environments, or client work.
What belongs to a workspace#
Apps and custom domains belong to a workspace. When you switch the active workspace in the dashboard, app lists, deployment history, and domain management all follow that scope.
Workspace creator and billing owner#
The person who creates a workspace becomes its initial owner and is the billing owner by default. Billing state, runtime affordability checks, and build usage are all anchored to that workspace billing owner.
Account audit#
Workspace owners can review account audit events from the dashboard. The audit feed includes app changes, manual deploy actions, resource updates, domain changes, and workspace lifecycle events across workspaces they own.
Creating a workspace#
Create a workspace from the dashboard before deploying if you want to keep projects isolated. Shiprr also creates a default personal workspace during initial account provisioning.
Deleting a workspace#
Workspace owners can delete an empty workspace from dashboard settings. All apps in the workspace must be deleted first, and your account must keep at least one other workspace.
Deleting a workspace removes the workspace record, custom domains, workspace-scoped access records, and workspace deployment history. Billing records, wallet entries, and usage history needed for account records are retained.
How to organize workspaces#
- Personal — Side projects and experiments.
- Business — Production and staging apps for one company.
- Client — Separate billing and domains for each customer.