Workspaces

Share a credit pool and apps across your team. Workspaces are pooled-billing teams with member roles and shared usage attribution.

Workspaces require the Business plan. Members can be on any plan, they draw from the workspace pool, not their personal balance.

What a Workspace Is

A workspace is a shared entity that owns apps, holds a single credit balance, and lists multiple member users. When someone in the workspace generates code or deploys, the cost comes out of the workspace pool, not their personal allocation.

One billing entity for the whole team - predictable cost.
Apps belong to the workspace, not individual creators.
Per-action attribution in the credit transaction history shows who used what.
Unlimited members, no per-seat fees.

Members & Roles

Each workspace has an owner and a set of members. Roles control who can manage billing and team membership.

Role	Permissions
Owner	Full control: manage billing, invite/remove members, transfer apps, delete workspace.
Admin	Invite/remove members and manage apps. Cannot change billing or delete the workspace.
Member	Create, edit, and deploy apps. Draws from the workspace credit pool.

Shared Credit Pool

Business workspaces share a single 5,000-credit monthly allocation across all members. There are no per-member sub-allocations, the first action of the month draws from the same pool as the last.

Monthly allocation	5,000 credits (Business)
Rollover cap	10,000 credits (carries over for one cycle)
Top-up packs	Purchasable by the workspace owner - never expire
Attribution	Every deduction logs the acting member for visibility
AI proxy charges	Billed to the workspace pool, not end users

See the Credits documentation for per-action costs and how rollover works at the cycle boundary.

Creating a Workspace

Upgrade to Business

Workspaces require the Business plan on the workspace owner's account. Members can be on any plan; they draw from the pool when working in the workspace context.

Create the workspace

From the team settings page, click Create Workspace, give it a name, and confirm. The workspace pool is initialized with your Business credit allocation.

Invite members

Add members by email. They receive an invite link and join with the role you assign - Admin or Member.

Optional - add an SSO domain

For larger teams, configure an SSO domain so anyone signing in with a matching email is auto-joined.

Switching Contexts

A user can be a member of multiple workspaces and still have a personal account. The active context is shown in the navigation bar and determines which credit pool is charged.

Personal context uses your personal credit balance and shows your personal apps.
Workspace context uses the workspace pool and shows workspace apps.
Switching contexts mid-session is safe - in-flight actions complete against whichever pool was active at start.

Best Practices

One workspace per business unit

If different teams have different budgets or apps, use separate workspaces. Each one has its own credit pool and member list, so usage stays isolated.

Use SSO for big teams

Manually inviting 50 employees gets old fast. Configure an SSO domain so anyone with a matching email auto-joins on first sign-in.

Watch attribution

The transaction history shows who consumed what. If a single member is responsible for a disproportionate share, surface it as feedback rather than letting the pool quietly drain.

FAQs

How is a workspace different from regular team collaboration?▾

Per-app collaborators (covered in Team & Collaboration) give other users edit access to a single app - useful for one-off pairings. A workspace is a shared billing entity: every member draws from one credit pool, every app belongs to the workspace, and there is no per-seat charge.

Who pays for workspace credits?▾

The workspace owner. Top-up packs purchased by the owner add to the workspace pool, not their personal balance. Members draw from the pool every time they generate, deploy, or use the AI proxy.

What happens when a member leaves?▾

Their access is revoked immediately. Apps they created remain in the workspace - ownership stays with the workspace, not the individual. Their personal account is unaffected.

Can a user belong to multiple workspaces?▾

Yes. Personal and workspace contexts are switchable from the navigation bar. Credit deductions apply to whichever workspace context is active when you start an action.

Ready to build?

Create your first app for free, no credit card required.

Team & Collaboration SSO Domains