Windsurf cut prices and removed flow action credits while OpenAI was reportedly in talks to acquire the company for $3 billion. The timing looked strategic. As a user, I cared more about no longer having to reason about several kinds of credits.
New Pricing
Windsurf ditched usage-based flow action credits for flat-rate, per-user pricing. No more tracking multiple credit types for background AI actions. They credit better GPU optimization for making this work. Flow action credits never made sense to me — unnecessary complexity that confused users.
- Pro plan: $15/month per user
- Teams plan: $30/month per user (down from $35)
- Enterprise: Custom pricing
The Teams plan includes 500 credits per user with pooled add-on credits ($40 for 1,000 credits shared across the org). Seat management and analytics included. Advanced controls coming for an extra $10/user/month.
How Cursor and GitHub Copilot Compare
| Product | Free Tier | Individual Plan (Pro) | Team/Business Plan | Notes |
|---|---|---|---|---|
| Windsurf | No | $15/month | $30/user/month | No usage-based credits; pooled add-ons available |
| Cursor | Yes (Hobby) | $20/month | $40/user/month | Unlimited completions on Pro; premium models with fair-use limits |
| GitHub Copilot | Yes (Free) | $10/month (Pro) | $19/user/month (Biz) | Pro+ at $39/month for 1,500 premium requests; extra $0.04/request |
What I Would Watch
At $30/user/month, Windsurf undercuts Cursor’s $40 and GitHub Copilot’s $39 Enterprise plan. The $15/month individual plan beats Cursor’s $20, though Copilot Pro at $10/month is still the cheapest option — with limits on advanced models and requests.
Dropping flow action credits removed the part of the bill I found hardest to understand. The acquisition reporting made the new prices interesting, but the useful product change was simpler: fewer counters between me and the coding session. Whether those prices survived a deal was still an open question when I wrote this.
One quick signal
Did this earn your time?
Thanks. That gives me something concrete to check.
About the author
KahWee Teng
I’m a staff software engineer focused on frontend systems and developer experience. I write from migrations, measured tradeoffs, and tools tested in real work.
