How Much Does Cursor Cost per Developer per Month?

TL;DR: Cursor's per-developer cost has two parts: the seat price, covered in this plan-by-plan Cursor pricing breakdown, and the additional usage on top of it. Additional usage covers third-party models plus Cursor-model usage past the weekly pool, and it draws from a prepaid balance. Third-party requests on Teams also carry a per-token Cursor Token Rate. A 30-day pilot gives the usage figure, which varies most with how often engineers run agents. The cost question that matters more is whether token spend correlates with business outcomes such as roadmap value delivery, which minware measures.

New Cursor customers now start on The X Subscription, a bundled plan that covers Grok, X, and Cursor, with Grok and Cursor sharing one weekly usage pool. Existing accounts on legacy plans such as Pro and Teams Standard can keep them. The seat price is only the starting point, because third-party models and Cursor-model usage past the weekly pool raise the real per-developer figure as agent use grows.

For an engineering leader building a budget, the per-developer figure has two parts: the seat price and the usage on top of it. This guide covers both, then compares Cursor with GitHub Copilot and shows how to connect the spend to business outcomes.

Comparing Cursor plans and seat tiers

Cursor publishes its plan prices, with Enterprise priced through sales. For each plan's price and what it includes, see Cursor Pricing 2026: Individual, Teams, and Enterprise Plans Compared. Each plan includes a usage pool for Cursor models, and usage beyond it decides how far the real cost rises above the seat price.

Plan	Usage included	SSO	System for Cross-domain Identity Management (SCIM)
Free	Limited	No	No
Plus	Weekly Cursor-model pool	No	No
Premium	Weekly Cursor-model pool, third-party models at API price from prepaid credit	No	No
Super	Larger weekly pool, third-party models at API price	No	No
Ultra	50x Plus usage, third-party models at API price	No	No
Teams	Same weekly usage as the matching individual plan	Yes	No
Enterprise	Pooled usage	Yes	Yes

Individual and Teams plans

Individual plans run from Free through Plus, Premium, and Super to Ultra. Cursor also offers annual billing on paid individual plans at a discount to monthly payments.

Teams is priced per seat, and each seat is Premium, Super, or Ultra. Each seat carries the same price and weekly usage as the matching individual plan. One team can mix tiers, so light users can sit on Premium while the heaviest agent users get Super or Ultra seats. Teams adds SAML/OpenID Connect (OIDC) SSO at no additional cost, centralized billing, usage analytics, and team-wide privacy mode.

Enterprise and legacy plans

Enterprise is priced through Cursor's sales team, which is also the route to invoice billing and wire transfers. Cursor recommends Enterprise for teams that need priority support, pooled usage, invoicing, or SCIM. Cursor lists the Enterprise price as custom, so any volume discount comes out of that negotiation.

Before The X Subscription, Cursor's plans included Hobby, Start (India only), Pro, Pro+, Ultra, and Teams. Legacy Teams seats come in Standard and Premium tiers. Teams accounts created before The X Subscription keep these seats, with the option to add seats or change seat types.

When someone joins a legacy Cursor team, their individual legacy plan is canceled automatically. Joining a team on The X Subscription leaves a personal plan in place.

Estimating monthly cost by team size

Seat cost scales linearly with headcount, while usage cost scales with how heavily each engineer runs agents. Cursor bills Teams per active paid seat, so the monthly seat cost is each tier's seat price times the number of seats on that tier. Cursor recommends Premium for new agent users and Super for daily agent users. A team where most engineers run agents every day needs more Super seats, which raises the per-developer average.

Additional usage comes on top of the seat cost. Third-party models draw from prepaid credit at API list price plus the Cursor Token Rate on Teams. Cursor-model usage past the weekly pool draws from the same balance at Cursor's model rates. Larger teams that need pooled usage or invoicing can move to Cursor Enterprise, priced through Cursor's sales team.

Budgeting for additional usage

Additional usage is the part of the bill that moves month to month. Two mechanics set it: how Cursor splits Cursor models from third-party models, and the extra rate Teams pays on third-party requests.

