Skip to content
OTFotf
All posts

Your AI IDE changed its billing, its price, and its owner — and you didn't get a vote

D
DaveAuthor
7 min read
Your AI IDE changed its billing, its price, and its owner — and you didn't get a vote

In one quarter, the AI IDE a lot of people build inside changed three things about itself without asking anyone who uses it. Windsurf retired its credit system and replaced it with daily and weekly quotas on March 19, 2026. Pro went from $15 to $20. A new $200 Max tier appeared. And the whole thing now sits under Cognition — the Devin company — after a 2025 acquisition.

None of those were bugs. They are the normal lifecycle of a tool you rent. The point is not that Windsurf did anything wrong. The point is that when you build inside a tool, its price, its billing model, and its owner are all variables you absorb rather than choose — and right now all three are moving across the whole category at once.

Three things changed, and you did not get a vote

Break down what actually shifted, because each one lands differently:

  • The billing model changed. Credits — a pool you understood — became daily and weekly quotas, with overages now billed at API rates instead of credit packs. The mental model you had built for "how much will this cost me" was reset overnight.
  • The price changed. $15 to $20 is a 33% Pro increase, plus a new tier an order of magnitude above it. Not catastrophic. But it is a number you do not control, on a tool your workflow now depends on.
  • The owner changed. Cognition folding Windsurf in alongside Devin means roadmap, priorities, and terms now answer to an acquirer's strategy, not to the product you originally signed up for.

Any one of these is survivable. The pattern behind them is the thing to notice.

The receipts: what actually changed at Windsurf

The details below are per CloudZero's pricing review of Windsurf, updated September 2, 2026 after examining Windsurf's own pricing page — the most thorough independent record of the current terms. (Windsurf's pricing page itself sits behind a browser checkpoint at the time of writing, so figures here are attributed to CloudZero's review rather than stated from the primary.)

On March 19, 2026, Windsurf replaced its credit system with quota-based billing: daily and weekly quotas instead of a pool you could watch drain. Overage usage is billed at API rates rather than through credit packs, which changes the failure mode of a heavy month — instead of running out of credits, you run into a bill shaped by raw model prices. The Pro plan moved from $15 to $20 per seat per month, a 33% increase, and a new $200 Max tier arrived for the heaviest users, with Teams at $40. A free tier remains, but the shape of the paid ladder is unrecognizable next to what early adopters signed up for.

Then there is the ownership line. Windsurf began life as Codeium, rebranded, and was acquired by Cognition in 2025 — the company behind the Devin agent — bringing it under the same roof as its SWE-1.5 and Fast Agent models. That is not a footnote. When the company that owns your IDE also owns the flagship agent models, the roadmap stops being "best editor wins" and starts being "best distribution for our models wins." Your subscription now funds someone else's bundling strategy, and the terms you accepted can be rewritten to serve it.

None of this is an accusation. Every figure above is a documented business decision, and businesses are allowed to make them. The question is only ever what you are exposed to when they do.

11 production screens. Login and database wired.

The SaaS Dashboard Kit includes login, a database, and a working dashboard. Live demo at saas.otf-kit.dev.

See the live demo

This is the category, not one tool

Windsurf is just the clearest recent receipt. Zoom out and the same forces are everywhere in vibe coding: credit pools and token quotas that get re-cut, prices that drift upward, and a consolidation wave pulling the field into a few large platforms. Read that last clause as analysis, not fact — no single dataset proves the whole category is consolidating — but the direction of travel is visible in every funding round and acquisition headline: the tools are racing, raising, and merging. That is healthy for the market and genuinely exciting to watch, and it means the terms under your project are the least stable part of your stack.

If your app's foundation lives inside one of these tools, you are not just betting the tool is good. You are betting its price, its billing, and its corporate parent stay convenient for as long as your project lives. That is a lot of bets to have no vote in.

What you own versus what you rent

Here is the line that actually matters, and it is a clean one:

