Claude Enterprise Pricing: Wetin Dem Really Dey Charge

Wetin Claude Enterprise dey cost?

Claude Enterprise pricing get two parts, but dem publish only one. As of August 2026, dem list the seat at $20 for each user every month, with annual billing. Dem bill usage separately: every token wey your team spend across Claude surfaces, including Chat and Claude Code, dem charge am according to standard API (application programming interface) rates on top of the seat. No usage allowance dey included. The amount for seats depend on headcount. The amount for usage no get fixed limit.

Na so the bill dey structured. The remaining part explain who qualify, wetin the seat add compared with Team plan, and how dem calculate the quote wey dem give you.

Why Enterprise price get seat price but no fixed price

Enterprise seat dey buy permission to use Claude under your company control. E no come with any token. No published monthly total dey because two seats fit differ up to hundred times: manager wey dey ask four questions per day and engineer wey dey run Claude Code across large repository both dey use one seat, but their token bills no be alike at all.

How you go pay depend on the route wey you take. Self-serve path dey accept card or ACH bank transfer, and e dey work with credits wey you buy upfront, so usage go reduce the balance wey you dey top up. Sales-assisted path dey send invoice monthly in arrears. Invoice payment terms dey show when contract reach large size, $50,000 or more as of August 2026. Dem also dey sell Enterprise through AWS Marketplace. If you already get AWS agreement, ask your account team whether Marketplace spend dey count toward your committed spend, because na your AWS contract dey define that answer, no be Anthropic price list.

How many seats Claude Enterprise need?

Minimum dey two. Self-serve Enterprise start for 20 seats. Sales-assisted Enterprise start for 50 seats. Team dey run from 2 reach 150 seats, so company wey pass 150 people go move to Enterprise because Team don reach im limit, no be 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 for mind. One Team premium seat wey cost $100 every month get five times the usage of standard Team seat, and that usage dey included. One Enterprise seat wey cost $20 every month no include any usage. Na the smaller number get the open end.

Wetin Enterprise get wey Team no get

Make we first look wetin Team already get, because na here upgrade reasons dey usually go wrong. Team get SSO (single sign-on) with SAML, domain capture, JIT (just-in-time) provisioning, role-based permissioning, and spend caps for both user and organisation level. Single sign-on no be reason to move to Enterprise. E don already dey there.

Enterprise add the controls wey security team dey specifically ask for:

• SCIM (system for cross-domain identity management) provisioning, so identity provider fit deprovision person wey leave instead of person doing am by hand.
• Audit logs, with OpenTelemetry monitoring. Anthropic list these as Enterprise only.
• Compliance API wey dey return usage data, activity logs, chat histories and file content, filtered by user and time range.
• Custom data retention controls.
• Network-level access control and IP allowlisting.
• Customer-managed encryption keys. You provision key for your own cloud account, and Anthropic use that key protect your team's chats, projects and files.
• US-only inference, wey keep your company's inference inside United States.
• HIPAA-ready offering (Health Insurance Portability and Accountability Act), plus fine grained role-based access control.

One idea dey run through the whole list: evidence. Team let person use Claude with sensible defaults. Enterprise let you prove afterwards wetin that person do. When auditor ask which files employee upload last quarter, Compliance API answer am, but Team no fit, because Team no expose audit log and no get endpoint to query am.

Data retention and model training

By default, dem no dey use content for commercial plans to train Anthropic's models. This one apply to Team and Enterprise too, so “dem go train with our conversations” no be reason to upgrade. Wetin Enterprise add na control over how long dem go keep content, plus ability to read am back programmatically.

Anthropic publish SOC 2, ISO 27001, GDPR (General Data Protection Regulation) and CCPA (California Consumer Privacy Act) compliance for the platform. Dem be properties of the service, no be separate items wey you go negotiate. Retention length, the HIPAA offering, customer-managed keys and the inference region na the parts wey go enter contract.

Context window no be the reason again

Old write-ups dey describe 500K token context window as the main Enterprise feature. Check this claim against the current help center before you rely on am. As of August 2026, Anthropic dey document 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 dey follow the model wey you choose, so if you want bigger window, choose newer model. Choosing between dem na separate question, and which Claude model to use for which job cover am.

Wetin decide una quote

Four things dey move the amount.

