Managing AI Coding Costs at Scale · Patrick Wendell, Akshat Bhatia, Vinay Gaba, Erich Elsen and Ivan Zhou, Databricks · Databricks Blog, August 7, 2026
Databricks and four other companies publish a shared playbook for controlling AI coding costs
Based on Databricks' own experience and conversations with engineering leaders at Stripe, Coinbase, Uber and Ramp, the post lays out four cost levers: chase the "efficiency frontier" (best price for a given quality bar) rather than the "intelligence frontier"; route tasks dynamically to the cheapest model that clears it; give developers visibility and progressive friction instead of hard budget cutoffs; and cut token overhead through compaction and cache tuning. The numbers are first-party: "relatively simple tuning of our harness and caching settings led to an almost 50% reduction in the number of generated tokens and associated costs, with no observed quality degradation." Databricks' AI Gateway Smart Router "is able to consistently reduce average task cost by more than 30%, while roughly matching the quality of the most expensive model in the working set." The piece also names negative results other outlets tend to skip: "Stripe found that Opus 4.7 did not meaningfully improve quality over Opus 4.6, while increasing cost. They therefore declined to make Opus 4.7 available internally. Databricks saw similar cost regressions when comparing Opus 5.0 to 4.8." The post also names the harness itself as a source of vendor lock-in: switching costs for individual developers can get high enough that "the harness itself becomes a de facto lock-in to a model family."
The headline savings table is self-described as "directional, based on an informal survey of development teams," not a controlled measurement, and the two infrastructure components singled out as remedies, Omnigent and Unity AI Gateway, are Databricks products. The acknowledgements also thank Thrive Capital, an investor, for feedback on an early draft.
Why it matters: The document attaches real first-party numbers to the cost of running agents at scale. Its named negative results matter as much as the wins: efficiency requires measuring newer models rather than assuming newer means better, and two large companies just published cases where it didn't.