LICENSEWARE

Cursor Teams and Enterprise licensing

This article is about Cursor's business plans: Teams seats billed per active user, and Enterprise plans on an Order Form with Core Licenses, Precommitted Usage and true-ups. Individual plans and model pricing are covered in separate articles. It is not legal advice.

On This Page

Cursor Teams and Enterprise are the two business plans Anysphere sells. The Docs state that there are two business plans, Teams and Enterprise (custom), and that Teams has two paid seat types, Standard at $40 per user per month and Premium at $120 per user per month with five times the Standard usage.[1] Anysphere recommends Teams for customers who are happy to self-serve, and Enterprise for those who need priority support, pooled usage, invoicing, SCIM or advanced security controls.[1]

Editions

Teams plans add centralized billing and administration, a team marketplace for internal rules, skills and plugins, agentic code review with Bugbot, cloud agents and automations with shared team context, usage analytics, team-wide Privacy Mode enforcement and SAML or OIDC single sign-on.[1] SAML 2.0 SSO is available at no additional cost on Teams and Enterprise.[7]

Enterprise includes everything in Teams, plus pooled usage shared across all team members, SCIM seat management and automated provisioning, granular admin controls (Model Access Control, Run Mode, Repository Blocklist and MCP Configuration), Self-Hosted Machines for Cloud Agents, and priority support with dedicated account management.[5] Audit logs and invoice billing are also listed as Enterprise features.[11] Enterprise has no public price; a quote is requested through the sales contact form.[5]

Metrics

On Teams the unit is the paid seat, billed monthly or yearly, with a seat type that sets the included usage. Teams also has a free Unpaid Admin seat for administrators who do not use Cursor.[1] Roles are separate from seat types: Members, Admins and Unpaid Admins are roles, and a Member or Admin can hold either a Standard or Premium seat.[1][2] The catalog rows are Teams Standard seat, Teams Premium seat and Unpaid Admin seat.

On Enterprise the Pricing Policy uses different vocabulary. Cursor Core Licenses are required, Precommitted Usage is pooled across users under the same account number, and an Active User is a user acting under the customer’s account who accesses the Service at least once during the True Up Period.[4] See Core License, Active User and Precommitted Usage.

Counting and floors

Teams

Cursor bills per active paid seat, not pre-allocated seats, so seats can be added, removed, upgraded or downgraded at any time. Adding a member mid-cycle creates a pro-rated charge, and the renewal date does not change.[1] A member who used credits keeps the seat occupied until the cycle ends.[1] An upgrade from Standard to Premium takes effect immediately; a downgrade takes effect at the next renewal.[2] A team must always have at least one Admin and one paid member.[2]

Included usage comes in two pools, Cursor Models and Other Models, and is allocated per user by seat type. It does not transfer between members and resets at the start of each billing cycle.[1] Third-party model usage is charged at public list API prices plus the Cursor Token Rate of $0.25 per million tokens, including when Auto routes to a third-party model.[1][12] On-demand usage is enabled by default for Teams and billed monthly in arrears.[1]

Two administrative details affect seat counts. First, joining a team automatically cancels any individual Pro subscription on the joining account, and members cannot leave a team on their own.[3] Second, teammates with a verified, matching email domain can join without an invite when that domain control is enabled, and invite links have a long expiration and let anyone with the link join, so the documentation advises revoking links regularly or using SSO or domain restrictions.[2] A yearly team plan cannot be switched to monthly mid-plan.[2]

Enterprise

Under the Pricing Policy, Precommitted Usage is the minimum usage-based fees the Order Form commits the customer to pay during its Service Term, and it does not roll over to a later term.[4] Only Model API Fees and Cursor Token Fees count toward it.[4] On-Demand Usage is usage above the commitment, billed at the Order Form rate, or usage that occurs when no Order Form is current.[4]

The true-up works as follows. At the end of each True Up Period, Anysphere counts Active Users who accessed the Service in the final 30 days. For each seat above the True Up Baseline (the Core License seat count), it invoices a per-seat Core License Fee and a Precommitted Usage Fee for the remaining months of the Service Term, and the higher count becomes the next baseline.[4] Reassigning licensed seats to new users within the enterprise organization is permitted without extra fees, provided Active Users within the 30-day period do not exceed the Core License seat count.[4] Commentary: because the definition counts users who accessed the Service during the period, a licence manager would compare distinct users who signed in during the final 30 days with the seat count; the Policy does not say how a seat reassigned within that window is counted.

