Windsurf Pricing: Current Plans and Legacy Credits

Updated October 28, 2026

Windsurf's pricing URL now redirects to Devin's pricing page. As checked October 28, 2026, it lists Free at $0, Pro at $20 per month and Max at $200 per month. Teams has an $80 monthly minimum with $40 full seats, explained in the billing documentation. Enterprise pricing requires a quote. Older references to $15 Pro and a universal 500-credit allowance should not be used for a new purchase.

This is a documentation-based buying guide, not a hands-on performance review. Compare plans by who needs editor access, how often they use agents, what happens after included usage, and which administrative controls the organization requires. A higher subscription price does not establish better code quality.

Our data: six subscription budget scenarios

We calculated two individual-plan annualized costs and four team seat scenarios from the current published monthly prices. The inputs, formulas and exclusions are below. These are planning examples, not customer invoices. AI assisted the research and drafting; PE Collective is responsible for the editorial analysis.

Current plans · Free versus Pro · Quotas and credits · Team budget · Legacy plans · Buying checklist

Windsurf pricing plans and the current Devin destination

PlanPublished monthly priceDecision to make
Free$0Can you evaluate the workflow within limited agent usage?
Pro$20Does regular individual work fit the included usage?
Max$200Does sustained individual use justify the larger allowance?
Teams$80 minimum; $40 per full seatWho needs a full desktop seat versus occasional shared usage?
EnterpriseCustomWhich contractual, deployment and administration requirements need a quote?

Sources: current pricing and self-serve billing documentation. The marketing page's team headline can read like a base fee plus seats; the detailed billing table instead describes an $80 minimum satisfied by seats and credits. The examples here follow that explicit billing table. Confirm the checkout total for your account before buying.

The product name matters when comparing an old invoice with a new subscription. Follow the plan destination from your account and record its effective date. A search result using “Windsurf Pro” may describe a historical offer, an existing customer's terms, or the current individual product. Those cases can have different allowances even when the monthly charge looks similar.

Keep the plan price separate from your agent budget. Subscription cost, included allowance, purchased extra usage and taxes are different lines in the calculation. An apparently cheap seat can still be expensive for a team that runs many long sessions, while a higher seat price may cover work that otherwise incurs usage charges.

Is Windsurf free, and when does Pro make sense?

The current Free plan includes limited agent use and model availability, plus unlimited inline edits and Tab completions according to the pricing page. That makes it suitable for examining the editor workflow before choosing a paid plan. “Unlimited completions” should not be read as unlimited agent work; the two interactions have different limits.

Use a bounded evaluation task from your normal work. For example, ask the tool to explain a small module, change a validation rule, and show the relevant tests. Inspect the diff and run the same checks you would require from a colleague. Record where you needed to correct context, reject edits or explain repository conventions.

Free is a reasonable starting point when you are learning the interface or doing occasional changes. It is a weaker planning assumption for a deadline-driven project that depends on repeated agent sessions. Decide beforehand what you will do if you reach a limit: finish manually, wait for the reset, or make an approved purchase.

Pro is the first paid individual option in the current lineup. Its role is regular single-person usage. Before upgrading, identify the problem you want the subscription to solve. Running out of agent allowance is different from using the wrong model, missing project context or asking for changes the repository cannot support.

A subscription cannot repair an incomplete task description. Give the agent the failing behavior, expected outcome, relevant files and verification command. Smaller, well-scoped requests are easier to assess, and they also make it possible to compare how much usage a task consumes. A long conversation full of unrelated material makes that comparison harder.

How quotas and extra usage work

The billing documentation describes daily and weekly allowances for Pro and full team seats; Max has a larger weekly allowance without a daily cap. Purchased on-demand credits can fund additional usage and roll forward. Flex seats draw from shared team credits and do not include Desktop access. These are current billing categories, distinct from old Windsurf prompt-credit tables.

Do not convert a quota into an invented number of tasks. A short explanation and a multi-step repository change can consume different amounts of work. The model, input context, generated output and tool activity affect consumption. A fixed “requests per month” comparison would hide those differences unless the provider defines the same unit for every request.

For your own estimate, record three task types: a small edit, a routine feature and a difficult debugging session. Track the account's usage movement around each task. Use several examples per type before assigning a budget. This is a proposed measurement method, not a claim that PE Collective observed those costs.

Keep reset allowance and purchased balance in separate columns. A reset can replenish included capacity without refunding an already purchased credit. A remaining balance can also outlive the particular project that caused the purchase. That distinction matters when comparing a one-month experiment with a subscription your team expects to keep for a year.

Check automatic top-up settings before starting unattended or recurring work. A budget owner should know which activity can spend additional funds, what limit applies and where usage is visible. Use an explicit amount appropriate to the task; an unrestricted balance makes it difficult to learn whether the subscription itself meets your needs.

