Cursor Teams Pricing: Seats and Usage for 5 to 25 Developers
Cursor Teams now uses Premium, Super, and Ultra seats, with individual weekly pools and a shared prepaid balance for extra usage.
Short answer: Cursor's current Teams page lists Premium at $30, Super at $100, and Ultra at $200 per developer per month. Each paid seat has its own weekly pool for Cursor models. Third-party models and usage beyond a seat's included pool draw from a team prepaid balance. This is a seat and billing guide, not a performance test.
How do Cursor Teams Premium, Super, and Ultra differ?
The current documentation calls the self-serve organization plan Teams, not Business. It lists Premium, Super, and Ultra seats, plus a Free seat with no team usage allowance. The paid tiers are $30, $100, and $200 per user each month. Members and admins can hold any seat tier, and one team can mix tiers. A role label does not automatically require the most expensive seat.
Each paid seat has an individual weekly pool for Cursor models. The pool is shared across Cursor and Grok for that member, but it is not shared across colleagues and unused usage does not transfer. Super is listed as 3.75 times Premium's weekly pool and Ultra as 12.5 times Premium's pool. The public pricing page does not express the pools as a fixed token or task count that applies to every model, so use the admin usage record when estimating actual capacity.
Additional usage is not a flat per-request fee. Cursor says third-party model use is billed at public API prices plus the Cursor Token Rate from the first request. Cursor-model usage after the personal weekly pool is exhausted also consumes additional usage, but those model charges do not use the Token Rate. The amount comes from a prepaid balance shared by the team, which admins can top up or replenish automatically.
This changes the budget question. The seat table is the predictable subscription subtotal, not the total bill for a team that regularly uses third-party models or exceeds weekly pools. Set a prepaid balance cap and decide whether members can enable Auto Top-up before assigning seats. If the business expects usage pooled across people, Cursor directs buyers to Enterprise rather than the self-serve Teams plan.
Does a Cursor seat share its weekly pool with teammates?
A Free seat has no team usage allowance. A paid seat's included pool refreshes weekly and stays with that member. Enterprise adds pooled usage, while the current self-serve plan keeps individual pools. Those are material differences for a team with a few heavy users and many occasional users. Cursor's documentation describes model pool ratios but does not give one universal task count because usage depends on model choice and request size.
A paid seat's pool follows its assigned developer and refreshes weekly; it is not a single open pot for the whole team. Extra eligible use draws on a prepaid balance. Enterprise uses pooled usage, so teams with a few heavy users should compare that quote with the self-serve model.
What do 5, 10, and 25 developer seats cost?
The all-Premium examples are subscription-only: 5 × $30 = $150, 10 × $30 = $300, and 25 × $30 = $750 monthly. A 10-person mixed team with eight Premium, one Super, and one Ultra seat costs 8 × $30 + $100 + $200 = $540 before additional usage. By comparison, 10 Super seats are $1,000 monthly. Add a prepaid balance forecast based on the team's model mix, then keep the seat fee and additional-use spend as separate lines in the budget.
Five Premium seats cost $150 monthly, five Super seats $500, and five Ultra seats $1,000. At 25 seats, the same tiers total $750, $2,500, and $5,000. A developer who exhausts a pool can also draw on team prepaid funds.
A 10-developer mix of eight Premium, one Super, and one Ultra seat costs $540 monthly, or $6,480 across twelve monthly charges, before prepaid use. Ten Super seats cost $1,000 each month, $12,000 over a year. Cursor's current pricing page lists monthly seats rather than an annual discount, so do not subtract a guessed yearly savings. Any third-party model use still draws from prepaid funds.
When should an engineering team request Enterprise?
Cursor Teams is worth evaluating when the editor itself is central to the development workflow and the organization wants shared billing, analytics, privacy enforcement, and team administration in the same product. Keep Cursor for the IDE if developers already rely on it, then decide separately which chat, research, and documentation subscriptions the team still needs around it.
Skip a higher seat tier if the employee does not regularly reach the included pool. Skip the self-serve plan if you need pooled use, invoicing, SCIM, or advanced security controls that Cursor lists under Enterprise. Keep the IDE decision separate from the chat, research, and documentation subscriptions developers use around it.
What should a Cursor Teams admin inspect each month?
Review usage by seat, not only the team total. A low organization average can hide one developer repeatedly running out of included access.
Ask Cursor to confirm model eligibility, privacy settings, the prepaid balance rules, and whether Enterprise pool terms change the billing forecast. Keep the weekly reset in the internal runbook.
What happens to Cursor usage when a seat changes or the team cancels?
Cursor bills active paid seats rather than reserved seats. Adding a developer mid-cycle creates a prorated charge, and moving Premium to Super takes effect immediately with a prorated difference; a downgrade begins at the end of the billing period.
Removing a member frees the seat for another person, but the team must reduce the seat count in Billing to stop paying at period end. Cursor keeps the renewal date fixed and lets admins set team-wide, default per-member, and individual limits for additional usage. The pricing page does not state whether unused prepaid funds are refunded when the whole team cancels.
What should a team try before changing every developer's Cursor seat?
Choose one developer with a typical workload and one with heavy model use, then track their separate weekly pools across a complete refresh. Record which model classes draw from the prepaid balance and whether the team's privacy enforcement setting is enabled.
If uneven usage drives the request, compare a mixed Premium, Super, or Ultra assignment with an Enterprise pooled quote. Keep the IDE decision separate from subscriptions for chat and research, then compare Cursor's stated weekly pools with the team's own model mix.
What does shared team use look like in Krater?
Krater data: 18 active teams used a median 1,280 credits per active member over the 30 days to Nov 10, 2026, with a 4,434-credit median team pool.
Where can Krater sit beside a developer's IDE?
Krater is a separate workspace for chat, research, document tasks, agents, and media creation using 500+ AI models. Developers can keep the editor and use one place for research or writing around a coding session.
Krater credits meter chat, research, and creation rather than Cursor's member-specific weekly pool. Pro includes 1,500 monthly credits; Max includes 10,000 credits for five members including the owner. Choose based on the work your team wants together.
How we checked
Cursor's current Teams documentation supplies the tier names, seat prices, pool behavior, and prepaid-use rules described here. Checked November 11, 2026.
Frequently asked questions
Is Cursor Teams the same as Cursor Business?
The current Cursor page describes Teams and Enterprise as the business plans. It lists Premium, Super, and Ultra for new Teams seats. Older teams may remain on legacy seat names and rates.
How much do 10 Cursor Teams Premium seats cost?
Ten Premium seats cost $300 per month before additional usage, because each seat is listed at $30 monthly.
Does Cursor pool weekly usage across a team?
No. Each paid seat has its own weekly pool. Cursor says seat pools do not transfer between team members. Enterprise offers pooled usage.
What does Cursor charge after the included pool?
Additional use draws on a prepaid team balance. Third-party models are billed at public API prices plus the Cursor Token Rate, while Cursor models after the pool use their token rates without that rate.
Is Cursor usage shared between Cursor and Grok?
The current pricing documentation says a person's Cursor-model weekly pool is shared across Cursor and Grok for that person.
Does Cursor Teams pool weekly usage across coworkers?
No. A paid seat's weekly pool belongs to that member; Cursor describes pooled usage for Enterprise.
Bottom line
The seat price is easy to multiply. The weekly pool and prepaid balance are the details that change the invoice. Keep the editor decision separate from the subscriptions around it, assign higher tiers only where usage supports them, and check Enterprise if the team needs shared pools.
Get your free AI consultation
Thirty minutes with Adam Johansson, an AI expert who maps out what actually fits your business: the right tools, plan and setup for your team size and usage. Free, no strings attached.
Free for any business, any size. We reply within one business day.
Adam Johansson
AI Advisor, Krater
Related reads
Sources
- Cursor Teams pricing: Current Teams and Enterprise names, seat tiers, pool ratios, additional usage and prepaid balance. Checked November 11, 2026.
- Krater plan prices: src/config/pricing.ts.