Included usage and the Cursor Token Rate

On The X Subscription, each plan includes one weekly usage pool for Cursor models such as Composer 2.5 and the Grok family. Third-party models sit outside that pool. Premium and higher plans can use them at API list price, paid from prepaid credit.

On Teams and Enterprise, third-party requests also carry a Cursor Token Rate on top of API pricing, including bring-your-own-key usage. Cursor models are exempt from that rate.

Additional usage, often called overage, draws from a prepaid balance. It stops when the balance runs out or a team hits its monthly additional usage limit. Legacy plans bill on-demand usage monthly in arrears instead.

Usage estimates from a pilot group

Under Cursor's legacy plans, daily agent users typically spent $60 to $100 a month in total, while power users running several agents often passed $200. Treat these as a rough guide for The X Subscription, and estimate your own figure from a pilot group's first 30 days of usage.

Include engineers who run agents daily in the pilot, since their usage sets the upper end of the range. Cursor's admin dashboard shows aggregate spend and per-user usage, which gives the pilot its numbers. Divide the pilot's monthly additional usage spend, third-party models plus any Cursor-model usage past the weekly pool, by its headcount to get the usage figure for the annual cost formula.

Weighing Cursor against GitHub Copilot on cost

Cursor and GitHub Copilot both charge per seat, but their pricing structures differ, as do the features each tier includes. The seats also include different usage. Copilot Business and Copilot Enterprise include monthly AI Credits that match the seat price, spent on model usage. A Cursor seat's weekly pool covers Cursor's own models only, so Claude, GPT, or Gemini requests bill at API list price from the first request. For both tools, the return on investment (ROI) question is the same: does the spend correlate with business outcomes?

Code completions in Copilot don't use credits, and admins can allow usage past the included credits at published rates. Because one seat includes credits and the other doesn't, comparing seat prices alone doesn't show what each team will pay for model usage.

On features, Copilot Pro includes code completion and chat, while Copilot Business adds organization-wide policy management. Copilot Enterprise, available to organizations on GitHub Enterprise Cloud, adds priority access to new models and features.

Calculating annual cost per developer

Annual cost per developer = (Seat price × 12) + (Monthly additional usage × 12)

Where:

• Seat price = your Teams seat tier's monthly price from Cursor's pricing page, or your negotiated Cursor Enterprise rate

• Monthly additional usage = your pilot group's measured spend per developer on third-party models and on Cursor models past the weekly pool

Engineering time sits outside the formula: training, workflow adjustments, and the work needed to show whether the spend moved delivery metrics. Showing that means connecting Cursor usage data to 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. Building that pipeline in-house is a large upfront project, and someone then has to maintain it as vendor APIs change.

Connecting Cursor spend to delivery outcomes

The pricing question comes down to seat price plus measured usage. The harder question is whether the spend is buying more delivery, or just a bigger bill. Your board or leadership team will ask it, and minware is built to answer it.

Token spend against business outcomes

minware ingests Cursor usage data through Cursor's Admin API, which returns token consumption and cost for each usage event. Cursor's Teams and Enterprise plans include the Admin API. minware's patented hypercube data model connects those usage events to commit history and ticket progression without a custom data pipeline.

minware runs a separate linear regression of each business outcome against token spend across teams and time periods. The three outcomes are roadmap value delivery (story points completed by default), on-time delivery rate, and overhead cost. The slope of each regression is the ROI readout, such as the change in story points completed per additional dollar of token spend.

Name the confounders when reading a slope: engineers reach for AI on work where it is likely to help, and early adopters are often already the strongest performers. Read with those in mind, the regression gives a spend-to-outcome relationship that holds up better than a before-and-after comparison.

Cursor seats include a weekly usage pool, so the token spend Cursor reports can differ from the amount on your invoice. Where those differ, minware can multiply reported spend by your total bill divided by total reported spend, reflecting the average discount across the team.

Usage data linked to delivered work

