How Revolut Cut AI Coding Costs 90% With Self-Hosted Open Models - David Abitbol, Revolut

11:472분 읽기AI Engineer2026. 10. 29.컴퓨터/소프트웨어 · 경영/리더십

핵심 요약

Self-hosting the GLM open-source model on a fixed cluster of 56 GPUs cuts Revolut's AI coding expenses by 90% while significantly accelerating engineering lead times.

하이라이트

  • Revolut deployed 56 B200 GPUs to self-host the GLM open-source model for 2,000 engineers.

  • Self-hosting open-source coding models lowered token costs to $0.30 per million, reducing inference expenses to 10% of commercial provider fees.

  • Engineering lead time improved by 70% and coding time decreased by 60% after adopting self-hosted open-source models.

  • Optimizing inference parameters improved time-to-first-token performance by 88% while handling 76% higher request volume on the same hardware footprint.

  • Restricting quantization to FP4 on Blackwell GPUs yields a 40% reduction in GPU footprint without any loss in model precision.

타임라인

  1. Introduction and Initial AI Adoption at Revolut

    Revolut maintains a strong emphasis on shipping products rapidly and maintaining engineering excellence. Initial rollouts of commercial tools generated high expenses with limited financial return, leading the engineering team to cap budgets and test open-source alternatives like GLM.

    • Revolut operates as a European digital bank supporting 80 million customers across 45 markets.
    • Initial deployments of Gemini and commercial cloud coding tools yielded modest efficiency gains alongside high subscription costs.
    • Strict budget limitations prompted an exploration into self-hosted open-source models for coding tasks.
  2. Hardware Metrics and Cost Savings of Self-Hosting

    Self-hosting shifts the financial structure from unpredictable variable billing to flat infrastructure costs. Engineers no longer ration tokens for critical tasks, utilizing parallel task execution and off-peak hours to maximize throughput.

    • A cluster of 56 B200 GPUs successfully serves 2,000 internal engineers using the GLM model.
    • Targeting a time-to-first-token latency under three seconds prevents developer disruption and Slack alerts.
    • Blended token costs settle at $0.30 per million, producing invoices equivalent to 10% of Anthropic and OpenAI spending.
  3. Inference Optimization and Parameter Tuning

    Raw model weights require extensive configuration adjustments to avoid poor inference performance. Resisting the urge to scale hardware prematurely forces deeper optimization of quantization, tensor parallelism, and context length parameters.

    • System performance increased by 88% while handling 76% higher request volume on the exact same GPU count.
    • Limiting context windows to 256k tokens and using FP4 quantization on Blackwell GPUs maximizes efficiency.
    • Maintaining cache hit rates above 90% is required for effective coding task execution.
  4. Production Setup, Compliance, and Governance

    Deploying open-source models within a heavily regulated banking environment requires robust data privacy frameworks, zero data retention policies from GPU providers, and comprehensive open telemetry logging to track all operational incidents.

    • Local routers direct image recognition tasks to multimodal models while retaining GLM for primary text coding.
    • Hosting model weights on US-based servers satisfies data sharing compliance despite using open-source models originating abroad.
    • Sandboxed execution environments enforce strict tool permissions to satisfy strict regulatory requirements for human-in-the-loop oversight.

설명

David Abitbol, who leads AI operations at Revolut, shares data from 2,000 engineers on what AI tools did to coding time and lead time, and why self-hosting open-source GLM models made the biggest difference: about 60-70% faster delivery at roughly a tenth of what they were paying frontier labs. He covers the GPUs needed, the latency targets that keep engineers happy, the tuning that made the same hardware 88% faster, and how an EU-regulated bank keeps it compliant. Chapters: 0:00 Intro 0:36 Who Revolut is 1:18 What AI did to 2,000 engineers' lead time 2:45 Why they started self-hosting 3:33 Coding isn't the bottleneck 4:24 What it takes to self-host GLM 5:46 Tuning: same GPUs, 88% faster 7:06 The parameters that matter 8:14 Production setup 9:23 For the CIO: compliance and safety David Abitbol https://www.revolut.com Join us in SF for the second annual AIE CODE summit: https://aie.codes our last flagship summit of 2026. Applications live now!

이 영상에 대해 글쓰기