OpenClaw Business Accounts and Shared Billing Guide

Teams adopting OpenClaw quickly hit an operational question: how do we share capacity and billing without sharing one login? Business accounts solve this by separating billing ownership from individual access while pooling instance capacity across the team.

Evidence from the field: MVP shipped March 16, 2026

Business accounts shipped as a production feature on March 16, 2026, with owner-managed billing, email-based invitations, and shared capacity counting. The implementation provides concrete evidence of how teams actually use shared billing in production.

• Backend models: The system introduced three new database models — BusinessAccount, BusinessAccountMember, and BusinessAccountInvitation — to track ownership, membership, and pending invitations.
• Capacity sharing: Instances count against a shared plan limit across the business account. The billing resolution explicitly uses the owner's Stripe account for deploy entitlement while tracking active instances across all members.
• Invitation flow: Members join through an email invitation link and complete acceptance with their own Google authentication. The system handles wrong-email cases and provides a public invitation acceptance page.
• Instance ownership: Instance creator ownership stays on instance.user_id while billing and capacity attach to instance.business_account_id. Members see only their own instances, not each other's.
• Member lifecycle constraints: Removing or quitting a business account is blocked while that member still has non-deleted instances attached to the business account — preventing accidental orphaning.

The problem business accounts solve

Without business accounts, teams face two bad options:

• Share one login: Multiple people use the same account, which creates security risk, makes attribution difficult, and mixes personal and work usage.
• Separate personal plans: Each person has their own plan and billing, which fragments capacity tracking and makes team-wide management impossible.

Business accounts provide a third path: one billing owner, multiple team members, and shared capacity counting.

How business accounts actually work

A business account converts a personal plan into a team billing scope. The owner controls the plan and invitations, members join from their own accounts, and active-instance capacity is pooled across everyone.

Core mechanics

• Owner-managed billing: One person owns the Stripe subscription and plan management.
• Email invitation flow: Members receive an invitation link and join through a dedicated acceptance flow.
• Shared capacity counting: All instances created by owner and members count against the same plan limit.
• Separate member logins: Each person uses their own Google account to access the dashboard.
• Creator-based instance ownership: Members see and manage the instances they created, not each other's.

What stays personal

Business accounts share billing and capacity, but they do not share everything. Team members do not see one another's instances. Each person manages the instances they created, but those instances consume the shared business-account capacity.

Who should use a business account

Clear fit cases

• Small teams with shared infrastructure: 2–10 people deploying OpenClaw instances for related work.
• Organizations with centralized billing: Teams that want one invoice and payment method regardless of how many people deploy.
• Remote and distributed teams: Groups where sharing a single login is impractical or a security violation.
• Teams growing beyond solo experimentation: When one person's plan no longer covers the team's instance needs.

Edge cases where business accounts may not fit

• Strict instance isolation: If your compliance model requires completely separate billing and capacity per person, separate personal plans may be required.
• Contractual billing separation: Some organizations require separate invoices per cost center or team member.

Migration patterns: from separate plans to business account

Pattern 1: Consolidating multiple personal plans

If your team already has multiple personal plans:

1. Choose which account will become the business account owner.
2. Enable business account mode from the owner's billing settings.
3. Send invitations to team members who currently have separate plans.
4. Members accept invitations and optionally cancel their redundant personal plans after migration.

Pattern 2: Upgrading from a single shared login

If your team has been sharing one account:

1. Identify the owner who will retain billing control.
2. Each team member creates their own OpenClaw Setup account.
3. The owner enables business account mode and invites members by email.
4. Members migrate any critical instances before fully leaving the shared login.
5. Disable or remove the shared login once migration is complete.

Operational considerations

Capacity planning

With shared capacity, you need to plan instance usage at the team level rather than per person. Consider:

• Peak concurrent instances: How many instances will run at the same time across the team?
• Development vs production: Do you need separate capacity for experimental and production instances?
• Growth headroom: Plan for new team members and increased usage over the next quarter.

Member lifecycle

Plan for people joining and leaving:

• Onboarding: New members receive an invitation link and complete acceptance through their own Google account.
• Offboarding: The owner removes members from the business account when they leave the team.
• Instance handoff: If a departing member owns critical instances, plan for transfer or recreation before their account loses access.

Verification checklist

After setting up a business account, confirm:

• Owner sees the business account section in billing settings.
• Invited members receive and can complete the invitation flow.
• Members can log in with their own accounts and access the dashboard.
• Instances created by members count against the shared plan capacity.
• Members see only their own instances, not other members' instances.
• One invoice appears for the business account, not separate invoices per person.

Typical mistakes

Mistake 1: Sharing credentials instead of using business accounts

Sharing one login creates security risk, makes auditing impossible, and violates most corporate security policies. Use business accounts instead.

Mistake 2: Not planning instance handoff for departing members

If a member leaves and owns critical instances, you may lose access or have to recreate work. Document instance ownership and plan transfers before offboarding.

Mistake 3: Underestimating shared capacity needs

Pooling capacity means one team member can consume the entire plan. Monitor usage and set internal guidelines if necessary to prevent one person from monopolizing resources.

Comparison: business account vs alternatives

Getting started with business accounts

If you are evaluating whether a business account fits your team:

1. Review your current setup: shared login, separate plans, or mixed?
2. Count active team members and instances to estimate capacity needs.
3. Identify the billing owner who will manage the business account.
4. Enable business account mode from the owner's billing settings.
5. Send invitations and verify members can complete the flow.

Set up your team with business accounts

Managed OpenClaw hosting supports business accounts with shared billing, team member invitations, and pooled instance capacity. One owner manages billing while each team member operates from their own account.

Set up business account View pricing Business account feature details

Related reading