Spend controls

Teams can set monthly team-wide spend limits. Per-member limits are available on Enterprise plans.[1] Enterprise limits can also be set per directory group, and a user in several groups receives the highest applicable limit.[6][8] On Enterprise pooled-usage accounts, member spend limits apply to total usage, not only on-demand usage.[8] Account administrators may also set hard limits or caps on usage for the organization.[4] Enforcement is not instant, so usage can briefly exceed a limit.[8]

Identity and device controls

SCIM 2.0 provisioning is available on Enterprise plans with SSO enabled and requires contacting sales; SCIM-provisioned users and groups are read-only in Cursor.[6] For corporate devices, an allowed-team-ID policy distributed by mobile device management logs out any user who signs in with a team ID outside the list, which prevents use of personal accounts on managed machines.[10]

Programs and contract terms

Enterprise customers buy under an Order Form, though the Pricing Policy notes that an Order Form is not necessary to access and use the Services.[4] Where an organization has a Master Services Agreement with Anysphere, that agreement governs use of the Service instead of the online Terms, and the Terms’ payment section is subject to any pricing in an Order Form.[9] Invoices go to the billing email on the Order Form. Purchase order documents must reach Anysphere at least five business days before the end of the next billing period, and payment is due net 30 days from the invoice date unless the Order Form says otherwise.[4]

An auto-renewing Order Form renews for the period it states. Either party can opt out with written notice at least 30 days before the current Service Term expires.[4] Taxes are the customer’s responsibility, and the customer agrees that Anysphere may reference it as a customer in marketing materials and public events, subject to any review right in the Order Form.[4] The Acceptable Use Policy prohibits exploiting account provisioning, team management or user assignment workflows to avoid or reduce fees.[14]

Out of scope

This article does not state Enterprise prices or minimum commitments, which are set in confidential Order Forms. It does not cover the data-processing terms, model pricing or Bugbot and Cloud Agent billing, which are in the related articles, and it does not cover Teams pricing shown on the cursor.com pricing page, which listed a different Teams entry price at retrieval and is discussed in the overview.

References

  1. Team Pricing (Cursor Docs)Seat types, included usage, on-demand usage, active seats, spending controls. Not date-stamped.Retrieved 2026-10-13.
  2. Members, Roles, and Seat Types (Cursor Docs)Roles, seat changes, domain controls, yearly billing. Not date-stamped.Retrieved 2026-10-13.
  3. Teams management (Cursor Help)Adding members, effect on Pro subscriptions. Not date-stamped.Retrieved 2026-10-13.
  4. Pricing PolicyLast updated Aug 21, 2026. Sections 1 to 9.Effective 2026-08-21. Retrieved 2026-10-13.
  5. Enterprise plan (Cursor Help)Not date-stamped.Retrieved 2026-10-13.
  6. SCIM provisioning (Cursor Docs)Not date-stamped.Retrieved 2026-10-13.
  7. SSO and SAML (Cursor Docs)Not date-stamped.Retrieved 2026-10-13.
  8. Spend limits (Cursor Help)Not date-stamped.Retrieved 2026-10-13.
  9. Terms of ServiceLast updated September 3, 2026.Effective 2026-09-03. Retrieved 2026-10-13.
  10. Identity and Access Management (Cursor Docs)Roles, SSO, SCIM, MDM allowed team IDs. Not date-stamped.Retrieved 2026-10-13.
  11. Pricing and plans (Cursor Help)Plan table; Enterprise inclusions. Not date-stamped.Retrieved 2026-10-13.
  12. Models & Pricing (Cursor Docs)Cursor Token Rate. Not date-stamped.Retrieved 2026-10-13.
  13. Overages (Cursor Help)Not date-stamped.Retrieved 2026-10-13.
  14. Acceptable Use PolicyLast updated August 11, 2026.Effective 2026-08-11. Retrieved 2026-10-13.

See also

Catalog Rows Cited

7Metrics4SKUs4Programs

Esc