Cursor's admin dashboard tracks acceptance rates, AI-generated commit attribution, and token spend, but it doesn't map those costs to the epics or roadmap initiatives they delivered. Usage telemetry on its own shows how much engineers use Cursor and how much code it contributed. Mapping that usage to ticket and roadmap data is what shows whether it produced delivery outcomes.

minware's relationship recovery, the harder half of entity resolution, links agent sessions to commits, pull requests, and tickets, so you can see which sessions produced deliverable work. Because those links are recovered from activity data, analysis can start before every branch is tied to a ticket. Data normalization puts Cursor usage into the same model as other AI tools, so teams running Cursor and Copilot can see both in one report.

Pre-built reports and trial access

minware Professional is $25/contributor/month with no seat minimum, and the 14-day trial is self-serve with no credit card required. You can connect your Cursor data and explore the pre-built AI impact reports before talking to anyone on our team. When a question needs a new or adjusted report, customer success typically handles it within a single call and about 24 hours.

"What I like best about minware is its flexibility. The platform comes with a great set of engineering reports out of the box, so you can start getting value immediately. At the same time, those reports are highly customizable, and minQL makes it possible to build your own metrics and dashboards tailored to your team's workflow rather than being limited to predefined reports." - Verified user on G2

Putting the Cursor budget in context

Cursor's per-developer cost comes down to the seat price plus additional usage, which varies most with how often engineers run agents. A 30-day pilot gives the usage figure the budget needs. The board's follow-up question is whether that spend bought more delivery, which a regression of roadmap value delivery against token spend answers.

Start a 14-day free trial at minware.com, no credit card required, and connect your Cursor data to see token spend correlated against business outcomes.

FAQs

Does Cursor offer a free tier?

Yes. Cursor's Free plan costs $0, with Agent and Chat at limited usage. Cloud agents, AI code reviews through Bugbot, code hosting through Origin, and third-party models are not included.

Can I mix seat tiers on one Cursor Teams account?

Yes. A Teams account on The X Subscription can mix seat tiers, for example three Premium seats and one Super seat. Accounts created before The X Subscription keep their Standard ($40) and Premium ($120) seats, with the option to change seat types.

What happens when I use up my included usage?

Cursor draws further Cursor-model usage from your prepaid balance at Cursor's model rates. Third-party models bill from the same balance from the first request, at API list price. Usage stops once that balance is empty or the team reaches its monthly additional usage limit. On legacy plans, on-demand usage is billed monthly in arrears instead.

Is there a discount for annual billing?

Yes, on individual plans. Annual billing for Premium costs $300 a year against $360 billed monthly, and Ultra costs $2,000 a year against $2,400.

How does Cursor pricing scale for large teams?

Seat costs scale linearly, at $30 per engineer per month on Premium Teams seats. Cursor prices Enterprise through its sales team and recommends it for teams that need priority support, pooled usage, invoicing, or SCIM.

Key terms glossary

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.

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, fitting a line through token spend and a delivery outcome metric across teams and time periods. Each regression fits one metric pair, correlating spend against multiple outcomes requires a separate regression for each.

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.

Business outcomes: The metrics boards, CEOs, and CFOs use to judge AI's impact, covering value (roadmap value delivery and on-time delivery rate) and cost (roadmap delivery cost and overhead cost).

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.

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.

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).

Relationship recovery: Linking commits, tickets, pull requests, and AI agent sessions that carry no structured connection between them. The harder half of entity resolution, and the subject of minware's patent.

SSO (Single Sign-On): An authentication method that lets users log in to multiple applications with one set of credentials. Cursor Teams and Enterprise plans include SAML 2.0 SSO at no additional cost.

SCIM: System for Cross-domain Identity Management, an open standard for automating user provisioning between an identity provider and an application.

Additional usage: Cursor's term for third-party model usage plus Cursor-model usage past a seat's weekly pool, often called overage. On The X Subscription it draws from a prepaid balance. Third-party requests on Teams and Enterprise also carry a $0.25 per million token rate.