AI-first code editor

Cursor pricing, plans, and team cost

AI-first editor with individual and team subscriptions, repo-aware workflows, and tracked team administration features.

Checked 2026-07-11Official product page
Verified quick facts

Cursor at a glance

Only source-tracked facts are shown.

Billing model
subscription per user
Starting tracked price
$0.00 / month
Tracked plans
Hobby, Individual Pro, Teams, Enterprise
Workflow
Editor-first, Agent workflow, Repo-aware editing
Integrations
VS Code extension compatibility
Source checked
2026-07-11
Source-tracked plans

Cursor pricing and plans

Unknown or custom prices remain uncalculated.

PlanPriceBillingScopeUsage caveat
Hobby$0.00month / userindividualLimited Agent requests and Tab completions.
Individual Pro$20.00month / userindividualIncluded model usage and on-demand billing should be checked.
Teams$40.00month / userteamUsage-based Bugbot charges and extra usage are excluded.
EnterpriseCustom pricingcustom / organizationenterpriseCustom pricing requires an official quote.

Open the full Cursor pricing guide

Editable estimate

Estimate Cursor team cost

Uses the existing source-tracked calculator logic. Excluded costs remain listed below.

Monthly estimate$400.00
Annual estimate$4,800.00
Per developer / month$40.00
Selected period$4,800.00

Tracked per-user team plan with centralized billing and administration.

Excluded: Enterprise pricing, usage-based Bugbot charges, taxes, and extra usage are excluded.

Open the full Cursor cost calculator
StackLens assessment

Workflow fit to test

  • Editor-first: worth testing with representative repository work before rollout.
  • Agent workflow: worth testing with representative repository work before rollout.
  • Repo-aware editing: worth testing with representative repository work before rollout.

Do not treat workflow labels as a productivity conclusion.

Verified team notes

Administration and privacy review

  • Centralized billing
  • Administration
  • Analytics
  • SAML/OIDC SSO
  • Teams includes a tracked team-wide privacy mode; verify current policy details before rollout.
Limits and caveats

What to verify before rollout

Public limits and plan terms can change.

  • Included model usage and on-demand usage can change effective cost.
  • Enterprise pricing is custom.
  • Confirm which developers need full paid seats.
  • Estimate usage-based charges separately.
  • Compare Teams controls with the cost of individual subscriptions.