Cursor Pricing 2026: Hobby, Pro, Teams & Usage Costs

Cursor pricing in 2026 has two layers: the subscription and the model usage behind Agent work. The public plans are simple—Hobby Free, Pro $20, Pro+ $60, Ultra $200, Teams Standard $40 and Teams Premium $120—but total cost can be higher when developers use expensive third-party models, on-demand usage or Bugbot at scale.

Cursor also now has a separate India-only Start plan at ₹649 per month including tax. It is intentionally narrower than Pro: Start focuses on Cursor's own model pool and Cloud Agents, while Pro and higher add access to the Other Models pool, on-demand usage, Bugbot, Auto, Automations and the Cursor SDK.

Cursor pricing at a glance

Hobby: Free

Hobby is Cursor's permanent free plan. It does not require a credit card and provides limited Agent requests plus access to Composer. It is the correct way to evaluate the editor before paying.

Hobby is suitable for occasional experimentation, small personal projects and developers who mainly want to understand Cursor's interface. It becomes restrictive when Agent work, Cloud Agents or sustained Tab usage becomes part of daily development.

Start: ₹649/month in India

Start is available only to developers in India and costs ₹649 per month including tax. It is billed monthly in INR and supports UPI, credit card and debit card.

The plan includes the Cursor Models pool, Cloud Agents, Cursor for iOS, plugins, MCP servers, hooks and skills. Current documentation says Start does not include the Other Models pool, on-demand usage, Bugbot, Auto, Automations or the Cursor SDK.

That makes Start a strong low-cost plan for developers comfortable using Cursor's first-party model pool. It is not a substitute for Pro when access to OpenAI, Anthropic, Google or other third-party frontier models inside Cursor is a requirement.

Pro: $20/month

Pro is the mainstream global individual plan. It includes unlimited Tab completions, expanded Agent limits, access to frontier models, Grok Bot, MCP, skills, hooks, Cloud Agents and access to Bugbot through usage-based billing.

Cursor advertises a 20% saving with yearly billing on eligible self-serve plans. Because the exact checkout amount can vary with region, currency and tax handling, SearchSagar uses the live monthly price as the primary comparison point and treats the annual percentage as the verified discount.

Who should choose Pro?

Pro fits developers who use Cursor most days but do not run long agents continuously. It is also the right baseline for comparing Cursor with Claude Code, GitHub Copilot and Devin Desktop because those tools have mainstream paid tiers near the same $10–$20 monthly range.

Pro+: $60/month

Pro+ costs $60 per month and includes roughly three times Pro Agent limits. Cursor currently recommends Pro+ for daily Agent users. It retains access to the same broad feature set while increasing capacity.

The jump from $20 to $60 should be justified by real usage. A developer who rarely reaches Pro limits will not gain much from paying triple. A developer who regularly pauses work because Agent capacity is exhausted can recover the difference in productivity.

Ultra: $200/month

Ultra costs $200 per month and includes roughly twenty times Pro Agent limits. It is designed for Agent power users and includes priority access to new features.

Cursor's own usage guidance says power users running multiple agents or automations often consume more than $200 per month in total usage. Ultra therefore makes the most sense when high Agent volume is already proven, not as a speculative upgrade.

Cursor Models and Other Models pools

Pro, Pro+ and Ultra include two usage pools. The Cursor Models pool covers Cursor-selected models such as current Grok and Composer-family options. The Other Models pool covers third-party frontier models and consumes usage according to their API prices.

Different models can burn through the allowance at very different rates. A cheaper model used for routine implementation can preserve budget, while a high-cost reasoning model across a large repository can consume capacity quickly. Cursor exposes the pools separately in the usage dashboard so developers can see where spend is going.

On-demand usage

Once included usage is exhausted, users can continue with on-demand billing. Cursor says additional individual requests are billed at API rates with no markup. Teams and Enterprise can have additional token-rate mechanics for third-party models.

Individual on-demand usage must be explicitly enabled. Teams have it enabled by default, but admins can disable it and set spending limits. On-demand charges appear as separate invoice line items from the base subscription.

Teams Standard: $40/user/month

Teams Standard costs $40 per user per month. Cursor's June 2026 pricing update states that annual plans cost $32 per user per month. The seat includes centralized billing, team administration, shared rules/skills/plugins, cloud agents with shared context, Bugbot, usage analytics, privacy-mode enforcement and SAML/OIDC SSO.

Standard includes separate first-party and third-party model usage pools. Cursor redesigned the plan in 2026 to provide more first-party usage and better spend visibility without increasing the $40 monthly price.

Teams Premium: $120/user/month

Premium costs $120 per user monthly or $96 annual-equivalent. It includes roughly five times Standard usage and is aimed at the small group of engineers who drive the majority of Agent consumption.

Teams can mix seat types. This is important for cost control: a company can keep most developers on Standard and assign Premium only to heavy Agent users instead of paying $120 for every engineer.

Enterprise: custom

Enterprise adds pooled usage, invoice and purchase-order billing, SCIM seat management, repository/model/MCP access controls, Auto-run, browser and network controls, audit logs, service accounts, an AI code-tracking API and priority support.

Pricing is custom. Enterprise buyers should request a full model of seat pricing, included model usage, on-demand rates, regional data residency, support, implementation and security controls rather than comparing only the subscription label.

Bugbot pricing

Bugbot moved from a seat add-on to usage-based billing in 2026. Current documentation says the cost depends on pull-request size, complexity and review effort. Cursor's transition announcement cited an average historical run around $1 to $1.50, but actual cost can differ.

