Claude Enterprise Pricing, Explained

What does Claude Enterprise cost?

Claude Enterprise pricing has two parts, and only one of them is published. As of August 2026 the seat is listed at $20 per user per month, billed annually. Usage is billed separately: every token your team spends across Claude's surfaces, Chat and Claude Code included, is charged at standard API (application programming interface) rates on top of the seat, with no allowance bundled in. Your seat line is fixed by headcount. Your usage line is fixed by nothing.

That is the shape of the bill. What follows is who qualifies, what the seat buys over the Team plan, and how the number you are quoted gets built.

Why Claude Enterprise pricing has a seat price but no list price

An Enterprise seat buys permission to use Claude under your company's controls. It carries no tokens with it. No published monthly total exists because two seats can differ by a hundred times: a manager who asks four questions a day and an engineer running Claude Code across a large repository both cost one seat, and their token bills are nothing alike.

How you pay depends on which door you walk through. The self-serve path takes a card or ACH bank transfer and runs on credits bought upfront, so usage draws down a balance you top up. The sales-assisted path is invoiced monthly in arrears. Invoice payment terms appear once the contract is large, at $50,000 or more as of August 2026. Enterprise is also sold through the AWS Marketplace. If you already have an AWS agreement, ask your account team whether Marketplace spend counts against your committed spend, because that answer lives in your AWS contract rather than in Anthropic's price list.

How many seats does Claude Enterprise require?

There are two minimums. Self-serve Enterprise starts at 20 seats. Sales-assisted Enterprise starts at 50 seats. Team runs from 2 to 150 seats, so a company past 150 people moves to Enterprise because Team has run out of room, not because of any single control.

[
  {
    "plan": "Pro",
    "usd_per_seat_month": 17,
    "min_seats": 1
  },
  {
    "plan": "Team standard",
    "usd_per_seat_month": 20,
    "min_seats": 2
  },
  {
    "plan": "Team premium",
    "usd_per_seat_month": 100,
    "min_seats": 2
  },
  {
    "plan": "Enterprise self-serve",
    "usd_per_seat_month": 20,
    "min_seats": 20
  },
  {
    "plan": "Enterprise sales-assisted",
    "usd_per_seat_month": 20,
    "min_seats": 50
  }
]

Read that chart with one thing in mind. A Team premium seat at $100 per month carries five times the usage of a standard Team seat, and that usage is included. An Enterprise seat at $20 per month includes none. The smaller number is the one with the open end.

What Enterprise buys that Team does not

Start with what Team already has, because this is where upgrade arguments usually go wrong. Team includes SSO (single sign-on) with SAML, domain capture, JIT (just-in-time) provisioning, role-based permissioning, and spend caps at both the user and the organisation level. Single sign-on is not a reason to move to Enterprise. It is already there.

Enterprise adds the controls a security team asks for by name:

• SCIM (system for cross-domain identity management) provisioning, so a leaver is deprovisioned by your identity provider instead of by hand.
• Audit logs, with OpenTelemetry monitoring. Anthropic lists these as Enterprise only.
• A Compliance API that returns usage data, activity logs, chat histories and file content, filtered by user and by time range.
• Custom data retention controls.
• Network-level access control and IP allowlisting.
• Customer-managed encryption keys. You provision a key in your own cloud account, and Anthropic uses that key to protect your team's chats, projects and files.
• US-only inference, which keeps your company's inference inside the United States.
• A HIPAA-ready offering (Health Insurance Portability and Accountability Act), plus fine grained role-based access control.

One idea runs through that list: evidence. Team lets a person use Claude under sane defaults. Enterprise lets you prove afterwards what that person did. When an auditor asks which files an employee uploaded last quarter, the Compliance API answers it and a Team plan cannot, because Team exposes no audit log and no endpoint to query one.

Data retention and model training

Content on commercial plans is not used to train Anthropic's models by default. That holds on Team as well as Enterprise, so "they will train on our conversations" is not a reason to upgrade. What Enterprise adds is control over how long content is kept, and the ability to read it back programmatically.

Anthropic publishes SOC 2, ISO 27001, GDPR (General Data Protection Regulation) and CCPA (California Consumer Privacy Act) compliance for the platform. Those are properties of the service and not line items you negotiate. Retention length, the HIPAA offering, customer-managed keys and the inference region are the parts that go into a contract.

The context window is not the reason anymore

