Anthropic has been quietly rolling out a big change.
Businesses can no longer buy Claude subscriptions. API access only.
Enterprise got the call first. Here's what it means for your team š§µ
Why now? The math stopped working.
One dev tracked 10 billion tokens across 8 months on a $100/month Max plan. That's $15,000 in API-equivalent value for $800 paid.
Anthropic absorbed those losses to grow Claude Code. With an IPO reportedly on the way, the subsidy was never going to last.
What happens next is already happening.
Engineers expensing personal Claude subscriptions on company cards. Managers buying five at a time. Entire orgs handing out cards so every dev can expense their own.
No SSO. No audit trail. When the CISO asks, there's no good answer.
Over time, most companies will do the responsible thing.
Legal gets involved, finance gets involved, and teams shift onto proper API pricing with real governance behind it. That's the new normal.
And that's when the interesting question shows up.
Once a company is forced onto API pricing, a new question shows up: why stay locked into one model family?
Arcee, BytePlus, MiniMax, Moonshot, Zhipu. Frontier-class performance at a fraction of the cost. Once you're paying per token, the lock-in logic falls apart.
The cleanest setup I've found for this is @kilocode.
ā Bring your own Anthropic API key ā Or tap into 500+ models through Kilo Gateway ā Route frontier models for hard tasks, cheap open-weights for routine work ā Standardize your team's workflow, stay flexible on what runs underneath
One tool. Every model. No rug pulls.
If your company just got the Claude policy call, or you know it's coming, this is the fastest path to a model-agnostic setup.
Coding agent in VS Code, JetBrains, and CLI. Always-on agents with KiloClaw. Kilo Gateway for unified model access.