Claude Team vs Enterprise at a glance
These are Anthropic’s published terms on 13 November 2026. Prices are in US dollars.
The seat price is the same headline number on both plans, but it buys different things. A Team seat includes usage. An Enterprise seat is access only, and Anthropic bills what people use at API rates. Model a heavy Claude Code user before you compare the two on price.
You can start on Team and move later. Anthropic documents an upgrade that keeps the same organization, with its members, chats and projects. The online route needs at least 20 seats and cannot be reversed; the sales route has a short cutover when people cannot use Claude.
Scroll sideways to see all columns. With the table focused, use the arrow keys.
| Claude Team | Claude Enterprise | |
|---|---|---|
| Size | 2 to 150 seats | 20 seat minimum when bought online, 50 through Anthropic’s sales team; no stated maximum |
| Seat price | Standard: $20 a month billed annually, $25 billed monthly. Premium: $100 billed annually, $125 billed monthly | $20 a seat a month, billed annually |
| Usage | Included with each seat, with per-member limits. Premium seats get 5 times the Standard allowance | Billed separately at API rates on top of the seat fee, with no included allowance |
| Claude Code | Included with every seat | Included with the Enterprise seat on new and self-serve plans |
| Single sign-on | Yes, with domain capture and just-in-time provisioning | Yes |
| SCIM provisioning | Not listed | Yes |
| Audit logs | Not listed | Yes |
| Compliance API | Not listed | Yes |
| Custom data retention | Not listed | Yes |
| Roles | Role-based permissions | Fine-grained roles, including custom roles |
| Spend controls | Spending caps for the organization, and per user where available | User and organization spend limits set by admins |
| Network controls | Not listed | Network-level access control and IP allowlisting |
| Custom connectors | Owners and Primary Owners add them | Owners, Primary Owners and custom roles that manage Libraries add them |
What neither plan decides: the apps your people build
A plan controls who can use Claude. It does not control what happens to the things people make with it. Within weeks of a rollout, someone in Finance has a purchase request tool and someone in Sales has a deal tracker. The questions that follow are the same on Team and on Enterprise.
Inside Claude, an artifact can be shared with invited people or with everyone in the organization, and viewers sign in with their Claude account. That suits a prototype. An app that a department depends on needs a place to run, a named owner, a chosen audience and a record of each release. SpringRoll is where that app goes: Claude deploys it through the SpringRoll connector, and colleagues open it from the App Portal.
Add SpringRoll to a Claude Team or Enterprise organization
The steps are the same on both plans. An Owner adds the connector once. Each member then connects and signs in to SpringRoll as themselves, so every deployment is recorded against the person who made it. Members cannot add a custom connector for themselves on either plan, so the Owner step comes first.
- In Claude, open Organization settings, then Connectors. Choose Add, then Custom, then Web.
- Name: SpringRoll
- URL: https://springroll.dev/api/mcp
- Choose Continue. Claude detects SpringRoll’s sign-in. Keep the recommended settings, including Use Claude’s published identity under OAuth client, and choose Add. There is no API key or client secret to enter.
- Each member opens Customize, then Connectors, finds SpringRoll and chooses Connect.
- On SpringRoll’s authorization page, a member with a SpringRoll workspace signs in. Someone trying it for the first time can choose Connect SpringRoll and start as a guest with no SpringRoll account.
Name: SpringRoll
URL: https://springroll.dev/api/mcp
OAuth client: Use Claude's published identity (Recommended)Add SpringRoll to Claude Code on either plan
Claude Code is included on both plans. Developers who work in a terminal add SpringRoll there directly, then approve the connection in the browser.
claude mcp add --transport http springroll https://springroll.dev/api/mcpWhich Claude plan to choose
Match your situation to the nearest row. The plan decides how you manage Claude, and SpringRoll decides how you manage what Claude builds.
If the only reason you are considering Enterprise is to control the apps people build, check whether SpringRoll on a Team plan already answers the question. Enterprise’s extra controls govern Claude itself: provisioning, logs, retention and network access.
Scroll sideways to see all columns. With the table focused, use the arrow keys.
| Your situation | Plan | What to set up in SpringRoll |
|---|---|---|
| Up to 150 people, an identity provider, and no requirement to export audit logs | Team | One workspace. Direct to Production for low-risk apps, and an audience on every app |
| People join and leave often and access must follow the directory | Enterprise, for SCIM | SCIM 2.0 provisioning in SpringRoll too, so removing someone from the directory removes their membership and revokes their agent credentials |
| An auditor will ask what was deployed, by whom and with which data | Enterprise, for audit logs | The Staged workflow, so a named person approves each Production release, and a data grant for each app |
| More than 150 seats | Enterprise | Groups from your directory as App Portal audiences |
| One department trying this for a quarter | Team, with a few Premium seats for heavy Claude Code users | Start as a guest with one example app, then create a workspace when a second person needs it |
Try it with one app before you choose
You do not need to settle the plan question to test the handoff. Any Claude plan can connect SpringRoll, and a guest connection needs no SpringRoll account. Use fictional records.
- Download the Purchase Desk example and open it in Claude or Claude Code.
- Ask Claude to deploy it through SpringRoll. Review the proposal and the placement receipt, then confirm.
- Follow the build to READY and open the app.
- Set the app’s audience to two colleagues. Ask one of them, and one person outside the audience, to open it from the App Portal.
- Open the app’s own provider address as well. The App Portal controls discovery and launch; the app must check sign-in itself at its own address. The team edition of Purchase Desk does.
Use SpringRoll to deploy this project. Show me the deployment proposal and the placement receipt first, then follow the build until it is READY.What SpringRoll does not change about your Claude plan
SpringRoll works beside either plan. These are the edges.
- It does not add SCIM, audit logs or retention controls to Claude Team. Those are Enterprise features of Claude.
- It does not see or store Claude conversations.
- It does not govern artifacts that stay inside Claude. It governs apps deployed through it.
- A deployed app’s provider address is not behind SpringRoll. Treat that address as reachable and have the app check access itself.
- Organization pricing for SpringRoll is by quote. A guest connection is a way to start, not a promise of hosting at no cost.
How SpringRoll helps on either Claude plan
Once SpringRoll is connected, the questions a rollout raises get the same answers on Team and on Enterprise.
SpringRoll does not replace anything in the two Claude columns. It records what happens to deployed apps. It does not log Claude conversations, manage Claude seats or set Claude spend limits. If you need a record of what people asked Claude, that is Enterprise’s audit log and Compliance API.
Scroll sideways to see all columns. With the table focused, use the arrow keys.
| Question | Claude Team | Claude Enterprise | With SpringRoll connected |
|---|---|---|---|
| Where does a finished app run? | As an artifact inside Claude | As an artifact inside Claude | Deployed to managed Vercel or Cloudflare, with a placement receipt naming the provider, plan and estimated cost |
| Who is accountable for it? | The person who made the artifact | The person who made the artifact | A named App Owner and support contact on every app |
| Who can open it? | Invited people, or everyone in the organization | The same, with external sharing off unless an Owner allows it | The audience you choose for that app in the App Portal: people, groups or the whole workspace |
| Does someone review a release? | No review step is described | No review step is described | Direct to Production, or a Staged route where a named person approves. An agent cannot record the approval |
| How does it reach company data? | Through each viewer’s own connectors | Through each viewer’s own connectors | Through the app’s own grant, limited to the fields and rows a data owner approved. Source credentials stay on the SpringRoll server |
| What record is kept? | Audit logs are not listed for Team | Audit logs and a Compliance API that records artifact events | An append-only, hash-chained history of deployments, approvals, access changes and data grants |
Frequently asked questions
Does Claude Team include single sign-on?
Yes. Anthropic lists single sign-on, domain capture and just-in-time provisioning for Team. SCIM is listed for Enterprise only.
Does Claude Team include Claude Code?
Yes. Every Team seat includes Claude Code, and Premium seats carry more usage. Enterprise seats on new and self-serve plans include it too.
What is the minimum for Claude Enterprise?
20 seats when bought online and 50 through Anthropic’s sales team, at $20 a seat a month billed annually, with usage billed separately at API rates.
Can a Claude Team organization add SpringRoll?
Yes. An Owner adds it once under Organization settings, Connectors, and each member connects from Customize, Connectors.
Do we need Claude Enterprise to control the apps people build?
No. SpringRoll’s owners, audiences, approvals and data grants work the same with Team and Enterprise. Enterprise adds controls over Claude itself.
Can we move from Team to Enterprise later?
Yes. Anthropic documents an upgrade of the same organization, online or through its sales team, and the online route cannot be reversed. Its article does not say whether custom connectors carry over, so check that SpringRoll is still listed afterwards.