Older write-ups describe an expanded 500K token context window as the Enterprise headline. Check that claim against the current help center before you buy on it. As of August 2026 Anthropic documents a 1M token context window for Opus 5 and Sonnet 5 on all paid plans, and 500K for Opus 4.8 and Sonnet 4.6 on all paid plans. Context length follows the model you pick, so if you want a bigger window, pick a newer model. Choosing between them is its own question, covered in which Claude model to use for which job.

What decides your quote

Four inputs move the number.

• Seat count. Under 20 seats Enterprise is not sold at all. From 20 to 49 you are on the self-serve path with fixed terms. At 50 and above a salesperson is involved, which is where custom terms become possible.
• Term. Enterprise uses a single seat type, priced per user per month and billed annually. The annual commitment is the default shape of the deal rather than a discount you have to ask for.
• Expected usage. Usage bills at API rates with no allowance, so this is where your risk sits. Estimate it from a real month of Team or API usage, not from headcount, because headcount tells you nothing about tokens.
• The extras. HIPAA readiness, customer-managed encryption keys, US-only inference and a custom retention length are separate asks. Raise them on the first call, because they change which agreement you end up signing.

Before that call, pull one real number: the tokens your people spent last month. Where Claude Code tokens actually go and how Claude usage limits work both explain how to read that figure. A quote you cannot check is a quote you cannot argue with.

Solo, small team, or org

• One person. Pro or Max. Enterprise is closed to you, and the seat minimum is the reason. Start from choosing between the Claude plans.
• 2 to 150 people, no audit obligation. Team. You already get single sign-on, domain capture, role-based permissions and spend caps, with usage included in the seat. The Claude Team plan for a small business covers the seat math.
• Over 150 people, or under an audit obligation. Enterprise. The trigger is either the Team seat cap or one named control from the Enterprise-only list, usually SCIM or audit logs.
• Machine workloads with no human behind them. The API. A nightly batch job does not need a seat, and giving it one wastes the fee.

When Enterprise beats putting the API on a corporate account

Enterprise usage is billed at standard API rates. So moving a team from a corporate API account to Enterprise does not change what a token costs. It adds a fixed fee per human head, and that fee buys identity and audit controls a raw API key does not have.

An API-only setup gives you metered usage with no seat minimum and no monthly floor. It also gives you no interface for the people who do not write code, no identity managed through your directory, and no per-person audit trail, because an API key is not a person. Every key you issue is a credential someone must rotate and nobody has to justify.

The break-even is therefore decided by how many humans need supervised access. Multiply seat count by the monthly seat fee, then compare that against building the same controls yourself: a proxy in front of the API, your own key rotation, your own logging, your own per-user attribution. Under 20 people the comparison never happens, because the seat minimum rules Enterprise out. At a few hundred people, the seat fee is usually smaller than the engineering it replaces. Run the same arithmetic at the individual level first with the break-even between the Claude API and a subscription, because the shape of the answer is the same and the numbers are easier to check.

FAQ

How much does the Claude Enterprise plan cost per user?

The published seat price is $20 per user per month, billed annually, as of August 2026. That figure covers the seat only. Every token your team spends is billed separately at standard API rates with no allowance included, so the total is seat price times headcount plus actual consumption. No all-in price is published because usage per seat varies far too much to quote in advance.

What is the minimum number of seats for Claude Enterprise?

Twenty seats if you buy self-serve with a card or ACH transfer. Fifty seats if you buy through a salesperson. Under twenty seats Enterprise is not available, and Team is the tier to use. Team itself caps at 150 seats, so any company larger than that moves to Enterprise whether or not it needs the extra controls.

Does Claude Enterprise include usage, or is it billed separately?

Separately. Enterprise charges every token at standard API rates on top of the seat fee, and no allowance is bundled in. Pro, Max and Team work the other way: usage comes with the seat and is bounded by rate limits instead of by an invoice. Self-serve Enterprise draws usage from credits bought upfront, while sales-assisted Enterprise is invoiced monthly in arrears.

Do I need Enterprise to get SSO for Claude?

No. Team already includes single sign-on with SAML, domain capture and just-in-time provisioning. What Team lacks is SCIM provisioning and audit logs, and those two are what usually force the move, along with the Compliance API that reads them back. If the requirement is that employees sign in with their work identity, Team meets it.

Is company data used to train Claude on the Enterprise plan?

No. Content on commercial plans is not used to train Anthropic's models by default, and that applies to Team as much as Enterprise. Enterprise adds custom data retention controls, a Compliance API for exporting activity and content by user and time range, customer-managed encryption keys and a US-only inference option.