You rentYou own
The tool's pricingYour source code
The billing modelYour repo and git history
The roadmap and the ownerYour conventions and agent config
The sandbox it runs inThe agent you point at it (swappable)

When the rented column changes — and it will keep changing — the owned column does not care. Code on your own filesystem builds the same whether Windsurf is $15 or $200, credits or quotas, independent or acquired. An agent reading your repo is swappable; if one tool reprices or gets bought, you point a different agent at the same code and keep going.

Make the tool the replaceable part

Ownership is not a vibe; it is four concrete things sitting in a repo you control. Run this checklist against your project and see which column each item is in:

  1. Source code in your own repo with real history. Not a project locked in a tool's cloud workspace — a git repo you can clone anywhere. History matters because it is the audit trail an agent reads when it needs to understand why something is the way it is.
  2. Conventions an agent can read. A CLAUDE.md or equivalent at the repo root, plus lint and typecheck configs that enforce the rules mechanically. This is the same discipline behind keeping cursor rules that actually stick and running agent sessions with reusable prompts: the knowledge lives in files, not in one tool's memory panel.
  3. Your own deploy path. If shipping means clicking one vendor's button, the vendor owns your release process. A standard pipeline — the kind covered in a ship-to-production checklist — runs identically no matter which editor you opened that morning.
  4. Swappable agent access. Any agentic tool that can read a repo works: the current IDE, a CLI agent, the next thing entirely. The moment only one tool can operate your codebase, you have rebuilt the lock-in you were trying to escape.

None of these require abandoning AI IDEs. Use them — they are genuinely good. Just make sure every one of them is a reader of your repo rather than the home of it. Readers are replaceable. Homes are not.

The math owning gets you

A subscription is a bet that renews monthly. The tool stays good, the price stays put, the company stays independent — pay again, repeat. The moment any of those breaks, the bet was on the wrong thing.

Buying code you own is a different shape. A kit you bought once still builds if Windsurf tripled its price this morning, because it does not run on Windsurf — it runs in your repo, and your agent of choice reads it. The tool can consolidate, reprice, or rebrand. Your codebase does not get a memo, because it does not work for them.

Tools will keep getting acquired and keep changing their billing — that is the 2026 AI IDE market, and it is not slowing down. The only part of your stack you can keep stable through all of it is the part you actually own. Build there, and the shakeup is something you read about instead of something that happens to you.

Ready to own the foundation? Browse the OTF kits →

Sources

  • CloudZero — Windsurf pricing review (updated Sept 2, 2026) — quota switch date (Mar 19, 2026), Pro $15→$20, $200 Max tier, Teams $40, overages at API rates, Cognition 2025 acquisition, Codeium→Windsurf brand note. Secondary source; Windsurf's own pricing page was behind a browser checkpoint at retrofit time.
  • Windsurf pricing — listed as the primary; unreachable for verification at retrofit time (browser checkpoint, HTTP 429). Figures above are therefore attributed to CloudZero, not independently confirmed against the primary.

Originally published at otf-kit.dev — full-stack kits your AI coding agent can actually ship to production. See the kits →

ai-toolsagentskits
OTF SaaS Dashboard Kit

Ship the product, not the setup.

  • 11 production screens — auth, team, analytics, and settings
  • Login and a real database are wired in
  • AI configs pre-tuned so your agent extends instead of regenerates
Need more than components?

Full-stack kits.
Pay once, own the code.

SaaS Dashboard and Fitness include authentication and a database. Arcade is browse-first with a local demo session and no backend sign-in by default. Booking is in Preview; Marketplace is coming soon and not currently sold. The Bundle includes the three live kits.

Everything Bundle — $149See full pricing

Get the free AI configs pack

AI configs in every kit: CLAUDE.md, .cursorrules and task prompts. Drop them in and your AI tool instantly understands your project.

No spam. Unsubscribe any time.

Prefer the free SDK? Star it on GitHub →