How Revolut Cut Its AI Coding Bill 90% by Self-Hosting an Open-Weight Model

When British fintech Revolut rolled out AI coding assistants to roughly 2,000 engineers, the bill did what AI bills always do: it exploded. Some engineers were spending $1,000 — even $10,000 — a month on AI tokens with little measurable return.

So Revolut did something almost no company of its size has tried: it ditched the frontier APIs as its default and moved its engineers onto a self-hosted, open-weight model. The result, per Revolut's own numbers, was a roughly 90% cut in AI coding inference costs — plus coding that got about 60% faster.

What they actually did

David Abitbol, who runs AI operations and infrastructure at Revolut, laid out the timeline in a talk at the AI Engineer conference in New York (posted 29 October 2026, reported 3 November):

• Early 2025: Gemini rolled out company-wide — ~20% faster coding time.
• Early 2026: Claude Code arrived with strict per-engineer budgets because spending was getting out of hand. Measured impact was modest.
• April 2026: Revolut began self-hosting open-weight models, starting with GLM-5.1 from Chinese lab Z.ai — with no token limits at all.
• Later: upgraded to GLM-5.3 (~754B total parameters, ~40B active per token), served from about 56 Nvidia B200 GPUs.

Claude Code and OpenAI's Codex haven't vanished — they're now the "exception" list, reached for only when the self-hosted setup can't do the job. GLM is text-only, so UI work and the hardest problems still go to frontier models.

The numbers (Revolut's own, not independently verified)

• ~90% cost cut — blended serving cost of about $0.30 per million tokens, invoice roughly a tenth of the Anthropic/OpenAI bill.
• ~60% improvement in coding time, ~70% in lead time (pickup to merge), across ~2,000 engineers.
• 76% more requests/sec with no extra GPUs after tuning; 88% reduction in time-to-first-token (14.3s → 1.7s).
• GPU count held at 56 B200s from April through August while usage grew.

The real insight: unlimited tokens beat smarter models

The most important line in this story: "cheap unlimited tokens, not smarter AI, is what speeds up coding." Engineers didn't get a better model than Claude Opus — they got a model they could use without thinking about the meter running. Before the switch, people were rationing AI because every API call carried a bill. Unlimited, flat-cost tokens changed the behaviour — and the behaviour drove the speed gain.

There's a compliance angle too: Revolut runs the weights on US-based infrastructure rather than through Z.ai's hosted endpoint in China. For a regulated bank, self-hosting is also how you keep data inside your own legal perimeter.

The honest caveats

• These are Revolut's figures — the model change isn't isolated from the effect of removing token limits.
• The 30-cent math excludes cloud spend, staffing, and observability costs.
• 56 B200 GPUs is serious infrastructure — a 20-person startup can't copy this directly.
• The 76% throughput gain came from real inference-tuning work, not from downloading weights and pressing go.

What this means for the rest of us

You won't self-host a 754B model — but the playbook scales down: open models for routine work, frontier for exceptions. Smaller open-weight models like DeepSeek V4.1 Flash are MIT-licensed and downloadable today, and hosted inference for open models undercuts frontier pricing. Revolut's story is the extreme version of a trend that already reaches small teams.

If you run an engineering team and your AI bill makes your CFO flinch, the Revolut playbook — self-host an open model for the everyday work, keep the frontier for the exceptions — is no longer a theory. It's a documented playbook with numbers attached.

This is a condensed explainer. The full breakdown — timeline, the numbers that matter, honest caveats, and FAQ — is on NeurAITool: Revolut Cut AI Coding Costs 90% With Open Models (2026).