Cursor Pricing 2026: Individual, Teams, and Enterprise Plans Compared
TL;DR: Cursor's pricing changed on October 12, 2026, when Cursor became part of The X Subscription. Cursor sells individual plans, Teams seats, and custom-priced Cursor Enterprise plans, with list prices on Cursor's pricing page. The seat price is only the starting cost, because third-party models such as Claude and GPT bill at API list price outside the included pool. Teams and Cursor Enterprise plans also add a per-token Cursor Token Rate on those requests. minware regresses Cursor token spend against roadmap value delivery, on-time delivery rate, and overhead cost, so the slope shows whether higher spend buys more delivery.
Cursor's per-seat price is the number everyone quotes, but the invoice also carries usage charges the seat price leaves out. The X Subscription shares one weekly usage pool across Cursor and Grok products. Third-party models moved outside that pool on the new plans, so teams that rely on Claude, GPT, or Gemini pay API list price from the first request.
For engineering leaders preparing a budget or board review, the harder question is whether that spend buys delivery outcomes the business can see.
Updated October 2026 to reflect The X Subscription pricing.
Cursor's 2026 plans at a glance
Cursor now sells seven plans: five individual tiers, Teams, and Enterprise. Every paid plan includes one pool of usage for Cursor's own models, shared across the editor agent, the Grok apps, and Cloud Agents from Premium up. That pool refreshes weekly, so one heavy day doesn't use up a month's allowance.
| Plan | Price | Included usage | Third-party models |
|---|---|---|---|
| Free | $0 | Limited | Not available |
| Plus | $8/month | Base | Not available |
| Premium | $30/month | 4x Plus | API list price |
| Super | $100/month | 15x Plus | API list price |
| Ultra | $200/month | 50x Plus | API list price |
| Teams | $30, $100, or $200 per seat/month | Matches the seat's tier | API list price plus Cursor Token Rate |
| Enterprise | Custom | Pooled | API list price plus Cursor Token Rate |
The included usage multiples describe the size of each plan's weekly pool relative to Plus.
Individual plans for solo developers
Individual plans suit developers paying for their own seat or a small group testing Cursor before a wider rollout. Free and Plus include only Cursor's first-party models, so Plus fits developers who work in Grok or Composer. Premium adds Cloud Agents, automations, Bugbot code reviews, and third-party models at API list price. Super adds priority model access at peak times, while Ultra adds earliest access to new products and models.
Individual plans include Privacy Mode, which keeps Cursor from training on your code. The Cursor Token Rate applies only to Teams and Enterprise, so individual plans pay API list price alone on third-party requests.
Teams seats for organizations
Teams, the plan many buyers search for as Cursor Business, gives each paid member a Premium, Super, or Ultra seat at the same price as the matching individual plan. Members of one team can mix seat tiers, such as three Premium seats and one Super seat. Plus isn't available as a team seat, so the lowest paid Teams seat is Premium. Teams adds centralized billing, usage analytics, team-wide privacy settings, and custom Chat data retention. It also adds single sign-on through SAML or OpenID Connect (OIDC).
System for Cross-domain Identity Management (SCIM) seat management, audit logs, and service accounts require Cursor Enterprise. Cursor's announcement says Teams seats cost less than seats on the older Cursor Teams plan, with 3x more coding usage.
Cursor Enterprise for governance and scale
Cursor Enterprise is custom-priced through Cursor sales, with no published list price. It pools usage across the organization and supports invoice billing. The advanced governance controls are Enterprise-only, including SCIM seat management, audit logs, service accounts, and group-level spend limits. Enterprise also adds repository, model, and Model Context Protocol (MCP) access controls, plus priority support.
Cursor Enterprise customers can enroll teams in US-only data residency, which keeps inference, processing, and storage for supported features in the US. It adds a 10% uplift to eligible model pricing and is enabled per team. Privacy Mode is on by default for Enterprise teams. Third-party requests on Cursor Enterprise bill at API list price plus the Cursor Token Rate, while Cursor's own models draw from the pooled allowance.
Third-party model costs and the Cursor Token Rate
The seat price covers Cursor's own models only. Third-party models sit outside the included pool on every plan that offers them, so Claude, GPT, and Gemini requests bill at API list price, paid from prepaid credit. You can set spending caps on that usage.
On Teams and Enterprise, third-party requests also carry a Cursor Token Rate of $0.25 per million tokens on top of the provider's API price. It applies to direct third-party selections and to Cursor Router requests routed to a third-party model, including bring your own key (BYOK) usage. Auto's Cost mode is exempt. So are Cursor's own models, including Grok and Composer.
Long agent sessions push this cost up. Every agent turn resends the conversation so far, so each turn in a long session carries more context than the last. Model choice also affects how quickly included usage runs out.
Legacy plans for existing subscribers
Subscribers on Cursor's earlier plans can keep their plan or switch to The X Subscription, and a plan they keep goes on working as it does today. Legacy Pro, Pro+, and Ultra run on two monthly usage pools plus on-demand usage at API rates. One pool covers Cursor Models, and the other covers Other Models.
Teams created before The X Subscription keep Standard seats at $40 and Premium seats at $120 per user per month, with Premium carrying 5x the Standard allowance. Included third-party usage on a legacy plan continues until the subscriber switches, so compare a legacy team's current third-party model usage against per-request API pricing before moving it.
Feature comparison across Cursor plans
The table compares governance and billing features across plan groups, drawn from Cursor's plan comparison plus its data residency documentation. The individual column covers Premium, Super, and Ultra.
| Feature | Individual | Teams | Enterprise |
|---|---|---|---|
| SAML/OIDC SSO | No | Yes | Yes |
| Team-wide privacy settings | No | Yes | Yes |
| Usage analytics | No | Yes | Yes |
| SCIM seat management | No | No | Yes |
| Audit logs and service accounts | No | No | Yes |
| Group-level spend limits | No | No | Yes |
| Pooled usage | No | No | Yes |
| Invoice billing | No | No | Yes |
| US-only data residency | No | No | Yes |
| Priority support | No | No | Yes |
| Cursor Token Rate on third-party models | No | Yes | Yes |
The governance jump from Teams to Enterprise is larger than the jump from individual plans to Teams, since identity provisioning, audit trails, and group-level spend limits all sit at the Enterprise tier. Cursor holds a SOC 2 Type II attestation, with reports available on request.
Seat billing and plan changes
Cursor bills per active paid seat, so teams pay only for seats in use. Adding a member mid-cycle creates a pro-rated charge for the rest of the billing period. Upgrading a seat applies right away and charges the pro-rated difference, while downgrades take effect at the end of the billing period. A team needs at least one paid member, and Cursor publishes no other seat minimum.
Removing a member who used credits keeps the seat occupied until the cycle ends. Seat removals can create billing adjustments or credits, which appear on a future invoice. Renewal dates stay the same when members are added or removed. Self-serve plans accept card payments, while invoice and wire billing require Cursor Enterprise.
Cursor spend against delivery outcomes
Under these plans, each team's Cursor bill depends on how much its engineers use the tool. GitHub made a similar shift when Copilot moved to usage-based billing on June 1, 2026. Both Cursor and GitHub Copilot now bill model usage by token consumption, though each seat covers different usage. A Copilot seat includes AI Credits that match its price, while a Cursor seat's pool covers Cursor's own models only. The budget question follows directly: is higher Cursor spend buying more delivery, or just a bigger bill?
Answering it starts with connecting Cursor usage to delivery data. Cursor reports per-request usage and cost data through its Admin API, which is available on Teams or Enterprise plans. minware ingests that data alongside your version control system, such as GitHub, GitLab, Bitbucket, or Azure DevOps, and your project management system, such as Jira, Linear, Azure Boards, or GitHub Issues.
minware groups the combined data by team and time period by default. Each data point is normalized to per-person-day, so differences in team size don't distort the results.
Slope and R-squared readout
minware runs a linear regression of roadmap value delivery, on-time delivery rate, and overhead cost against token spend, one regression for each outcome. The slope of each regression is the return on investment (ROI) readout: the change in the outcome per additional dollar of token spend. The R-squared value shows how much of the outcome's variation the spend explains, so it belongs next to the slope in any board slide.
minware's AI impact reports charts each regression with its slope and R-squared value. The underlying data exports to CSV for board reviews. Reported token spend can differ from the amount actually invoiced for usage covered by a plan's included pool.
Confounders and same-team trends
A slope from observational data still needs its confounders named. Engineers reach for AI on work where it is likely to help (task-level selection), and early adopters are often already the strongest performers (person-level selection). Covariates such as code base age or code quality can also drive both Cursor use and delivery outcomes.
The supporting check is each outcome's trend over time for the same team as AI maturity increases. minware's AI impact reports track that trend without needing a clean pre-rollout snapshot. Bug rate and cycle time act as guardrails on the trend. If either rises as Cursor spend climbs, the extra usage may be creating quality problems or a review bottleneck further down the pipeline.
Cost attribution and spend projections
minware attributes human and AI costs to each commit. It then rolls those costs up to pull requests, tickets, and epics through its patented hypercube data model, which links data across every connected source. The model connects agent sessions to the commits and tickets they belong to by modeling what each person was working on at any given time. Costs roll up by team, or by division or cost center on minware's Enterprise plan.
For next year's budget, project Cursor spend as seat cost plus usage, modeling the number of seats and the average usage spend per seat separately. Seat count follows adoption, while usage spend follows agent session length and model choice. Revisit the projection each quarter against the regression slope, so the budget conversation runs on evidence from your own teams.
Cursor pricing takeaways for engineering leaders
Cursor's seat price now sets the minimum bill. The total depends on how much third-party model usage each team runs, plus the Cursor Token Rate on Teams and Enterprise. Teams covers single sign-on plus centralized billing, while SCIM, audit logs, and data residency require Cursor Enterprise. Legacy subscribers should compare their third-party usage against API list pricing before switching. Whichever plan you choose, regressing delivery outcomes against Cursor spend tells you whether the bill is buying delivery.
minware's Professional plan costs $25 per contributor per month with no seat minimum, while minware's Enterprise plan costs $45 per contributor per month with a 50-seat minimum. Start a 14-day free trial at minware.com, no credit card required, to connect Cursor, version control, and project management data. You can explore the pre-built AI impact reports with your own data before talking to anyone on our team.
FAQs
How much does Cursor cost per user in 2026?
Cursor's individual plans cost $0, $8, $30, $100, or $200 per month as of this writing. Teams charges $30, $100, or $200 for each paid seat per month depending on the tier, and Cursor Enterprise pricing is custom. Third-party model usage, such as Claude or GPT requests, is billed on top at API list price on every plan from Premium up, including Teams and Cursor Enterprise.
What's the minimum seat count for Cursor Teams and Enterprise?
Cursor requires one paid member to set up a team and lists no larger seat minimum for Teams. Cursor Enterprise is sold through Cursor sales, and Cursor doesn't publish a seat minimum for it.
Can I switch between Cursor plans mid-contract?
Yes. A seat upgrade takes effect immediately with a pro-rated charge, while a downgrade applies when the current billing period ends. Subscribers on legacy plans can keep them or switch to The X Subscription, though included third-party usage on a legacy plan ends at the switch.
Does Cursor charge for inactive seats?
Cursor charges teams only for active paid seats. If a member who used credits is removed, the seat stays billed until the cycle closes, and any resulting adjustment or credit lands on a future invoice.
How does Cursor pricing compare to GitHub Copilot?
The seat prices don't compare directly, because each seat covers different usage. Copilot Business and Copilot Enterprise include monthly AI Credits that match the seat price, spent on model usage at published per-model rates. A Cursor seat includes a weekly pool for Cursor's own models only. Claude, GPT, or Gemini requests in Cursor bill at API list price from the first request, with no included credit to draw on. minware connects each tool's spend to delivery outcomes, so the regression slope shows which one returns more delivery per dollar.
Key terms glossary
Bring your own key (BYOK): A billing arrangement where an organization supplies its own model provider API keys and pays the provider directly. On Cursor Teams and Cursor Enterprise, the Cursor Token Rate still applies on top.
Bug rate: A quality metric measuring the number of bugs created divided by the number of code changes, by default the number of pull requests merged into a main branch.
Cursor Token Rate: A $0.25 per million token charge Cursor adds to third-party model requests on Teams and Cursor Enterprise plans, on top of the model provider's API price. Auto's Cost mode and Cursor's own models are exempt.
GitHub AI Credits: The unit GitHub has billed Copilot usage in since June 2026. One credit is one cent, consumed against token usage at published per-model rates.
Hypercube data model: minware's patented data model that links every entity from every data source, so any metric can be broken down by any dimension.
Linear regression: A statistical model charting the best-fit line between an outcome metric and an input variable. It is the primary AI ROI methodology. It fits a line through token spend and a delivery outcome metric. Data points are grouped by team and time period. Each regression fits one metric pair, so correlating spend against multiple outcomes requires a separate regression for each.
On-time delivery rate: The estimated roadmap item duration (time from when a roadmap item is marked in progress until the original due date set at that time) divided by the actual roadmap item duration (time from in progress until it is marked done), capped at 100% per roadmap item. By default, minware treats each epic as a roadmap item, and this can be configured to use higher-level tickets instead.
OpenID Connect (OIDC): An identity protocol for single sign-on, built on top of OAuth 2.0.
Overhead cost: Personnel cost and AI token spend that goes toward work not counted in roadmap value delivery, i.e. cost not traceable to any ticket, or traceable to a ticket excluded from roadmap value delivery (by default, a bug ticket or a ticket with no parent epic/project ticket).
R-squared: In a regression chart, the share of the outcome metric's variation explained by the input variable, on a 0-to-1 scale.
Regression slope: The change in an outcome metric per unit change in the input variable, such as story points completed per dollar of token spend.
Roadmap value delivery: The expected value of completed work items. Configurable to any project management field where a team sets explicit value estimates during roadmap planning, or to a custom spreadsheet upload. If no explicit value field is configured, defaults to story points completed on tickets that are not bugs and have a parent epic/project ticket, with 1 point assigned per ticket if no estimate is set.
Security Assertion Markup Language (SAML): A standard protocol for single sign-on that lets users authenticate through their organization's identity provider.
SOC 2 Type II: An independent audit report attesting that a service organization's controls operated effectively over a defined period.
System for Cross-domain Identity Management (SCIM): An open standard for automating user provisioning between an identity provider and an application.
Token spend: The dollar cost of AI tool usage, as reported by AI tool APIs or OpenTelemetry. On flat-rate, tiered, or discounted plans, reported spend may differ from the amount actually invoiced.
Usage-based billing: A billing model where costs scale with consumption. In AI coding tools, this typically means token-based charges for model usage on top of a seat price.