Databricks AI Runtime and NVIDIA make it easier to customize open models with enterprise data
Summary
Databricks AI Runtime (AIR) is now generally available, letting teams train and fine-tune models on serverless NVIDIA GPUs with NeMo and containers, alongside governed enterprise data and without managing GPU infrastructure. It pairs NVIDIA Kumo models for structured-data predictions and Nemotron Retriever models for finding evidence in unstructured data, with Genie Code, NVIDIA-specific Agent Skills and joint Nemotron cookbooks to help you get started.
Summary generated by brickster.ai. For the full article, follow the source link above.
More from Databricks Blog
AI Runtime is Generally Available
AI Runtime is now generally available, bringing high-performance GPU infrastructure directly into Databricks with seconds-level launches, flexible environments, and integrated observability, so you can scale training without managing GPU infrastructure. Unity Catalog controls and workload isolation are built in to keep every training workload secure and governed as training becomes more agent-led.
Deploy RFD4-Proteina on Databricks
Genesis Workbench, an open and modular life sciences blueprint, underpins a new RFD4-Proteina integration on Databricks, with Genie Code and domain-specific agent skills helping you build and extend workflows from preparing model inputs to analyzing generated candidates. GPU-intensive workloads run on AI Runtime, while research data, experiment tracking, and governance stay connected on a single platform.
MemCurrent: Designing Persistent Memory for Production Agents
MemCurrent is a persistent memory architecture for production agents, now powering Agent Bricks Memory and Genie, that combines agent-written memory with an offline "dreaming" pipeline that consolidates, deduplicates, and resolves conflicts in a structured knowledge base. On Databricks' internal benchmark built from real Genie conversations, it triples the agent's pass rate versus no memory while using 31% fewer tokens and running 26% faster, outperforming Mem0, PropMem, and OpenClaw memory.
Introducing Agent Memory on Databricks
Agent Memory is now in Beta on Agent Bricks, giving agents a Lakebase-backed store for facts, preferences, and workflows, built on Databricks Research's MemCurrent architecture, which combines plugins, on-demand tools, and an offline "dreaming" pipeline. In Databricks' internal benchmarks on enterprise tasks, it tripled agent pass rate while using 31% fewer tokens, and the Agent Bricks CLI can deploy an agent with memory and sessions in minutes.
How Hamlet uses Databricks Lakebase Postgres to test changes against production data
Hamlet gives every pull request its own Lakebase Postgres branch of production data, so engineers can reproduce and test fixes against the exact data that caused a bug without touching production. AI coding agents run the pipelines and check their work on each branch before a person approves the merge, and Hamlet is now exploring Lakebase Search, branching for object storage, and a home for longer agentic jobs.
How HP Is Building an AI-Ready CDP with Databricks CustomerLake
HP reduced audience-readiness timelines from months to two hours and cut projected CDP total cost of ownership by up to 40% by implementing Databricks CustomerLake directly on its existing foundation. The deployment unified media, brand, and intent data into a governed Marketing Lakehouse, scaling topic ingestion to approximately 20,000 while slashing data-sharing turnaround from three months to 48 hours.