How Databricks rolls out frontier models to 12,000 employees on Day 1

Imported from official source

AI Classified by Officially

Providing our employees access to frontier AI capabilities is a top priority at Databricks, and consequently, it is important to us for them to use new models instantly when they become available. At the same time, it is nontrivial to give more than 12,000 people rapid access to a new model because:

  • Models that are marketed as frontier often aren’t. For example, Opus 5.0 was more expensive and ranked lower on both quantitative and qualitative quality scores among our engineers compared with Opus 4.8. Migrating to a model that regresses the frontier can meaningfully hurt a company, rather than help it. In our experience, substantial care is required when evaluating models before migrating workloads en masse to new models.
  • Naive use of a new model can explode costs. When we released GPT Astra to a control group with no associated cost mitigations, the average developer spent 60% more than before gaining access to Astra. An overnight 60% cost increase with a user population of more than 10,000 is very difficult for a company to plan around. Once we better understood which tasks Astra is uniquely great at, we were able to steer usage to substantially reduce overall costs.
  • This post discusses a set of techniques we’ve employed to give most employees at Databricks “Day 1” access to new models, while allowing us to assess whether models are indeed good long-term workhorses. These techniques rely heavily on Unity Gateway to adaptively release, evaluate, and incorporate new models. The week of September 21 was a critical test of these abilities when Opus 5, GPT-6 Sol and GPT-Luna were released in rapid succession. During the week, Databricks provided all employees with Day 1 access, and by Day 3, we had gathered enough data to confirm that these models were on the efficiency frontier, leading to their incorporation into our broader infrastructure.

     At a high level, new model releases at Databricks go through a pipeline that looks as follows:

    This is an extract. The publication continues at the source.

    Read the original at the source: https://www.databricks.com/blog/how-databricks-rolls-out-frontier-models-12000-employees-day-1

    Officially imported this from Databricks’s own source and shows an extract. If you work there, claiming the profile and verifying the domain lets you choose to show the full text here.

    Provenance

    Organization
    Databricks — imported from official source
    Official source
    https://www.databricks.com/feed RSS
    Imported
    September 29, 2026 19:00
    Versions
    1 recorded
    Identity
    https://www.databricks.com/blog/how-databricks-rolls-out-frontier-models-12000-employee...

    Officially records where a publication came from, not whether it is true. Imported records are reproduced from an organization's own official source.