In the works ยท join the waitlist

Commission for teams: one hub for your whole team's Claude Code.

Put Commission on one dedicated box, a VPS or a machine in the office. Everyone on your company's tailnet connects to it and works in shared spaces, and every Claude in a space knows what the others have learned. We're building it now, alongside Commission for one person.

One box. Your tailnet. Nothing else to set up.

1

Put the hub on a dedicated box

A VPS or a machine in the office. Commission sets it up and looks after it, including keeping each space walled off from the others.

2

Everyone joins over your tailnet

Being on the company tailnet is the whole setup: no Commission accounts, invites or pairing codes. The hub knows who is who from their tailnet login.

3

Give people spaces

A space holds a product or a client. A space has many people and a person can be in many spaces. Access is simply who can open which space.

What your team gets.

  • It feels like one Claude account. Everyone signs in with their own Claude, but a space shares what Claude has learned: project memory, session history, skills and MCP servers. Your Claude stops saying "ask whoever committed this".
  • Ready on day one. A new hire joins the tailnet and opens Commission. The space's repos, tools and integrations are already there, and their first session already knows the project.
  • From git blame to the session behind it. Commits made in Commission point to the session that made them, so you and Claude can read why a change was made.
  • Who did what. Approvals, messages and new sessions show the person. Hub owners see every session, and making a session private to a few people is logged.
  • Clients kept apart. Each space runs walled off on the box, so one client's code and keys can't be read from another client's sessions.
  • Every machine, the same setup. When someone works in a space from their own laptop, it gets the space's memory and tools too.
Your Claude accounts

Bring your own Claude.

Commission never provides, stores, pools or manages Claude subscriptions. Each person signs in with their own Claude account, such as a Claude Team or Enterprise seat or an API key, and your team is responsible for following Anthropic's terms.

Your network

Devices reach the hub over your tailnet. There is no Commission cloud in the middle and nothing listens on the public internet.

Your box

The hub, the sessions and their history stay on hardware your team runs, whether that's a VPS or a machine in the office.

Claude Code, as it is

Commission drives Claude Code with each person's own sign-in, and Claude Code talks to Anthropic exactly as it always does.

Commission is not affiliated with or endorsed by Anthropic.

Join the waitlist.

Tell us a little about your team. We'll write when there's something to try, and the answers help decide what comes first.

We use your email only for Commission for teams and never share it. Reply to any email from us to be taken off the list.

Questions.

When will it be ready?

We're building it now and will write to the waitlist when there's something to try. There are no dates yet.

Can several people share one Claude account?

No. Each person uses their own Claude account, and Commission isn't built to share one. Anthropic's individual plans are meant for one person.

Will Commission for one person change?

No. It stays as it is and keeps getting updates while the team version is built.

We need SSO, audit export or policy controls.

Tick the box in the form. Enterprise controls come after the team version, and the waitlist helps decide which come first.