{"slug": "ai-runtime-is-generally-available", "title": "AI Runtime is Generally Available", "summary": "Databricks announced the General Availability of AI Runtime (AIR), a fully managed GPU infrastructure service that runs inside the Databricks Lakehouse so customers can train foundation models on enterprise data without managing a separate GPU stack. Databricks said hundreds of companies, including Robinhood, PicPay, Merck, Flo Health, TinyFish and FactSet, already use AIR for deep learning training and production deployment. Superhuman Applied Research Scientist Kostia Omelianchuk said moving from a single node with 8 A100 GPUs to a multi-node setup with 16 H100 GPUs cut training time from roughly seven days to 48 hours, a 3.5x speedup.", "body_md": "Train foundation models faster on your enterprise data with fully managed GPU infrastructure\n\nby  [Tejas Sundaresan](https://www.databricks.com/blog/author/tejas-sundaresan), [Jianwei Xie](https://www.databricks.com/blog/author/jianwei-xie), [Mike Del Balso](https://www.databricks.com/blog/author/mike-del-balso), [Hanlin Tang](https://www.databricks.com/blog/author/hanlin-tang), [Julia Powell](https://www.databricks.com/blog/author/julia-powell)  and  [Cynthya Peranandam](https://www.databricks.com/blog/author/cynthya-peranandam) \n\nToday, we’re excited to announce the General Availability of AI Runtime (AIR), bringing fully managed GPU infrastructure directly into Databricks so customers can train their most demanding models where their enterprise data already lives.\n\nToo often, AI teams spend more time securing GPU capacity, managing failures, and waiting for experiments to launch than improving their models. Running GPU infrastructure separately from their Lakehouse adds governance gaps and puts sensitive training data at risk. As [coding agents drive more training experiments](https://www.databricks.com/blog/how-our-ai-research-team-uses-ai-runtime), these bottlenecks and [risks](https://openai.com/index/hugging-face-incident-and-the-road-ahead/) grow — making reliable, fast, and governed infrastructure essential.\n\nAIR brings GPU infrastructure, developer tools, and data governance together so teams can train at scale, iterate faster, and secure every workload without managing a separate GPU stack. Hundreds of companies, including Robinhood, PicPay, Merck, [Flo Health](https://www.databricks.com/blog/how-flo-health-built-safer-more-useful-open-models-databricks-ai-runtime), [TinyFish](https://www.databricks.com/blog/post-training-production-how-tinyfish-runs-its-web-native-model-databricks-ai-runtime), and [FactSet](https://www.databricks.com/blog/how-factset-cut-model-training-and-deployment-days-hours-databricks-ai-runtime), already use AIR to train and ship deep learning models to production, with use cases spanning healthcare, manufacturing, and consumer-facing agents. Our own [Databricks AI Research team uses AIR](https://www.databricks.com/blog/how-our-ai-research-team-uses-ai-runtime) to train the models behind KARL and AI Parse.\n\nWith AIR, customers can:\n\nManaging GPU infrastructure requires significant operational overhead, from capacity planning and node maintenance to networking and monitoring.\n\nWith AIR, Databricks takes on the operational work of provisioning GPUs, maintaining healthy infrastructure, and optimizing the workload, so your team can focus on training:\n\nUsing Databricks AI Runtime, we moved our large-scale training from a single-node setup with 8 A100 GPUs to a multi-node setup with 16 H100 GPUs. This reduced training time from roughly seven days to 48 hours, a 3.5x speedup, making it much easier for our team to iterate on larger model experiments and train more efficiently.—Kostia Omelianchuk, Applied Research Scientist and Area Tech Lead, Superhuman\n\n**Use GPUs wherever you work**\n\nAccess GPUs via CLI or interactively within Notebooks or IDEs. Your first workload just requires a single CLI command. With [Databricks AIR Skills](https://docs.databricks.com/aws/en/machine-learning/ai-runtime/develop-workloads/coding-agents/agent-skills), migrating from a K8S or SLURM cluster just takes a single natural language prompt.\n\n**Orchestrate GPU workloads with confidence with Lakeflow**\n\nAIR integrates natively with [Lakeflow](https://www.databricks.com/product/data-engineering) so you can keep GPU workloads in sync with upstream and downstream pipelines. Moving to production requires just a few extra lines of YAML, with built in priority/pre-emption that minimize idle GPU time and monitoring tools like [Genie ZeroOps](https://www.databricks.com/blog/introducing-genie-zeroops) that lower operational toil.\n\nDistributed training workloads are painful to set up and launch. AI teams waste time configuring training environments, waiting for GPU clusters to spin up, and debugging issues across the stack.\n\nAIR helps you get from code to training in seconds. You can use pre-built environments or [bring your own container](https://docs.databricks.com/aws/en/machine-learning/ai-runtime/connecting/cli/docker-images), and benefit from highly optimized environment caching so you just need to build environments once. AIR is compatible with all major frameworks, including Ray, so you can bring code over with minimal configuration.  \n\nDatabricks AI Runtime lets us train where our data already lives, with the reliability, security, and performance we need for large-scale model training. We can spend less time managing GPU infrastructure and more time improving the models themselves.—Vladislav Nedosekin, Director of Engineering, Data & AI Platform, Flo Health\n\n**Launch your next experiment in seconds**\n\nWhen you iterate and develop a training script, every second of delay is felt repeatedly. And so, we’ve [optimized every layer of the provisioning stack](https://www.databricks.com/blog/booting-databricks-vms-7x-faster-serverless-compute) to make workloads, even large scale RDMA-enabled clusters with dozens of GPUs, spin up in seconds.\n\n**Debug distributed training in one place**\n\nWe’ve built an entirely new observability experience in MLflow, the industry’s leading experiment tracking tool. With this new experience, debugging your logs, which stream seconds after submission, is as simple as adding `–watch` to your AIR command. For deeper investigation, you can use our new logs viewer, tailor-built for multinode training.\n\nAt Sonar, we help organizations build code confidence in their agentic software factories through independent code verification and governance. A team of our research engineers recently used Databricks AI Runtime to build LLM training pipelines and rapidly test different hypotheses. AI Runtime gave us the ability to move quickly from ideas to experiments, with observability of each stage in the pipeline.—Joe Tyler, Lead AI Researcher, Sonar\n\nDatabricks' AI Runtime greatly streamlined the process of training a custom Text To Formula (TTF) model. With no infrastructure setup or delays, it was easy to choose the right compute based on prompt size and output token generation. This allowed us to move quickly, maintain our Lakehouse workflows, and deliver a high-quality model with full governance, reducing time to setup, train and deploy our model from days to hours.—Nikhil Sunderraj, Principal Machine Learning Engineer, FactSet\n\n**Agentic debugging with built-in Genie Code**\n\nGenie Code is embedded into the entire user experience, and comes pre-packaged with agent skills to help you debug issues and optimize GPU training performance. These skills include insights that our research and performance teams discover, like how we [reduced Qwen training time by 6x on AIR](https://www.databricks.com/blog/reducing-qwen-training-time-6x-ai-runtime).\n\nAt Robinhood, AI Runtime helps our teams move from experimentation to training faster, without the infrastructure overhead. Fine-tuning is seamless, letting us train where our data lives while keeping governance and data controls built in. That means our engineers spend more time building better models and less time managing complex GPU setups.—Robert Macy III, Machine Learning Engineer, Robinhood\n\nDatabricks AI Runtime lets us scale distributed training on serverless GPUs across millions of records, right inside our existing data workflows. As more of the top 20 biopharma companies rely on our models to inform development decisions, that speed and simplicity lets our team keep improving the models instead of managing the infrastructure.—Eran Barash, VP of Artificial Intelligence and Machine Learning, QuantHealth\n\nManaging GPU infrastructure separately from enterprise data creates governance gaps, fragmented access controls, and unnecessary data copies. As agents run hundreds of training experiments in parallel, teams need to ensure sensitive data stays governed and workloads remain securely isolated, without relying on manual oversight. [The OpenAI Huggingface incident](https://openai.com/index/hugging-face-incident-and-the-road-ahead/) underscores this risk. \n\nAIR extends your trusted data controls and governance to every GPU workload. Unity Catalog enforces consistent read/write permissions on all aspects of a GPU workload (data access, checkpoints, logs, etc.), so your GPU platform and data governance layer now speak the exact same language.\n\n**Isolate workloads and control network access**\n\nAIR is backed by years of [investment in serverless security](https://www.databricks.com/trust/security-features/serverless-security), isolation, and private networking. Unlike GPU isolation mechanisms that expose the host kernel, AIR has VM-level isolation, supports PrivateLink and serverless egress controls. Thus AIR offers much stronger protections for training workloads compared to conventional systems. \n\n**Understand where your GPU budget goes**\n\nTrack AIR usage and costs through [Databricks billing system tables](https://docs.databricks.com/aws/en/machine-learning/ai-runtime/guides), alongside your other Databricks workloads. Use workload-level usage records to identify which training workloads consume your GPU budget and guide decisions about future runs. \n\nWith Databricks AI Runtime and Serverless, we’ve been able to scale LLM training and inference more quickly, working with larger models, multiple H100 GPUs, and large volumes of data. The integration with our existing pipelines, together with Databricks’ orchestration and monitoring capabilities, has made the end-to-end workflow simpler and more efficient, reducing infrastructure complexity and development cycle time.—Vitor Rolim, Staff Machine Learning Engineer, PicPay\n\nFor us, training the model is only part of the problem. We need to know whether a change actually makes the agent better at completing real tasks, and then be able to get that improvement into production quickly. With AI Runtime, we can train on GPUs, evaluate with MLflow, and serve our web-native model without building a separate stack for every stage.—Zach Richardson, Head of AI, TinyFish\n\nTo help you get started, we’ve put together several template notebooks and starter guides:\n\nPlease reach out to your account team to learn more or if you have any questions!\n\nSubscribe to our blog and get the latest posts delivered to your inbox.", "url": "https://wpnews.pro/news/ai-runtime-is-generally-available", "canonical_source": "https://www.databricks.com/blog/ai-runtime-generally-available", "published_at": "2026-10-21 11:20:00+00:00", "updated_at": "2026-10-21 11:43:53.627314+00:00", "lang": "en", "topics": ["ai-infrastructure", "machine-learning", "ai-tools", "mlops"], "entities": ["Databricks", "AI Runtime", "Robinhood", "PicPay", "Merck", "Flo Health", "TinyFish", "FactSet"], "also_reported_by": [], "alternates": {"html": "https://wpnews.pro/news/ai-runtime-is-generally-available", "markdown": "https://wpnews.pro/news/ai-runtime-is-generally-available.md", "text": "https://wpnews.pro/news/ai-runtime-is-generally-available.txt", "jsonld": "https://wpnews.pro/news/ai-runtime-is-generally-available.jsonld"}}