Cursor Pricing Explained: Free, Individual $20, Teams $40 (2026)
Last verified: June 9, 2026 · Format: Breakdown · Voice: Practitioner
If you are weighing Cursor, the question is not just the headline price. It is what each tier actually buys, how the usage-based billing behaves once you pass the included amount, and whether the old "500 requests" number you may have read still applies. This breakdown walks through all four plans, the billing model, and the trade-offs, using figures verified against Cursor's own pricing page on June 9, 2026. Where the pricing page does not publish a specific number, this article says so rather than guessing.
The Short Answer
Cursor sells four plans, and the jump between them is mostly about usage volume, team controls, and governance, not a different editor. Hobby (Free) needs no credit card and gives you a limited number of Agent requests plus limited Tab completions, which is enough to try the tool. Individual ($20/mo) is the working developer plan: extended Agent limits, access to frontier models, MCPs, skills and hooks, cloud agents, and Bugbot on usage-based billing. Teams ($40/user/mo) adds the admin, single sign-on, and analytics that organizations need. Enterprise (custom) layers on pooled usage, provisioning, and access controls.
Here is the honest framing. The Individual tier is described on the pricing page at $20 per month and contains Pro, Pro+, and Ultra options. Cursor publishes the $20 entry price but does not list distinct Pro+ and Ultra prices in the sources used here, so this article will not invent them. If you want the higher Individual tiers, check the current figures at cursor.com/pricing. For the wider landscape, the AI Tools Hub covers the rest of the catalog.
All figures here are vendor-reported and verified against cursor.com/pricing on June 9, 2026. Cursor adjusts plans, tiers, and included usage periodically. Re-check the current numbers at cursor.com/pricing before you subscribe.
How Usage Billing Works Before You Pick a Plan
You cannot read Cursor's pricing correctly without the billing model, because the plan price is only the first part of what you pay. Every plan includes a set amount of model usage. Once you consume that included usage, on-demand usage continues and is billed in arrears, which means you are charged after the usage happens rather than paying a fixed amount up front. The plan fee buys the baseline; the on-demand charges sit on top when you go past it.
The part that surprises new subscribers is the metering. Because heavier use of Agent and frontier models draws down the included amount faster, two developers on the same plan can land on different bills depending on how aggressively they run the agent. Self-serve plans (Hobby, Individual, Teams) take major credit cards, while Enterprise is invoiced. Cursor is sold only at cursor.com, so there are no resellers or third-party license keys to compare against.
So when you compare plans, separate two things: the monthly fee and the usage that fee includes. A solo developer who runs the agent constantly may pay more in on-demand than the base fee, while a lighter user may never touch the overage. The plan you choose sets your included budget and your controls; your actual bill depends on how much model usage you draw.
The Four Plans, Card by Card
Here is every plan with the figures Cursor publishes as of June 9, 2026. Where a tier exists but its exact price is not on the pricing page, the card says so and points to cursor.com/pricing rather than stating a number.
- Limited Agent requests
- Limited Tab completions
- Good for evaluating the editor
- Exact request counts not published
- No commercial team controls
- Extended Agent limits
- Access to frontier models
- MCPs, skills, and hooks
- Cloud agents
- Bugbot on usage-based billing
- Pro+ / Ultra prices: see cursor.com/pricing
- Everything in Individual
- Centralized billing and admin
- Team marketplace: rules, skills, plugins
- Agentic Bugbot code reviews
- Cloud agents plus shared team context
- Usage analytics
- Team-wide privacy mode
- SAML / OIDC SSO
- Everything in Teams
- Pooled usage
- Invoice / PO billing
- SCIM provisioning
- Repo / model / MCP access controls
- Auto-run, browser, network controls
- Audit logs and service accounts
- AI code tracking API
Only the $20 (Individual) and $40 (Teams) figures appear as exact prices on the pricing page. Pro+, Ultra, Standard, and Premium tier prices are not listed in the sources used here. Figures verified June 9, 2026, per cursor.com/pricing.
Plan Comparison Table
The same details, lined up so you can scan across. Scroll the table sideways on a narrow screen.
| Feature | Hobby | Individual | Teams | Enterprise |
|---|---|---|---|---|
| Price | Free | $20/mo | $40/user/mo | Custom |
| Tier options | n/a | Pro / Pro+ / Ultra | Standard / Premium | Contact sales |
| Credit card to start | No | Yes | Yes | Invoice / PO |
| Agent requests | Limited | Extended limits | Extended limits | Pooled usage |
| Tab completions | Limited | Yes | Yes | Yes |
| Frontier models | Limited | Yes | Yes | Yes |
| MCPs, skills, hooks | No | Yes | Yes | Yes |
| Cloud agents | No | Yes | Yes | Yes |
| Bugbot code reviews | No | Usage-based | Agentic reviews | Agentic reviews |
| Team-wide privacy mode | No | No | Yes | Yes |
| SAML / OIDC SSO | No | No | Yes | Yes |
| SCIM provisioning | No | No | No | Yes |
| Access controls (repo/model/MCP) | No | No | No | Yes |
| Audit logs + AI code tracking API | No | No | No | Yes |
All values vendor-reported and verified June 9, 2026, per cursor.com/pricing. Exact request counts for Hobby and prices for the Pro+, Ultra, Standard, and Premium options are not published in the sources used here.
The "500 Requests" Story, and Why It No Longer Applies
If you searched Cursor pricing a while ago, you probably saw the phrase "$20 Pro gets you 500 requests." That number is the single most common stale fact about Cursor pricing, so it is worth being precise. It does not describe the current plan. In July 2025 Cursor changed the older fixed-request arrangement to a usage-metered cap. That change drew complaints from users about surprise charges, and Cursor rolled it back and issued refunds.
The takeaway for anyone budgeting today is simple: do not plan around a flat "500 requests" figure, because it is not how the plan works now. The current shape is the included-usage-plus-on-demand model described above. Each plan bundles a set amount of model usage, and once that is consumed, on-demand usage continues and is billed in arrears. For the current numbers behind your specific tier, the authoritative source is the pricing page itself.
Do not budget around "500 requests." That figure was part of a July 2025 change that was reversed after user complaints, with refunds. Today, plan your spending around included model usage plus on-demand overage billed in arrears, and confirm the current allotments at cursor.com/pricing before committing.
Which Plan Is Actually For You
Match the plan to the job and the org structure, not to the longest feature list. Here is who each tier is built for.
You want to try the agent-native editor before paying. Hobby's free Agent requests and Tab completions are enough to judge whether Cursor fits your workflow, with no card on file.
Hobby (Free)You code daily and want extended Agent limits, frontier models, MCPs, and Bugbot. Individual at $20 is the working baseline; daily agent users may want the higher Individual options.
Individual ($20/mo)You need shared billing, SSO, usage analytics, agentic Bugbot reviews, and a team-wide privacy mode. Teams at $40 per user adds the admin layer a group needs.
Teams ($40/user/mo)You require pooled usage, SCIM, access controls over repos and models, audit logs, and an AI code tracking API. Enterprise is the tier built for governance and procurement.
Enterprise (custom)The most common mistake is a team buying many Individual seats to save money, then discovering it needs centralized billing, SSO, and a team privacy mode that only land on Teams. If more than a couple of developers share the tool, the admin and governance features usually justify the move to Teams. Save Enterprise for when provisioning, access controls, and audit logging become procurement requirements rather than conveniences.
Watch-Outs Before You Subscribe
None of these are dealbreakers, but they are the things that surprise people after they subscribe.
Past the included amount, on-demand usage continues and you are charged after the fact. Heavy agent use can push your real bill above the plan fee, so watch usage if cost predictability matters to you.
Hobby advertises limited Agent requests and Tab completions, but Cursor does not list the precise numbers on its pricing page. Treat the free tier as an evaluation budget, not a fixed quota you can plan a project around.
The fixed 500-request figure was changed in July 2025 and then rolled back after complaints. Budgeting around it will mislead you. Plan around included usage plus on-demand overage instead.
With Privacy Mode on, Cursor guarantees your code is not used for training by Anysphere or its model providers. Storage and retention specifics are not covered here; check Cursor's Security page for the full data handling picture.