Pro versus Max: calculate the break-even question

The listed monthly subscription difference is $180: $200 − $20. If you are considering Max solely to avoid extra usage purchases on Pro, compare that difference with your actual extra-usage spending. Spending $30 beyond Pro in a typical month does not by itself justify paying another $180 for Max.

The comparison becomes more interesting when the larger allowance or lack of a daily cap helps a concentrated work schedule. That is a capacity question as well as a price question. Examine when you hit limits, which models you use and whether the higher plan includes the capacity you need. Do not assume that a tenfold subscription price buys exactly ten times every model's usage.

For annualized budgeting at unchanged monthly rates, Pro is 12 × $20 = $240 and Max is 12 × $200 = $2,400. These are twelve-month sums, not advertised annual-billing discounts. They exclude taxes and extra usage. If a checkout offers an annual arrangement, use its actual terms rather than substituting this arithmetic.

Team pricing: full seats, occasional users and the minimum

Use the detailed seat table when building a procurement estimate. Under the documented minimum structure, recurring full-seat charges are $40 × the number of full seats, with an $80 monthly floor. Below two full seats, the remainder of that minimum becomes prepaid shared usage credit. Additional usage can increase the total.

Full seatsSeat arithmeticMinimum monthly totalCredit portion within the minimum
00 × $40$80$80
11 × $40$80$40
22 × $40$80$0
55 × $40$200$0

For a five-developer example, the recurring seat budget is therefore $200 per month before extra usage. Annualizing the same monthly amount gives $2,400. This calculation assumes five full seats throughout the year and unchanged pricing. It does not include extra users' metered activity, taxes, or a separate enterprise agreement.

Do not assign a full seat solely because someone belongs to the engineering organization. Map access to the actual task. A developer who works in the desktop editor every day has a different requirement from an occasional reviewer. Conversely, a free flex seat is not a substitute when the person needs Desktop access.

Shared credits need ownership. Decide who may start sessions that draw from the pool and how you will investigate a sudden increase. Separate normal engineering usage from experiments and automated review jobs. The useful unit for an internal report is completed, accepted work with its cost, not the number of prompts sent.

When comparing a team plan with separate individual subscriptions, include administration and collaboration requirements. The smallest subscription sum is not necessarily a permitted or workable team setup. The current documentation identifies Pro and Max as individual plans; do not share one person's account across developers to make the budget appear lower.

What happened to 500 credits and the old $15 Pro price?

Older guides describe Windsurf using monthly prompt credits and fixed allowances. Those numbers are not a reliable current-plan quote. The usage overview distinguishes self-serve plans, enterprise ACUs and legacy enterprise credits, and dates the introduction of new self-serve usage plans to March 2026.

If you already pay under older terms, compare your account plan name, invoice and current usage display. Keep the historical contract separate from a new-user pricing table. A billing migration may change the unit of consumption, the reset schedule or the treatment of purchased balances. Do not assume an old credit equals a new credit simply because both use that word.

For an internal procurement note, preserve the old price as a dated historical fact supported by the invoice. Then state the current renewal or migration terms shown to the account. That gives finance a useful explanation for a changing bill without presenting a past promotion as a publicly available offer.

Similarly, avoid the old page's blanket promise that all unused credits disappear at month end. The current self-serve documentation says purchased on-demand credits roll over. Included usage allowances still have their own reset behavior. Read the rule for the balance you are discussing.

Enterprise and data-handling questions

The pricing page lists enterprise capabilities including SAML/OIDC SSO and a dedicated deployment option. A published feature label is the beginning of procurement review, not a complete statement of your contract. Ask which controls apply to the exact product, models, integrations and deployment you intend to use.

Write down the types of repository data the tool may access, where execution occurs, how secrets are handled and who can authorize connections. If the organization needs a particular retention arrangement, verify it in the applicable documentation or agreement. Do not carry forward the old page's unsupported promise that every enterprise account has a specific retention setting by default.

Include offboarding in the purchase decision. The team should know how to revoke a developer's access, remove repository permissions and retain any work products it needs. These operational questions can matter more than a small difference in monthly seat price.

Windsurf, Cursor and Copilot: compare the bill

The three products do not sell identical units of work. Devin's current individual offer combines a subscription with quota resets and purchasable additional use. Cursor's pricing page separates its shared usage pool from third-party model charges. GitHub Copilot describes allowances in GitHub AI Credits. A credit from one product is not interchangeable with a credit from another, and multiplying an old request allowance by a subscription price produces a misleading comparison.

