Cursor Pro vs Teams vs Usage Pricing: Individual, Team, and Model-Usage Boundaries

Short answer: Cursor Pro is a personal coding subscription. Teams is a managed workspace route. Usage-based billing is the pressure valve when included model usage is consumed, and Enterprise is the route when the budget needs pooling, invoicing, SCIM, advanced controls, or formal procurement. A team should not treat one Pro seat as the whole budget once multiple developers, shared administration, or heavy agent work enter the workflow.

Personal plans and usage pools

Cursor's personal ladder starts with Hobby for limited Agent requests and limited Tab completions, then moves into Pro, Pro+, and Ultra. The public pricing page lists Pro at $16 per month when billed annually, or $20 if billed monthly. Pro+ is listed at $48 per month when billed annually, or $60 monthly. Ultra is listed at $160 per month when billed annually, or $200 monthly.

Those tiers are not just bigger versions of the same prompt counter. Pro is positioned for weekly agent sessions. Pro+ is positioned for daily agent sessions, with three times the Pro Agent limits. Ultra is positioned for agent power users, with twenty times the Pro Agent limits and priority access to new features.

The headline subscription price is only part of the decision. Cursor's docs describe individual plans as having two separate usage pools. Auto + Composer gives significantly more included usage when Auto or Composer 2.5 is selected, which makes it the everyday coding route for many users. The API pool is charged at the selected model's API price and is used when a person selects a specific model or uses Premium routing.

The included API usage differs by tier. Cursor's models-and-pricing docs list Pro with $20 of API usage, Pro+ with $70, and Ultra with $400, plus generous Auto and Composer usage. That means Pro is not a simple fixed number of prompts: model choice, context size, output length, cache behavior, Premium routing, and Max Mode can all change how quickly included usage is consumed.

How usage turns into extra spend

Cursor says each individual plan includes model usage, and when included monthly usage is exceeded the user can either add on-demand usage or upgrade to a higher tier. On-demand usage is billed monthly at the same rates as included usage, and Cursor says requests are not downgraded in quality or speed after the included amount is consumed.

The useful budget translation is behavioral. Cursor's own guidance says daily Tab users stay within a low usage profile, limited Agent users often stay within the included Pro amount, daily Agent users typically land in a higher total monthly usage band, and power users running multiple agents or automation often need a much larger budget. That is the clearest signal for when a personal plan should move from Pro to Pro+, Ultra, or on-demand usage.

Cloud Agents and automation deserve separate attention. Cursor lists Cloud Agents and automations in the paid individual feature set, while its docs say Cloud Agents are charged at API pricing for the selected model and ask users to set a spend limit when they first start using them. If a developer is moving from interactive coding into background work, the team should budget for usage behavior, not only the base subscription.

Max Mode is another boundary. It extends the context window for complex tasks and consumes usage faster than the default context window. Current Cursor docs say Max Mode on individual plans is billed at the model's API rate, while Teams non-Auto requests include the Cursor Token Rate. Expensive frontier models can therefore be valuable for hard tasks, but they are not interchangeable with Auto for cost planning.

Pro versus Teams

Teams is not just a bulk version of Pro. Cursor's Teams pricing docs list Teams at $40 per user per month and describe it as a usage-based plan with privacy mode enforcement, an admin dashboard with usage stats, centralized team billing, and SAML/OIDC SSO. That makes Teams the self-serve organizational route when professional developers are collaborating and a manager needs visibility into spend and access.

Each Teams seat includes $20 per month of included usage. Cursor says that usage is allocated per user, does not transfer between team members, resets at the start of the billing cycle, and covers agent requests at public list API prices plus the Cursor Token Rate. When a team member exceeds included usage, on-demand usage continues automatically by default, is billed monthly at the same rates, and can be controlled with spending limits.

This is the key difference from buying one more individual subscription. A second Pro seat can help if a second person simply needs their own personal Cursor access. Teams becomes the cleaner route when the organization needs central billing, admin usage reporting, privacy settings, SSO, active-user billing behavior, or team-wide spending limits. Those controls matter before the invoice is large, not only after a budget surprise.

Enterprise and API-key boundaries

Enterprise is the route when Teams is not enough. Cursor recommends Enterprise for customers that need priority support, pooled usage, invoicing, SCIM, or advanced security controls. The public Enterprise page also emphasizes organization-level controls such as model access controls, MCP controls, agent rules, audit-style administration, identity management, and support for larger procurement needs.

Pooled usage is the important budget concept. Teams allocates included usage per user and says that usage does not transfer between team members. Enterprise is the official route Cursor points to when a buyer needs pooled usage shared across users. If one developer is light and another is running heavy agents all day, Teams may still leave the heavy user in on-demand usage while the light user's included usage sits unused.

Bring-your-own API keys are a different boundary, not a universal escape hatch. Cursor's API key help says custom keys can send messages at the user's own provider cost and only work with standard chat models. Features that require specialized models, such as Tab completion, continue to use Cursor's built-in models. It also says Cursor's Zero Data Retention policy does not apply when using your own API keys because data handling follows the provider's policy.

Final budget check

Start with the buyer, then the usage pattern. A solo developer who mostly uses Tab and occasional Agent work should begin with Pro and watch the usage dashboard. A solo daily agent user should compare Pro+ against Pro plus on-demand usage. A power user who repeatedly hits Pro+ boundaries should compare Ultra against the real monthly usage total rather than the base subscription price.

For teams, the first budget question is not only how many people need Cursor. It is whether the organization needs shared administration, central billing, spend visibility, privacy enforcement, SSO, and limits. If those controls matter, Teams is usually the cleaner starting point than reimbursing individual subscriptions.

The second team question is whether usage should pool. If each developer's usage can stand alone, Teams may be enough. If heavy and light users need one shared usage budget, or if procurement requires invoice billing, SCIM, priority support, advanced security controls, or negotiated terms, Enterprise is the budget route to evaluate.

Before paying, check five boundaries: annual versus monthly price, individual versus workspace ownership, Auto + Composer versus specific-model API-pool usage, on-demand spend limits, and whether heavy users need pooled usage. Cursor pricing is easiest to control when the team treats subscription seats and model usage as connected but separate budget lines.