Cursor Teams Upgrades Pricing for Predictability

Cursor is rolling out significant updates to its Teams plan pricing, aiming to enhance cost predictability and increase usage limits. These changes, effective immediately for new customers and for renewing customers on billing cycles starting July 1st, 2026, introduce a distinct usage pool for first-party models and third-party APIs.

Companies working on this

StartupHub profiles of the companies this article names, with funding and a one-liner from our database.

Cursor

$50.0B

An AI-native code editor that helps developers write, understand, and manage code more efficiently.

Earnix

$1.2B

Global provider of intelligent insurance and banking operations with agile, composable, real-time solutions.

Fetcherr

$104M

AI-powered Generative Pricing Engine for the travel industry, optimizing airline revenue.

FeedVisor

$43M

An AI-first optimization and intelligence platform for large sellers and brands on Amazon, providing pricing, advertising, and inventory solutions.

The core of the update involves a new usage pool structure for every Teams seat. Each seat will now include separate allowances for 'Composer and Auto' (first-party Cursor models) and 'Third-Party API' usage. This segregation, coupled with the introduction of Composer 2.5, aims to provide frontier model performance at a reduced cost, according to the announcement.

New Premium Seat for Power Users

To address unpredictable costs driven by heavy users, Cursor is introducing a 'Premium' seat. This tier provides five times the included usage of the Standard seat but at three times the price. Cursor expects this to cover a full month of intensive agent use for most users.

The updated seat pricing is as follows: Standard seats will cost $32 per seat per month for annual plans ($40 monthly), now with increased total usage. The new Premium seat is priced at $96 per seat per month annually ($120 monthly), offering significantly more usage.

Enhanced Visibility and Controls

Admins will now benefit from real-time usage visibility directly within the Cursor dashboard. The interface will display progress toward limits for both first-party and third-party model usage. Recommendations will be provided to help teams optimize their plan based on individual usage patterns.

Spend alerting has also been rebuilt, allowing admins to set dollar-based thresholds and receive notifications via Slack or email. This aims to prevent unexpected billing surprises, similar to how Bugbot Ditches Per-Seat Fees for Usage Billing and Copilot Shifts to Usage Billing have adapted their models.

StartupHub.ai data gives Cursor (Anysphere) a score of 68/100 in our AI developer-tools category, ranking it above most code-editor startups we track. The shift to usage-pool pricing is a meaningful structural change: of the 10+ AI coding tools in our database, Cursor is among the first to separate first-party model usage from third-party API costs, a distinction that matters as frontier model prices continue to fall faster than flat-seat pricing models can adjust.

Last updated: August 2026

Frequently Asked Questions

What changed in Cursor Teams pricing in 2026?

Cursor introduced separate usage pools for first-party models (Composer and Auto) and third-party APIs, a new Premium seat priced at $96/month annually (five times the usage of a Standard seat), and enhanced admin controls including real-time usage dashboards and dollar-based spend alerts. These changes took effect immediately for new customers and for renewing customers on billing cycles starting July 1, 2026.

How much does Cursor Teams cost in 2026?

The Standard seat costs $32 per seat per month on annual plans ($40 on monthly). The new Premium seat is $96 per seat per month annually ($120 monthly) and offers five times the usage of a Standard seat, designed for heavy agent workflows. Both tiers now include separate usage pools for first-party and third-party model costs.

What is Composer 2.5 in Cursor?

Composer 2.5 is Cursor's first-party frontier model that now has its own dedicated usage pool within the Teams plan. Cursor positions it as delivering frontier-level coding assistance at a lower cost than routing the same tasks through third-party APIs like Claude or GPT-4o. The dedicated pool prevents Composer 2.5 usage from competing with your third-party API allocation.

How does Cursor's spend alerting work?

Admins can now set dollar-based alert thresholds in the Cursor dashboard and receive notifications via Slack or email when a team's usage approaches those limits. Real-time progress indicators show consumption against both the first-party Composer pool and the third-party API pool, making cost surprises easier to avoid before the billing cycle closes.