- 7th Annual
- November 17-18, 2026
- Austin, TX
MLOps World | GenAI Summit 2026
Two days of case studies, workshops, and expo on taking AI/ML and agentic systems into production – at the Etter-Harbin Alumni photo – full-bleed hero or browse files
Can’t travel? The virtual day on Nov 16 is free.
The event that takes AI/ML & agentic systems from concept to large-scale production
2 Days • 16 Tracks • 75 Sessions • Vibrant Expo
Why attend
Programmed by a 75+ member Steering Committee of working practitioners – case studies, not product pitches.
Build optimal strategies
Learn the workflows and architectures from teams actively scaling ML, GenAl, and agents in production.
Increase project efficiency
Minimize risk, delays, and missteps with case studies that set the standard for impact and quality.
Make better decisions
Faster calls, backed by hard won lessons from teams shaping agentic systems at scale.
Tracks & track leads
Track lead: Denys Linkov — Head of ML, Wisedocs
This track is for ML engineers looking to go deeper into hardware and kernel knowledge: the new generation of chips, chip architecture, kernels and inference tricks, and what they unlock in LLMs and other models.
Track lead: Hannes Hapke — Director, Open Source, Dataiku
This track is for ML engineers looking to go deeper into hardware and kernel knowledge: the new generation of chips, chip architecture, kernels and inference tricks, and what they unlock in LLMs and other models.
Track lead: Tony Kipkemboi — Staff Engineer, AI Operations Guild. Prev, Founding DevRel Engineer & Partnerships Lead , CrewAI
Learn the harness patterns that keep agents reliable in production: tool permissions and sandboxes, self-correction loops, state and memory under a cost ceiling, evals that hold at volume, and the agent loop itself, from speakers who built and measured them, including the failure modes that forced a redesign.
Track lead: Tony Kipkemboi — Head of Developer Relations, CrewAI
AI usage continues to grow, yet leaders are struggling to quantify the ROI of their investment. In this track you’ll hear from engineers who have debugged and optimized their costs.
Track lead: Suhas Pai — Co-Founder & CTO, Hudson Labs
There is no settled architecture for deciding what an agent should store, retrieve, revise, and forget. In this track, attendees will leave with a stronger understanding for choosing, implementing, and evaluating memory components in an agent system.
Track lead: Tony Kipkemboi — Head of Developer Relations, CrewAI
Being more productive than you were before coding agents makes it easy to be fooled into thinking you’re already at best practice. This track covers coding agents on complex codebases, secure AI-assisted development, and the code review bottleneck with concrete case studies from speakers who’ve gone beyond the hype.
Track lead: Suhas Pai — Co-Founder & CTO, Hudson Labs
AI systems can increasingly self-evaluate and modify their own prompts, tools, memory, code, data, and workflows. This track will focus on ensuring these feedback loops produce genuine, repeatable improvement rather than benchmark overfitting or unstable changes.
Track lead: Suhas Pai — Co-Founder & CTO, Hudson Labs
In a world where models are released daily, how do we build an effective eval approach, or know when the right time is to swap models? This session is designed to help engineers move more quickly, build better products, and save on costs
Track lead: Dave Scharbach — Executive Director, TMLS
2 Days of workshops, Case studies, Discussions & Socials
Learn from leading minds, sharpen your skills, and connect with innovators driving safe and effective AI in the real world.
Free Online Stage
- Virtual Day (Nov 16th)
- In-Person Workshops (Nov 17th-18th)
- Workshops (Nov 19th)
Day 1
- Summit:
- Talks, Panels, & Workshops
- Expo:
- Lightning Talks
- Brain Dates
- Community Square
- Startup Zone
- Vendor Booths
- Opening Party
Day 2
- Keynote
- Summit:
- Talks, Panels, & Workshops
- Expo:
- Lightning Talks
- Brain Dates
- Community Square
- Startup Zone
Why attend: Connect & Grow
Grow industry influence
Equip your team to win
Stay ahead of fast-moving competitors by giving your team the insights, skills, and contacts they need to exceed expectations.
Build career momentum
Make every hour count by using our event app to hyper-focus on the right topics and people who will help shape your future in AI.
2025 Summit: Full-Spectrum AI
All themes, talks, and workshops curated by top AI practitioners to deliver real-world value. Explore sessions
2025 THEME: AI Agents & Agentic Workforces
AI Agents for Developer Productivity
This track highlights practical uses of agents to streamline dev workflows—from debugging and code generation to test automation and CI/CD integration.
AI Agents for Model Validation and Deployments
Agents can now assist in model testing, monitoring, and rollback decisions. The track focuses on how teams are using autonomous systems to harden their ML deployment workflows.
Augmenting Agentic Workforces
This track explores how teams are combining human oversight with semi-autonomous agents to scale support, operations, and decision-making across the business.
Agents in Production
Latest Trends in MLOps
2025 THEME: MLOps & Organizational Scale
Governance, Auditability & Model Risk Management
This track covers how teams manage AI risk in production—through model governance, audit trails, compliance workflows, and strategies for monitoring model behavior over time.
MLOps for Smaller Teams
Not every team has a platform squad or unlimited infra budget. This track shares practical approaches to shipping ML with lean teams—covering lightweight tooling, automation shortcuts, and lessons from teams doing more with less.
ML Lifecycle Security
ML Training Lifecycle
Scoping and Delivering Complex AI Projects
2025 THEME: LLM Infrastructure & Operations
LLMs on Kubernetes
This track covers the key architectural choices and infra strategies behind scaling AI and LLM systems in production—from bare metal to Kubernetes, GPU scheduling to inference optimization. Learn what it really takes to build and operate reliable GenAI and agent platforms at scale.
ML Deployments on Prem
LLM Observability
Data Engineering in an LLM Era
Inference Optimization & Scaling
Multimodal Systems in Production
Our Expo is where innovation, ideas, and connections come to life
Transform from attendee to active participant by leveling-up your professional contacts, exchanging ideas, and even grabbing the mic to share a passion project.
Make New Connections
Connect with AI Practitioners
Brain Dates
Speakers' Corner
Vendor Booths
Community Square
Startup Zone
Hands-on Sessions
Austin Parties
Expo Expo Expo Expo Expo Expo Expo Expo Expo Expo Expo Expo
40+ Technical Workshops and Industry Case Studies