Bugbot effort settings let teams trade cost and time for review depth. Low or default effort can reduce spend, while high effort spends more reasoning budget. Teams should monitor Bugbot separately from Agent usage because it can become a meaningful line item when every pull request is reviewed automatically.

Yearly billing

Cursor's live pricing page advertises 20% savings with yearly billing. Team annual prices are explicitly documented at $32 for Standard and $96 for Premium. Individual exact annual checkout totals can vary by regional billing and taxes, so buyers should confirm the final amount in the billing dashboard.

Annual billing is best after usage is stable. A developer who is still deciding between Pro and Pro+ benefits from monthly flexibility, while a team with predictable seat assignments can capture the annual discount more safely.

Refund policy

Pro, Pro+ and Ultra use the same current refund rules for monthly and annual plans. A user may qualify for a refund of the most recent subscription payment when the charge was within 14 days and the subscription has not been used during that billing period.

Outside that window, or after usage during the period, the charge is generally non-refundable. Cursor also states that consumed on-demand and fast-request charges are not refundable.

Cancellation

Paid plans renew automatically unless canceled before renewal. Canceling stops future charges but does not automatically refund a processed payment. Access continues through the current paid period, then the account returns to Hobby.

Teams should also disable or cap on-demand usage where necessary before reducing seats, because usage charges and subscription charges are separate billing components.

Regional data residency and other costs

Cursor's Models & Pricing documentation says eligible regional data residency can add a 10% uplift to model pricing. This is relevant for organizations that require specific data-location controls.

Other potential costs include on-demand model usage, Bugbot, third-party model token rates on Teams/Enterprise, taxes on non-Start plans and any external MCP or cloud services triggered by agents.

Cost scenarios for different Cursor users

A developer who mainly uses Tab completion and a few Agent tasks each day is likely to get the most value from Pro because the $20 base subscription covers the full paid feature set without committing to power-user capacity. If usage consistently expands into long repository sessions, several agents running in parallel or expensive frontier models, Pro+ becomes easier to justify.

A developer on Pro who adds $20 to $30 of on-demand usage occasionally can still spend less than a permanent Pro+ subscription. The opposite becomes true when overage is routine and interruptions or spend monitoring become a weekly concern. Ultra should be treated as a high-capacity professional tier for users who already know they need sustained Agent volume.

For organizations, the mixed-seat model is important. A 50-person engineering group may have only five to ten developers who run intensive agents all day. Assigning Premium seats only to those users can provide substantially better economics than putting the whole organization on the highest-capacity seat.

How model choice changes the bill

Cursor's pricing is unusual because two users on the same plan can consume very different amounts. One developer may rely heavily on Composer and Cursor Models, while another repeatedly selects expensive third-party reasoning models over large repositories. Both pay the same base subscription, but the second user can exhaust included capacity faster.

This makes model policy a real budgeting tool. Teams can define which models are appropriate for routine implementation, deep planning, code review and high-stakes debugging. Enterprise controls can also restrict model access. A sensible default model can lower cost without blocking engineers from escalating to a stronger model when the task actually needs it.

How Cloud Agents affect cost

Cloud Agents can create more value from a subscription because they work in parallel and do not occupy the developer's local machine, but they can also increase usage rapidly. A developer who delegates three independent tasks at once is effectively running several AI engineering sessions in parallel.

Organizations should pair Cloud Agent adoption with usage alerts and task-quality metrics. If agents routinely produce mergeable pull requests, higher spend can be economical. If they often create abandoned branches or require extensive rework, the problem is workflow quality rather than insufficient plan capacity.

Annual billing decision

Cursor advertises a 20% yearly saving, but annual billing should follow plan stability. A developer uncertain whether Pro is enough should stay monthly until two or three normal development cycles reveal the real usage pattern. Locking into Pro and immediately needing Pro+ reduces the value of the annual discount.

Teams have clearer published annual rates: $32 for Standard and $96 for Premium. Before annualizing, administrators should review which users genuinely need Premium and whether expected headcount is stable enough to justify the commitment.

How to choose the right Cursor plan

Hobby: evaluate the product. Start: low-cost India option for Cursor Models. Pro: most individual developers. Pro+: daily Agent users. Ultra: sustained multi-agent or automation-heavy usage. Teams Standard: managed organizational rollout. Teams Premium: heavy Agent users inside teams. Enterprise: organizations requiring pooled usage, procurement and deeper security controls.

Cursor pricing versus alternatives

Claude Code is included with Claude Pro at $20 per month and Max at $100 or $200, while Team Standard/Premium cost $25/$125 monthly or $20/$100 annually. GitHub Copilot Pro starts at $10, Pro+ $39 and Max $100, with GitHub AI Credits governing chat and agent usage. Devin Desktop, formerly Windsurf, lists Free, Pro $20, Max $200 and Teams at $80 per month plus $40 per full seat.

Cursor Pro therefore sits at the mainstream $20 price point, but Cursor differentiates through its editor-native workflow and model choice. GitHub Copilot is cheaper at entry level, Claude Code is bundled with the broader Claude subscription, and Devin Desktop emphasizes multi-agent coordination.

Final pricing verdict

Cursor has a sensible price ladder, especially now that Start gives Indian developers a lower-cost route and Teams can mix Standard and Premium seats. Pro remains the best default for most individual developers.

The important caveat is usage. Cursor is not a simple unlimited $20 product. Model choice, Agent intensity, Bugbot and on-demand billing determine real cost. Buyers who monitor the dashboard and set spend limits can keep that flexibility under control.

Frequently asked questions