ProductWhat to record before choosingComparison mistake to avoid
Windsurf / current Devin plansIndividual or team seat, reset schedule, included quota, extra usage, Desktop accessTreating legacy prompt credits as current-plan capacity
CursorSubscription tier, eligible models, usage pool and separately billed third-party modelsAssuming the seat price includes every model used by an agent
GitHub CopilotIndividual or organization plan, AI-credit allowance, administrator restrictions and additional usageComparing today's credits with a past premium-request allowance

Use the Cursor plan table and GitHub Copilot plan documentation for the current offer. Keep an observed date beside the terms in your purchase comparison. The product that is cheaper for occasional inline assistance may not be cheaper for long autonomous tasks, especially when you choose a separately billed model.

Give each candidate the same repository revision and a small change with a known acceptance test. Record the subscription assumption, any added usage charge, whether the change passes, and the time required to repair it. Do not count an unreviewed patch as a completed task. A plan with a lower bill but more rejected work can be the more expensive choice for that workflow.

Keep migration effort separate from recurring cost. Moving to a new editor may require extension, shortcut and debugging setup. A team also needs repository rules, access policies and a process for approving generated changes. Budget that work as a one-time evaluation cost rather than pretending it is included in the subscription.

A worked budget with extra usage

Consider an illustrative individual who buys Pro at $20 and then spends $45 on additional usage during a busy month. The subscription-plus-usage total is $65 before taxes: $20 + $45. At the same workload, Max would start at $200 before any further charges. The $135 difference does not prove Pro is the better plan, because Max may avoid a limit that matters to the developer's schedule. It does show that paying for extra usage alone is insufficient justification for the upgrade.

Now assume six similarly busy months and six months with no additional purchases. The annualized estimate is 12 × $20 + 6 × $45 = $510 before taxes. This is a hypothetical workload calculation, not a measured average or an annual contract quote. Compare it with 12 × $200 = $2,400 for a year of Max at the listed monthly price. Recalculate when observed usage or subscription terms change.

For team procurement, keep a second estimate for uncertainty in the advertised minimum. The detailed billing table describes the $80 minimum as satisfied by full seats and credits, while the pricing headline can be read as a base charge plus seats. For five full seats, those interpretations would be $200 and $280 respectively before extra usage. The seat table supports the $200 calculation above; the actual checkout or written quote must resolve the amount charged. Do not approve a purchase from an ambiguous headline alone.

What to check when a bill rises

Start with the billing period and seat count. A partial period, seat change or different renewal date can make two invoices unsuitable for direct comparison. Separate recurring subscriptions from added usage and taxes. Identify the specific charge rather than assuming every increase comes from a price rise.

Compare added usage with the activity that generated it. Look for unattended tasks, retries, a more expensive model or larger repository context. These are hypotheses to check against the usage display, not claims about the cause of your bill. Keep the period and unit consistent when comparing two developers or two weeks.

If a charge belongs to an older Windsurf agreement, preserve the applicable invoice and plan terms. Ask the provider to explain the migration rule rather than converting old credits into current quotas yourself. The current usage documentation identifies where usage and invoices are available.

A purchase worksheet should therefore contain the plan, billing interval, number and type of seats, included allowance, reset schedule, extra-usage limit, expected tax and the date the terms were checked. Add the person responsible for approving additional spend. With those fields, a developer and finance reviewer can discuss the same estimated bill instead of comparing screenshots that describe different plans.

How to choose a plan without guessing

  1. Confirm whether you are comparing a current self-serve plan, a legacy account or an enterprise quote.
  2. List users who require Desktop access and those who only need occasional cloud activity.
  3. Run representative tasks and record usage, accepted changes and manual correction time.
  4. Calculate subscription cost plus likely extra usage. Include taxes separately and avoid assuming a discount.
  5. Check daily or weekly limit behavior against your work schedule, especially before a deadline.
  6. Review spending controls, repository permissions and account ownership before wider use.

For alternatives, compare the current Cursor pricing page and GitHub Copilot plans against the same workload. Keep seat price, included model usage and team controls in separate columns. A lower advertised subscription may bill some model usage separately.

The practical starting point is Free for a bounded evaluation, Pro for an individual whose observed work fits its allowance, and Teams when multiple people need an administered subscription. Consider Max after measuring sustained individual demand. Use the official plan screen for the final quote, and recheck this guide when billing units or plan names change.

AI coding tools move fast

Weekly data on which tools developers are adopting, pricing changes, and new releases worth knowing about.

Illustrated portrait of Rome Thorndike

Rome Thorndike

Rome Thorndike is the CEO & Founder of Provyx, which provides GTM intelligence and data validation for healthcare companies, including EngagedMD and BTL Industries. He writes The AI News Digest for over 3,000 subscribers and has worked in Azure AI/ML enterprise sales and AI-company customer delivery.

Connect on LinkedIn