Event Speakers
We will release it soon.
Meet the experts bringing techniques, best practices, and strategies to this year’s stage.
Arun Malik
Arun Malik
ABOUT THE SPEAKER:
We redesigned frontline incident response around AI agents that do not just suggest fixes but execute them, across more than 12 million devices and tens of thousands of incidents a month. Structurally, three things changed. First, agents stopped getting broad human-equivalent access and instead call tools through a governed interface, with permissions scoped down to individual functions and parameter values, so a compromised or confused agent has a bounded blast radius. Second, human approval moved from a blanket gate to a targeted one, applied only to sensitive or irreversible actions and routed by how familiar the problem is and how reversible the action is. Third, we stopped paying full model-inference cost for repeated work by promoting an agent’s proven, validated behavior into deterministic playbooks that run at near-zero token cost, which cut agent running cost by more than 70 percent over eight months while incident volume doubled.
Attendees will leave able to decide what an agent should be allowed to do at all, where a human actually adds signal versus just latency, and how to drive the cost of autonomy down over time instead of letting it grow. I will be specific about what broke first and the guardrails we only added after an incident.
TALK TITLE:
TRACK:
Technical Level:
ABSTRACT:
We redesigned frontline incident response around AI agents that do not just suggest fixes but execute them, across more than 12 million devices and tens of thousands of incidents a month. Structurally, three things changed. First, agents stopped getting broad human-equivalent access and instead call tools through a governed interface, with permissions scoped down to individual functions and parameter values, so a compromised or confused agent has a bounded blast radius. Second, human approval moved from a blanket gate to a targeted one, applied only to sensitive or irreversible actions and routed by how familiar the problem is and how reversible the action is. Third, we stopped paying full model-inference cost for repeated work by promoting an agent’s proven, validated behavior into deterministic playbooks that run at near-zero token cost, which cut agent running cost by more than 70 percent over eight months while incident volume doubled.
Attendees will leave able to decide what an agent should be allowed to do at all, where a human actually adds signal versus just latency, and how to drive the cost of autonomy down over time instead of letting it grow. I will be specific about what broke first and the guardrails we only added after an incident.
Andy McMahon
Andy McMahon
ABOUT THE SPEAKER:
As organisations move from single models to connected agent systems, the challenge shifts to how agents interact, how they are evaluated, and how their behaviour can be monitored in real production environments.
This presentation explores what it takes to operationalise agentic AI in practice – from observability and evaluation to deploying agents safely and reliably across enterprise workflows.
Through real-world examples, we look at how teams are building responsible AgentOps frameworks to scale multi-agent systems in production while maintaining control, trust and measurable business impact.
TALK TITLE:
TRACK:
Technical Level:
ABSTRACT:
As organisations move from single models to connected agent systems, the challenge shifts to how agents interact, how they are evaluated, and how their behaviour can be monitored in real production environments.
This presentation explores what it takes to operationalise agentic AI in practice – from observability and evaluation to deploying agents safely and reliably across enterprise workflows.
Through real-world examples, we look at how teams are building responsible AgentOps frameworks to scale multi-agent systems in production while maintaining control, trust and measurable business impact.
Yegor Denisov-Blanch
Yegor Denisov-Blanch
ABOUT THE SPEAKER:
TALK TITLE:
TRACK:
Technical Level:
ABSTRACT:
Matt Mazzarell
Matt Mazzarell
ABOUT THE SPEAKER:
“One of the most difficult problems every company faces is understanding its customers completely. Customer lifetime value, attrition risk, and purchase propensity are all solvable with AI/ML — but how do we combine these modeling scores to initiate the right action with the right customer at any point in time?
Agentic applications help us make the best possible decisions when interpreting complex, high-volume signals from our customers. An agentic application gives end users visuals that explain key insights, with an agent in the loop to ensure nothing is missed. Context is everything: when done correctly, the agent always has the appropriate understanding to build an action plan that improves customer health and profitability.
In this session, we’ll show you how to build agentic apps from ideation to a finished product that interacts with customers. You’ll take away practical tips for using agentic coding frameworks, curating complete customer data products, and building customer-facing agents — capped off with a live demo of Teradata’s Customer Lifetime Value Agentic App.”
TALK TITLE:
TRACK:
Technical Level:
ABSTRACT:
“One of the most difficult problems every company faces is understanding its customers completely. Customer lifetime value, attrition risk, and purchase propensity are all solvable with AI/ML — but how do we combine these modeling scores to initiate the right action with the right customer at any point in time?
Agentic applications help us make the best possible decisions when interpreting complex, high-volume signals from our customers. An agentic application gives end users visuals that explain key insights, with an agent in the loop to ensure nothing is missed. Context is everything: when done correctly, the agent always has the appropriate understanding to build an action plan that improves customer health and profitability.
In this session, we’ll show you how to build agentic apps from ideation to a finished product that interacts with customers. You’ll take away practical tips for using agentic coding frameworks, curating complete customer data products, and building customer-facing agents — capped off with a live demo of Teradata’s Customer Lifetime Value Agentic App.”
Antonio Bustamante
Antonio Bustamante
ABOUT THE SPEAKER:
Everyone building on frontier models hits the same wall: 80% of the way there in a weekend, then an exponentially expensive climb toward the 99%+ that operational systems need. This talk is the honest map of that climb, from a team that now runs AI over millions of documents, images and videos a month for customers in logistics, fleet management, automotive and financial services who need the answer to be right every time.
We will walk through the ladder nobody budgets for: retries, then queues when the model is down for three hours, then rate limits, then discovering that 95% is not enough for transactional data, then discovering that the model cannot tell you how confident it is. We will show two failures from our own production history, a customer whose single engineer racked up $30K of usage in a month because nothing was watching, and our first churn, on 500-page reports with a hundred rows per page, a problem we still consider unsolved. And we will show what we changed: a harness that treats AI as a deterministic step inside durable workflows rather than as an open-ended agent, decisions expressed as a verified tree the model must traverse, algorithmic confidence scoring on top of models that provide none, routing anything under 95% to a human whose verdict feeds back into the system, semantic checks against instructions smuggled into the data, and, counterintuitively, encouraging customers to build their own independent monitoring of us. One customer’s users went from eight to nine hours a week on a task to about thirty minutes, and that number was measured by them, not by us.
Attendees will leave with five patterns they can apply Monday: confidence scoring for models that lack it, decision trees over open-ended prompts, exception routing with feedback loops, semantic security checks on inbound data, and customer-owned evaluation. They will also leave with a thesis we did not start with: chat is single-player AI; the next decade of software is ambient AI that runs the same process a hundred thousand times a day, unattended, and behaves the same way every time.
TALK TITLE:
TRACK:
Technical Level:
ABSTRACT:
Everyone building on frontier models hits the same wall: 80% of the way there in a weekend, then an exponentially expensive climb toward the 99%+ that operational systems need. This talk is the honest map of that climb, from a team that now runs AI over millions of documents, images and videos a month for customers in logistics, fleet management, automotive and financial services who need the answer to be right every time.
We will walk through the ladder nobody budgets for: retries, then queues when the model is down for three hours, then rate limits, then discovering that 95% is not enough for transactional data, then discovering that the model cannot tell you how confident it is. We will show two failures from our own production history, a customer whose single engineer racked up $30K of usage in a month because nothing was watching, and our first churn, on 500-page reports with a hundred rows per page, a problem we still consider unsolved. And we will show what we changed: a harness that treats AI as a deterministic step inside durable workflows rather than as an open-ended agent, decisions expressed as a verified tree the model must traverse, algorithmic confidence scoring on top of models that provide none, routing anything under 95% to a human whose verdict feeds back into the system, semantic checks against instructions smuggled into the data, and, counterintuitively, encouraging customers to build their own independent monitoring of us. One customer’s users went from eight to nine hours a week on a task to about thirty minutes, and that number was measured by them, not by us.
Attendees will leave with five patterns they can apply Monday: confidence scoring for models that lack it, decision trees over open-ended prompts, exception routing with feedback loops, semantic security checks on inbound data, and customer-owned evaluation. They will also leave with a thesis we did not start with: chat is single-player AI; the next decade of software is ambient AI that runs the same process a hundred thousand times a day, unattended, and behaves the same way every time.
D. Sculley
D. Sculley
ABOUT THE SPEAKER:
We spend a lot of time thinking about operational issues in AI related to deployment, somewhat less time thinking about adoption, or (dare we say it) acceptance. This talk will touch on some technical pieces in the current AI ops landscape including streaming systems, planning, latency, and on-device models, but most of the time will be spent looking at ways we can move beyond the stale framing of a chatbot, assistant, or customer service agent.
TALK TITLE:
TRACK:
Technical Level:
ABSTRACT:
We spend a lot of time thinking about operational issues in AI related to deployment, somewhat less time thinking about adoption, or (dare we say it) acceptance. This talk will touch on some technical pieces in the current AI ops landscape including streaming systems, planning, latency, and on-device models, but most of the time will be spent looking at ways we can move beyond the stale framing of a chatbot, assistant, or customer service agent.
Nadia Rauch
Nadia Rauch
ABOUT THE SPEAKER:
We built a multi-agent pipeline to automate a complex, document-intensive enterprise workflow. The initial system ran sequentially through a chain of specialized agent roles, each handling a distinct task in the process, using a single frontier model throughout. It worked. It was also slow and expensive, and we didn’t know why.
Rather than optimize blindly, we profiled first. The results were not where we expected: 67% of total latency came from a small minority of the agent roles, and the primary bottleneck was not the model — it was sequential chaining: independent work was being processed one step at a time instead of concurrently. Identifying and parallelizing the roles with no inter-dependency reduced end-to-end runtime by roughly 40%.*
The second experiment compared model tiers (frontier, mid-tier, lightweight) across each agent role independently, measuring accuracy, latency, and cost per role. The finding cuts against the default assumption: the roles that appeared most cognitively demanding required frontier models, but the accuracy gap was smaller than expected. The roles where model downgrade failed were the ones responsible for precise structured extraction — tasks where errors propagate silently downstream and surface only at the output. Swapping to mid-tier models on roles that tolerated it reduced per-run cost by ~40%, with an estimated <2% accuracy impact at the role level and <1% at the pipeline output level.*
The third experiment compared orchestration harnesses — evaluating how the choice of agentic framework affects runtime overhead, observability, and the ease of implementing the parallelization and model-swap changes described above. Framework choice turned out to matter more than expected for operational concerns: debugging multi-agent failures, tracing costs per agent, and modifying execution flow without rewriting pipeline logic.
Operating in a regulated enterprise environment added one constraint worth naming: every agent decision needs to be auditable. This ruled out certain optimization shortcuts that would have been acceptable in other contexts and shaped how we defined “accurate enough” per role.
This talk covers the profiling methodology, the per-role model comparison framework, the parallelization decisions, the harness comparison, and the operational lessons — including what we’d instrument from day one if we rebuilt the system today.
*Cost and accuracy figures for the parallelization and model-tier experiments are preliminary; the formal evaluation is in progress and will be updated with measured results before the talk.
TALK TITLE:
TRACK:
Technical Level:
ABSTRACT:
We built a multi-agent pipeline to automate a complex, document-intensive enterprise workflow. The initial system ran sequentially through a chain of specialized agent roles, each handling a distinct task in the process, using a single frontier model throughout. It worked. It was also slow and expensive, and we didn’t know why.
Rather than optimize blindly, we profiled first. The results were not where we expected: 67% of total latency came from a small minority of the agent roles, and the primary bottleneck was not the model — it was sequential chaining: independent work was being processed one step at a time instead of concurrently. Identifying and parallelizing the roles with no inter-dependency reduced end-to-end runtime by roughly 40%.*
The second experiment compared model tiers (frontier, mid-tier, lightweight) across each agent role independently, measuring accuracy, latency, and cost per role. The finding cuts against the default assumption: the roles that appeared most cognitively demanding required frontier models, but the accuracy gap was smaller than expected. The roles where model downgrade failed were the ones responsible for precise structured extraction — tasks where errors propagate silently downstream and surface only at the output. Swapping to mid-tier models on roles that tolerated it reduced per-run cost by ~40%, with an estimated <2% accuracy impact at the role level and <1% at the pipeline output level.*
The third experiment compared orchestration harnesses — evaluating how the choice of agentic framework affects runtime overhead, observability, and the ease of implementing the parallelization and model-swap changes described above. Framework choice turned out to matter more than expected for operational concerns: debugging multi-agent failures, tracing costs per agent, and modifying execution flow without rewriting pipeline logic.
Operating in a regulated enterprise environment added one constraint worth naming: every agent decision needs to be auditable. This ruled out certain optimization shortcuts that would have been acceptable in other contexts and shaped how we defined “accurate enough” per role.
This talk covers the profiling methodology, the per-role model comparison framework, the parallelization decisions, the harness comparison, and the operational lessons — including what we’d instrument from day one if we rebuilt the system today.
*Cost and accuracy figures for the parallelization and model-tier experiments are preliminary; the formal evaluation is in progress and will be updated with measured results before the talk.
Kalpesh Sutaria
Kalpesh Sutaria
ABOUT THE SPEAKER:
A leaderboard win is not a product. Nemotron Retriever’s models rank #1 on RTEB — but topping a benchmark and running efficiently inside a customer’s production are two very different problems. This talk is the engineering story of closing that gap.
I’ll walk through our journey rebuilding the Retriever inference stack in Rust with a single obsession: treating state-of-the-art performance as a first-class product requirement, not a post-hoc optimization. We’ll get concrete about the decisions that mattered — what we measured, where we spent effort, the throughput, memory, and footprint wins we chased, and how dramatic efficiency gains unlocked deployment scenarios (including edge and on-device) that simply weren’t possible before. I’ll also share what didn’t work, the tension between shipping fast and building durable, and how we leaned on AI-assisted development to move faster than the roadmap assumed.
You’ll leave with a mental model for treating inference performance as a product and go-to-market lever — and a practical playbook for taking research-grade models to production without leaving speed, cost, or reach on the table.
Key takeaways:
- Why “performance is the product”: efficiency is an adoption and go-to-market lever, not a cost center.
- Concrete decisions from a Rust-based inference rebuild — what to measure, where to optimize, and how to know it worked.
- How latency and footprint reductions open entirely new deployment surfaces (edge, on-device) for the same models.
- Navigating the research-to-production seam: turning SoTA benchmark results into reliable, cheap, fast serving customers can bet on.
Who should attend / level? AI engineers, ML platform/infrastructure engineers, and engineering leaders who build, deploy, or operate inference and serving systems. Intermediate.
TALK TITLE:
TRACK:
Technical Level:
ABSTRACT:
A leaderboard win is not a product. Nemotron Retriever’s models rank #1 on RTEB — but topping a benchmark and running efficiently inside a customer’s production are two very different problems. This talk is the engineering story of closing that gap.
I’ll walk through our journey rebuilding the Retriever inference stack in Rust with a single obsession: treating state-of-the-art performance as a first-class product requirement, not a post-hoc optimization. We’ll get concrete about the decisions that mattered — what we measured, where we spent effort, the throughput, memory, and footprint wins we chased, and how dramatic efficiency gains unlocked deployment scenarios (including edge and on-device) that simply weren’t possible before. I’ll also share what didn’t work, the tension between shipping fast and building durable, and how we leaned on AI-assisted development to move faster than the roadmap assumed.
You’ll leave with a mental model for treating inference performance as a product and go-to-market lever — and a practical playbook for taking research-grade models to production without leaving speed, cost, or reach on the table.
Key takeaways:
- Why “performance is the product”: efficiency is an adoption and go-to-market lever, not a cost center.
- Concrete decisions from a Rust-based inference rebuild — what to measure, where to optimize, and how to know it worked.
- How latency and footprint reductions open entirely new deployment surfaces (edge, on-device) for the same models.
- Navigating the research-to-production seam: turning SoTA benchmark results into reliable, cheap, fast serving customers can bet on.
Who should attend / level? AI engineers, ML platform/infrastructure engineers, and engineering leaders who build, deploy, or operate inference and serving systems. Intermediate.
Poonam Lamba
Poonam Lamba
ABOUT THE SPEAKER:
We redesigned distributed GPU orchestration for RL post-training and batch inference in the open-source llm-d platform. Structurally, we replaced static GPU/TPU locking with a three-tier co-operative time-slicing system:
- Application Layer: Workloads signal phase boundaries (rollouts, training, batch inference) via explicit acquire() and yield() APIs.
- Cluster Orchestrator: Manages lock queues to dynamically interleave complementary jobs onto shared hardware during idle phases.
- Node Snapshot Agent: Executes fast sub-second state swaps between GPU/TPU VRAM and host DRAM, enabling instant context switching without container restarts.
Attendees will walk away with:
- Drive 70%+ GPU/TPU Utilization: Understand how time-slicing reclaims idle hardware during RL loops and batch inference without impacting convergence.
- Architect Rapid Memory Swapping: Apply VRAM-to-DRAM snapshotting strategies for ultra-fast GPU/TPU context switching.
- Deploy on Kubernetes: Configure llm-d and K8s orchestrators to interleave RL and batch inference on shared clusters.
TALK TITLE:
TRACK:
Technical Level:
ABSTRACT:
We redesigned distributed GPU orchestration for RL post-training and batch inference in the open-source llm-d platform. Structurally, we replaced static GPU/TPU locking with a three-tier co-operative time-slicing system:
- Application Layer: Workloads signal phase boundaries (rollouts, training, batch inference) via explicit acquire() and yield() APIs.
- Cluster Orchestrator: Manages lock queues to dynamically interleave complementary jobs onto shared hardware during idle phases.
- Node Snapshot Agent: Executes fast sub-second state swaps between GPU/TPU VRAM and host DRAM, enabling instant context switching without container restarts.
Attendees will walk away with:
- Drive 70%+ GPU/TPU Utilization: Understand how time-slicing reclaims idle hardware during RL loops and batch inference without impacting convergence.
- Architect Rapid Memory Swapping: Apply VRAM-to-DRAM snapshotting strategies for ultra-fast GPU/TPU context switching.
- Deploy on Kubernetes: Configure llm-d and K8s orchestrators to interleave RL and batch inference on shared clusters.
Ishaan Sehgal
Ishaan Sehgal
ABOUT THE SPEAKER:
At Omnara, long-running agent sessions exposed a failure mode hidden by short-lived agents: the agent’s state was coupled to the process, model provider, or runtime executing it. When a worker crashed, a client disconnected, or execution moved to another machine, recovering the agent’s work became brittle.
We redesigned agent execution around an append-only session log as the source of truth. Model outputs, tool calls and results, user interventions, and other state transitions are persisted as ordered events; the live agent state becomes a replayable projection of that history.
This structural change decouples agent identity from any one model, worker, or harness. It enables crash recovery, resumability, branching, real-time observability, and migration across models and machines, but introduces difficult systems questions around ordering, idempotency, partial tool execution, checkpointing, compaction, concurrent writers, and log ownership.
This session walks through the production failures that motivated the redesign, the resulting event model and recovery path, and the tradeoffs we encountered. Using production traces and forced-failure examples, we will show what happens when a worker dies mid-tool call, how a session resumes under a different runtime, and how replay costs change as histories grow.
Attendees will leave with a practical blueprint for deciding what belongs in the durable log, what can be recomputed, and how to build agent sessions that survive process, machine, and model failure without locking continuity to a single provider.
TALK TITLE:
TRACK:
Technical Level:
ABSTRACT:
At Omnara, long-running agent sessions exposed a failure mode hidden by short-lived agents: the agent’s state was coupled to the process, model provider, or runtime executing it. When a worker crashed, a client disconnected, or execution moved to another machine, recovering the agent’s work became brittle.
We redesigned agent execution around an append-only session log as the source of truth. Model outputs, tool calls and results, user interventions, and other state transitions are persisted as ordered events; the live agent state becomes a replayable projection of that history.
This structural change decouples agent identity from any one model, worker, or harness. It enables crash recovery, resumability, branching, real-time observability, and migration across models and machines, but introduces difficult systems questions around ordering, idempotency, partial tool execution, checkpointing, compaction, concurrent writers, and log ownership.
This session walks through the production failures that motivated the redesign, the resulting event model and recovery path, and the tradeoffs we encountered. Using production traces and forced-failure examples, we will show what happens when a worker dies mid-tool call, how a session resumes under a different runtime, and how replay costs change as histories grow.
Attendees will leave with a practical blueprint for deciding what belongs in the durable log, what can be recomputed, and how to build agent sessions that survive process, machine, and model failure without locking continuity to a single provider.
Fuzail Khan
Fuzail Khan
ABOUT THE SPEAKER:
The ranking and recommendation systems landscape is being transformed in the generative era. This talk reports on the experience of building and shipping the training infrastructure behind the first generative recommender in production at Meta, covering both stages of the recipe: pre-training to acquire the generative capability and post-training RL to align generation with the ranking objective.
Generative recommenders bring distinct challenges to end-to-end performance and scalability. This primarily arises from a mixed architecture that consists of both recommender-native large sparse embedding tables and LLM-based decoders. This then generates semantic IDs translating to real-world use cases in production such as finding the right advertisement for a given user. We inherit the communication profile of a sparse recommender as well as the autoregressive nature of a large language model for which an end-to-end systems blueprint simply does not exist.
For pre-training, we make the significant change from discriminative to generative recommendation. We talk about feature processing, data loading and the user-modeling path while building the LLM decoder and semantic ID tokenization on top while addressing real-world productionization challenges and end-to-end LLM performance analysis.
Reinforcement learning was implemented as an extensible framework where rewards, losses, RL algorithms, reference models and generation strategies are pluggable. We’ll walk through the reward design and the end-to-end post-training pipeline that prioritizes scalability at the production scale at Meta.
We’ll close with end-to-end optimization work – redundant computation elimination, specialized kernels for very short sequences, dense-sparse pipelining and hybrid embedding placement that satisfies large-scale performance requirements in compute and throughput.
We believe the key output from this session is leaving attendees with a crisp understanding of generative recommendation systems in large-scale production. We want to ensure we stay practical and address real-world production challenges that are relevant to developers and builders in AI infrastructure today. We do this by diving into the technicalities of enabling a large-scale generative retrieval system as well as concrete performance optimizations that enable the shift from a research prototype to a highly-optimized production system critical to revenue. We also feel the training systems and infrastructure-side of LLMs in production is rarely addressed at least relative to model architecture and quality, and we hope to fill that gap with this session.
TALK TITLE:
TRACK:
Technical Level:
ABSTRACT:
The ranking and recommendation systems landscape is being transformed in the generative era. This talk reports on the experience of building and shipping the training infrastructure behind the first generative recommender in production at Meta, covering both stages of the recipe: pre-training to acquire the generative capability and post-training RL to align generation with the ranking objective.
Generative recommenders bring distinct challenges to end-to-end performance and scalability. This primarily arises from a mixed architecture that consists of both recommender-native large sparse embedding tables and LLM-based decoders. This then generates semantic IDs translating to real-world use cases in production such as finding the right advertisement for a given user. We inherit the communication profile of a sparse recommender as well as the autoregressive nature of a large language model for which an end-to-end systems blueprint simply does not exist.
For pre-training, we make the significant change from discriminative to generative recommendation. We talk about feature processing, data loading and the user-modeling path while building the LLM decoder and semantic ID tokenization on top while addressing real-world productionization challenges and end-to-end LLM performance analysis.
Reinforcement learning was implemented as an extensible framework where rewards, losses, RL algorithms, reference models and generation strategies are pluggable. We’ll walk through the reward design and the end-to-end post-training pipeline that prioritizes scalability at the production scale at Meta.
We’ll close with end-to-end optimization work – redundant computation elimination, specialized kernels for very short sequences, dense-sparse pipelining and hybrid embedding placement that satisfies large-scale performance requirements in compute and throughput.
We believe the key output from this session is leaving attendees with a crisp understanding of generative recommendation systems in large-scale production. We want to ensure we stay practical and address real-world production challenges that are relevant to developers and builders in AI infrastructure today. We do this by diving into the technicalities of enabling a large-scale generative retrieval system as well as concrete performance optimizations that enable the shift from a research prototype to a highly-optimized production system critical to revenue. We also feel the training systems and infrastructure-side of LLMs in production is rarely addressed at least relative to model architecture and quality, and we hope to fill that gap with this session.
Siddharth Jain
Siddharth Jain
ABOUT THE SPEAKER:
Teams often give an agent a service credential, add a human approval step, and call the workflow governed. That design breaks down when the agent can revise payloads, retry writes, chain tools, or act across systems with different permission models. The result is an accountability gap: the organization can see that a service account acted, but not necessarily who authorized the business intent, which payload was approved, whether a retry duplicated work, or what changed between proposal and execution.
This session presents a production control model for agent workflows that make consequential writes. It shows how to separate the business-intent identity from the concrete operation; classify tools by impact; issue short-lived, least-privilege credentials only after validation; bind human approval to a canonical payload hash and policy version; execute through controlled services with idempotency keys; and reconcile external state before declaring success. It also covers the evidence record needed to answer four operational questions: who requested the action, what the agent proposed, what policy and human approved, and what the downstream system actually did.
The talk focuses on failure modes that appear after the demo works: stale approvals, overbroad agent permissions, duplicate writes after retries, silent policy changes, and actions whose outcome is unknown. Attendees will leave with a lifecycle they can map to their own platform, concrete interfaces between model output and deterministic controls, and an audit schema that supports incident response, compliance review, and day-to-day operations without turning every agent into a bespoke security project.
TALK TITLE:
TRACK:
Technical Level:
ABSTRACT:
Teams often give an agent a service credential, add a human approval step, and call the workflow governed. That design breaks down when the agent can revise payloads, retry writes, chain tools, or act across systems with different permission models. The result is an accountability gap: the organization can see that a service account acted, but not necessarily who authorized the business intent, which payload was approved, whether a retry duplicated work, or what changed between proposal and execution.
This session presents a production control model for agent workflows that make consequential writes. It shows how to separate the business-intent identity from the concrete operation; classify tools by impact; issue short-lived, least-privilege credentials only after validation; bind human approval to a canonical payload hash and policy version; execute through controlled services with idempotency keys; and reconcile external state before declaring success. It also covers the evidence record needed to answer four operational questions: who requested the action, what the agent proposed, what policy and human approved, and what the downstream system actually did.
The talk focuses on failure modes that appear after the demo works: stale approvals, overbroad agent permissions, duplicate writes after retries, silent policy changes, and actions whose outcome is unknown. Attendees will leave with a lifecycle they can map to their own platform, concrete interfaces between model output and deterministic controls, and an audit schema that supports incident response, compliance review, and day-to-day operations without turning every agent into a bespoke security project.
WHAT YOU’LL LEARN:
- Do not let the model hold broad standing credentials; mint scoped identity for each authorized operation.
- Bind approval to material fields, a canonical payload hash, and the policy version so edits invalidate stale consent.
- Treat every consequential write as a durable state machine with explicit recovery paths, not as a single tool call.
- Separate retry from reconciliation so an ambiguous timeout does not become a duplicate action.
- Design the audit record as an operating interface: it should reconstruct who requested, what was proposed, what was approved, what executed, and what the downstream system recorded.
PREREQUISITE KNOWLEDGE
Latest News
Why attend
Event Parties & Networking
Explore Frontier Tools & Startups
Give your team an edge with insights, skills, and connections from the industry’s top innovators —
click here to see the exhibiting sponsors.
Grow industry influence
Join Brain Dates, Speaker’s Corner, Community Square, or deliver a talk to share your expertise and amplify your industry impact.
Curated by AI Practitioners
All sessions and workshops have been hand-picked by a Steering Committee of fellow AI practitioners who obsess about delivering real-world value for attendees.
Denys Linkov
Event Co-Chair & Head of ML at WiseDocs
“We built this year’s summit around practical takeaways. Not theory but actual workflows, strategies, and the next three steps for your team. We didn’t want another ‘Intro to RAG’ talk. We wanted the things people are debugging, scaling, and fixing right now.”
Volunteering
Apply for the opportunity to get exclusive behind the scenes access to the MLOps World experience while growing your network and skills in real-world artificial intelligence.
Austin
Renaissance Austin Hotel
Once again our venue is the beautiful Renaissance Austin Hotel which delivers an exceptional 360 experience for attendees, complete with restaurants, rooftop bar, swimming pool, spa, exercise facilities, and nearby nature walks. Rooms fill up fast, so use our code (MLOPS25) for discounted rates.
Choose Your Email Adventure
Join our Monthly Newsletter to be first to get expert videos from our flagship events and community offers including the latest Stack Drops.
Join Summit Updates to learn about event-specific news like ticket promos and agenda updates as well invites to join our free online Stack Sessions.
Choose what works best for you and update your email preferences at any time.
Hear From Past Attendees
Data and AI Scientist, Consultant, Podcaster
Free Virtual October 6-7 | In-person October 8-9
What Your Ticket Includes
- Full access to Summit sessions – Day 1 (Oct 8) & Day 2 (Oct 9) in Austin
- Bonus virtual program – live talks and workshops on Oct 6 & 7
- Hands-on learning – in-person talks, virtual workshops, and skill-building sessions
- Food & networking – connect with peers over meals, socials, and receptions
- AI-powered event app – desktop & mobile access for networking and schedules
- Networking events – structured meetups and community mixers
- On-demand replays – access to all post-summit videos
- 30 days of O’Reilly online learning – unlimited access to books, courses, and videos from O’Reilly and 200+ publishers
Past Agenda
This agenda is still subject to changes.
Join free virtual sessions October 6–7, then meet us in Austin for in-person case studies, workshops, and expo October 8–9
FAQ
When and where is the event?
The in-person portion of MLOps World | GenAI Summit takes place October 8-9, 2025 at the Renaissance Austin Hotel.
Address: 9721 Arboretum Blvd, Austin, TX 78759, United States See booking details.
What’s included with my ticket?
- Live training courses
- In-depth learning paths
- Interactive coding environments
- Certification prep materials
- Most major AI publications
Is there a virtual option?
What types of sessions can I expect?
Are there more active types of experiences?
How do I register?
Can I cancel or transfer my ticket?
Are discounts available for group ticket purchases?
Who typically attends MLOps World?
Will slides or recordings be available after the event?
Yes. The majority of presenters grant permission for their sessions to be recorded and shared. These recordings are made available after the event. The best way to be notified when new learning resources are released is by subscribing to our newsletter.
What if I have dietary or accessibility needs?
How do I apply to speak?
Submit your proposal via the Call for Speakers link in our site header (available ahead of each event) or subscribe to our newsletter for MLOps and other speaking alerts. Learn more
What kinds of talks are accepted?
Are speaker slots paid or unpaid?
What’s the speaker deadline for slides or submissions?
Do speakers get free tickets or travel support?
Can I speak virtually or only in-person?
Are sessions recorded? Will they be shared publicly?
What kind of A/V support or setup is provided?
What are the sponsorship packages and benefits?
How do I become a sponsor?
Visit our sponsor page to get more details and download our Sponsorship Guide, or contact Faraz Thambi at [email protected] to discuss availability and options.
What is the audience profile?
Attendees include ML/Data Engineers, Developers, Solution Architects / Principal Engineers, ML/AI Infra Leads, Technical Leaders, and Senior Leadership (Director, VP, C-suite, Founder) decision-makers from startups, scaleups, and enterprises across North America and around the globe.
Can I sponsor the virtual component or a specific track only?
How is lead capture handled?
Will there be booth space? How big? What’s included?
Yes. Booth packages vary in size depending on the tier; they range from a 20’x20’ island booth (Platinum) to a 6’ x 10’ draped booth (Bronze). Please see the guide for full specifications.
Can we run our own bespoke event or session?
Yes. We offer limited opportunities for sponsor-hosted workshops, roundtables, and after-hours events, pending approval and availability.
Are there other ways to get involved as a sponsor?
Yes, leading companies can apply to contribute discounts and free trials to our audience of AI/ML practitioners as part of our Stack Drop and Community Code programs. Learn more from our blog or email [email protected]