• Number of seats. If seats dey below 20, dem no dey sell Enterprise at all. From 20 to 49, una dey use self-serve path with fixed terms. From 50 and above, salesperson go join, and na there custom terms fit happen.
• Term. Enterprise get only one seat type. Dem price am per user per month, but billing dey happen yearly. The yearly commitment na the normal structure of the deal, no be discount wey you need ask for. This different from the plans wey una people dey use now, where cancelling or downgrading dey take effect for the end of the month wey una don already pay for. So treat the year as decision wey una make once, no be something wey una fit reverse for April.
• Expected usage. Usage billing dey follow API rates with no allowance, so na here your risk dey. Estimate am from one real month of Team or API usage, no be from headcount, because headcount no tell you anything about tokens. The model wey your people dey use fit change the amount as much as how much dem type. So price the mix wey you expect: wetin Fable 5 cost per million tokens and the jobs wey e fit handle na the kind per-model number wey suppose enter the estimate.
• The extras. HIPAA readiness, customer-managed encryption keys, US-only inference, and custom retention length na separate requests. Mention dem for the first call, because dem fit change the agreement wey una go sign.

Before that call, bring one real number: the tokens wey your people use last month. Where Claude Code tokens really dey go and how Claude usage limits dey work both explain how to read that number. Quote wey you no fit check na quote wey you no fit challenge.

Solo, small team, or org

• One person. Pro or Max. Enterprise no dey available for you because of the seat minimum. Start with how to choose between the Claude plans. If Pro look like the answer, check how much Pro cost and where its usage limits fit stop you before you commit for one year. If ChatGPT subscription dey your other shortlist option, the individual tiers from both vendors get almost the same price, so na the work you dey do go decide.
• 2 to 150 people, no audit obligation. Team. You already get single sign-on, domain capture, role-based permissions, and spend caps, while usage dey included for the seat. Claude Team plan for small business go explain the seat calculation.
• More than 150 people, or you get audit obligation. Enterprise. The trigger fit be either the Team seat cap or one named control from the Enterprise-only list, usually SCIM or audit logs.
• Machine workloads wey no human dey behind dem. The API. Nightly batch job no need seat, and giving am one go waste the fee.

When Enterprise better pass putting API for corporate account

Enterprise usage dey billed with standard API rates. So if you move team from corporate API account go Enterprise, e no change wetin each token cost. E add fixed fee for each human seat, and that fee pay for identity and audit controls wey raw API key no get.

API-only setup give you usage wey meter, with no minimum seat and no monthly floor. But no floor no mean say e free: API no get free tier, na small signup credit e get, so meter go start from your first call. E still no give interface for people wey no dey write code, no identity wey your directory dey manage, and no audit trail for each person, because API key no be person. Every key wey you issue na credential wey person must rotate, but nobody must explain why dem get am.

So, break-even depend on how many people need supervised access. Multiply seat count by monthly seat fee, then compare am with the cost of building the same controls yourself: proxy wey dey in front of API, your own key rotation, your own logging, and your own way to attribute activity to each user. If na under 20 people, this comparison no even start, because seat minimum don already rule Enterprise out. If na few hundred people, seat fee usually smaller than the engineering work wey e replace. First run the same calculation for one person with the break-even between Claude API and subscription, because the answer pattern na the same and the numbers easier to verify.

FAQ

Claude Enterprise plan dey cost how much per user?

Published seat price na $20 per user every month, with annual billing, as of August 2026. That amount cover the seat only. Every token wey your team use dey billed separately at standard API rates, with no allowance included. So total cost na seat price times number of users, plus actual usage. No all-in price dey published because usage per seat fit vary too much to calculate ahead of time.

Wetin be the minimum number of seats for Claude Enterprise?

Na twenty seats if you buy self-serve with card or ACH transfer. Na fifty seats if you buy through salesperson. Enterprise no dey available below twenty seats; Team na the tier to use. Team itself get limit of 150 seats, so any company wey pass that number go move to Enterprise, whether e need the extra controls or not.

Claude Enterprise include usage, or dem dey bill am separately?

Dem dey bill am separately. Enterprise charges every token at standard API rates on top of the seat fee, and no allowance dey bundled inside. Pro, Max and Team work the other way: usage dey come with the seat, and rate limits dey control am instead of invoice. Self-serve Enterprise dey use credits wey you buy upfront, while sales-assisted Enterprise dey send invoice monthly in arrears.

I need Enterprise to get SSO for Claude?

No. Team already include single sign-on with SAML, domain capture and just-in-time provisioning. Wetin Team no get na SCIM provisioning and audit logs. Those two na usually wetin make people move to Enterprise, together with Compliance API wey dey read the records back. If the requirement na for employees to sign in with their work identity, Team meet am.

Dem dey use company data to train Claude for Enterprise plan?

No. Content for commercial plans no dey used to train Anthropic's models by default, and this apply to Team just as e apply to Enterprise. Enterprise add custom data retention controls, Compliance API for exporting activity and content by user and time range, customer-managed encryption keys, and US-only inference option.