Cursor Pricing Explained (Every Plan Broken Down)

Every plan, broken down

Cursor has four tiers, and only two of them have a fixed public price. Hobby is free with no credit card required, giving limited Agent requests. Pro is $20/mo and extends Agent limits, adds frontier model access, and includes cloud agents. Teams (Standard) is $40/mo per user and adds SSO, centralized billing, usage analytics, and team privacy mode on top of everything Pro includes. Enterprise has no public price, offering custom pricing with pooled usage, SCIM, and audit logs.

Because Cursor is a fork of VS Code, every tier — including free — carries over your existing extensions and keybindings, so the pricing tiers only gate Agent capability and administrative features, not the base editing experience.

What the free tier actually gets you

The Hobby tier gets you the real Cursor product, not a stripped-down demo: multi-file agent edits across your repository, the core feature of the whole platform, are available on Hobby, just with limited Agent requests compared to paid tiers. No credit card is required, so there's zero financial commitment to test whether agentic editing actually changes your workflow.

What Hobby doesn't include is frontier model access or cloud agents, both of which are Pro features, and the limited Agent request allowance means Hobby suits evaluation and light use rather than being a daily driver for heavy agent-based development. If you're trying to understand what an AI coding agent actually does before committing to any paid tier, our what is an AI coding agent guide is a good starting point.

Where the cost jumps

The first real jump is from Hobby's free tier to Pro's $20/mo, which unlocks extended Agent limits, frontier model access, and cloud agents — the difference between light evaluation and genuine daily use. The second jump, from Pro to Teams (Standard) at $40/mo per user, doubles the per-seat cost specifically to add SSO, centralized billing, usage analytics, and team privacy mode — administrative and security features that matter for a company, not an individual.

The cost that catches people off guard, though, isn't a tier jump at all: Bugbot code review is billed as usage on top of whatever plan you're on, so it doesn't show up in the flat monthly price. A team that enables Bugbot broadly should expect that usage charge to add to the base $20 or $40 per-user subscription, not replace it. Beyond Pro, there's no published intermediate individual tier, so a developer whose Agent use outgrows Pro's extended limits has no smaller step up before Teams or a custom Enterprise arrangement.

Is it worth it?

For an individual developer, Cursor's value case rests on whether multi-file agent editing actually saves you time worth more than $20/mo — and because Hobby is free and requires no credit card, you can answer that question with a real trial before paying anything. The VS Code fork lineage means the switching cost is lower than it looks, since your existing setup mostly carries over.

For a team, the calculation is different: Teams (Standard) at $40/mo per user is a real per-seat cost that adds up quickly across a five- or ten-person team, before any usage-billed Bugbot charges are factored in. Whether that's worth it depends on how much the SSO, centralized billing, and privacy-mode features matter operationally, separate from whether the agent itself is useful — a team can get real value from the agent on individual Pro accounts without needing Teams-specific administrative features at all, if centralized management isn't yet a priority.

The most honest way to size up whether Cursor is worth it is to run a real two-week evaluation on Hobby first, on an actual project rather than a toy repo, before deciding whether Pro's extended limits are worth $20/mo. If your team is small enough that individual Pro subscriptions are manageable to track manually, there's no obligation to jump straight to Teams just because a company account exists — the administrative features are there for when centralized management becomes a real operational need, not a default upgrade path every team has to take.

It's also worth checking in periodically once you're paying, since Bugbot's usage-based billing can shift your effective monthly cost even on a flat-price plan. A developer who barely uses Bugbot pays close to the sticker price; one who runs it on every pull request pays meaningfully more. Track that separately from the base subscription so the real bill doesn't surprise you at the end of the month.