© Mapbox, © OpenStreetMap
Arun Addagatla

Arun Addagatla

Founding AI Engineer @ Lamatic.ai | AI Systems Infrastructure · Agent Runtimes · Production LLM Ops

Mumbai, India

Actions

I'm Arun Addagatla, an AI systems engineer who builds infrastructure for durable, production-grade agents - not slide-deck demos. As the first engineering hire at Lamatic.ai (TechCrunch Startup Battlefield 200, Cloudflare Workers Launchpad), I've shipped over 80% of the platform: serverless agent execution, multi-agent orchestration, production memory and RAG layers, and the runtime glue that keeps workflows alive past a single HTTP request.

At Lamatic, I architected a serverless executor handling Millions of Monthly agent runs and a deployment engine that cut latency from 2 minutes to 15 seconds (~87%). I built an LLM-as-a-judge evaluation framework, a Multi-Agent Supervisor with semantic RAG, Kubernetes ETL pipelines (Drive, S3, SharePoint), and a multimodal hiring agent that reduced recruiter workload by 70%. Most of the hard lessons came from reliability at scale—retries, per-tenant isolation, queue orchestration, and what breaks after the millionth run.

Before Lamatic, at Samespace, I fine-tuned Mistral and LLaMA-2 with LoRA/PEFT, built an LLM inference engine at 106 tokens/sec (dynamic batching, multi-GPU), and drove Whisper V3 ASR to 0.1–0.4s latency with ONNX, TensorRT, and Triton—that's where I learned to make AI dependable under load, not just impressive in a notebook.

Outside of work, I write on Medium about agent infrastructure, inference optimization, and MCP—70k+ reads from engineers who want the hard systems problems explained clearly. I hold a B.E. in Computer Engineering from the University of Mumbai (9.6 GPA).

Area of Expertise

  • Information & Communications Technology

Topics

  • AI/LLMs
  • SLMs
  • LLMOps
  • GenAI
  • AgenticAI

The Model Was Fine. Your Context Was Broken.

You can swap in the best model on the leaderboard and your agent will still fail - because the bug was never in the model. It was in what you fed it. This talk is a postmortem on the failures that actually block agents from shipping: the ones that happen before the first token is generated, in the invisible step where you decide what the model gets to see. After running multi-agent workflows across 1M+ executions a month, I can tell you the model is almost never the problem. The context is.

Prompt engineering taught us to obsess over wording. But in production, agents don't fail because a prompt was phrased poorly - they fail because the retrieval missed, the memory was stale, the tool schemas ate half the window, or the supervisor's summary dropped the one fact the worker agent needed. These are not prompting bugs. They are context engineering bugs, and they belong to a discipline most teams are doing by accident.

I'll make that discipline explicit by treating context assembly as a compile step - a pipeline that turns messy world state into the exact tokens the model sees:

- Context as a compiler, not a prompt - retrieval, reranking, memory injection, and tool-state snapshots, and why order changes the output
- Multi-agent context routing - what a supervisor hands to a specialist, what comes back, and what silently gets lost in translation
- Memory tiers under load - hot (recent turns), warm (session summaries), cold (long-term RAG) - and which one breaks first
- Compression that lies - when summarization saves your token budget and when it quietly poisons the next decision
- Token economics - the budget war between system prompts, tool schemas, and the context you actually need
- Debugging what the model saw - traces, diffs, and the one question that finds most agent bugs: "What was actually in the window?"

You'll leave with a mental model for context engineering as infrastructure, a checklist of failure modes to design against before they reach production, and a walkthrough of real traces where the fix was never a better prompt - it was better context.

Prompt engineering got us to the demo. Context engineering is what gets you to the millionth run.

Agents That Don't Forget Where They Were

Your agent works in the demo. Then it runs for nine minutes, calls twelve tools, waits on a human, and crashes at step seven. The notebook architecture quietly falls apart. This talk is about why: agents are long-running stateful workflows, but we deploy them on short-lived stateless infrastructure. That mismatch kills more agents than bad prompts ever will.

Serverless runtimes assume work finishes fast and forgets between calls. Agents violate both. They block on slow tools. They wait on humans. They hit execution limits mid-thought. They get retried-and replay side effects they already committed. The failures are distributed-systems failures: lost progress, duplicated actions, orphaned runs.

I'll share the patterns we use to run millions of agent executions on serverless, applicable to Lambda, Cloud Run, Kubernetes, or Cloudflare Workers:

- Why agents break statelessness - wall-clock limits, cold starts, requests vs. workflows
- Durable execution - checkpointed steps that resume instead of restart
- Idempotency - making tool calls safe to replay
- Queue-orchestrated handoffs - decomposing "one big prompt" into recoverable units
- Human-in-the-loop as state - pausing for hours without holding a connection
- Per-tenant observability - debugging step 7 of 12 at 2am across thousands of runs

You'll leave with a vendor-neutral model for resumable agents, the failure modes to design against, and a live demo: we kill an agent mid-run and watch it resume from checkpoint.

Designing Fast, Cost-Effective AI Agents with Small Language Models

Most AI agents today are built around LLMs, but in production that often means higher latency, rising inference costs, and less predictable behavior.

This talk shows a more practical way to build agentic systems using small language models (SLMs). Instead of relying on a single large model for every task, we break the system into modular components powered by smaller, specialized models that handle routing, tool use, structured decisions, and narrow reasoning more efficiently.

Drawing from real-world experience building production AI systems, this session explores how to design agents that are faster, cheaper, and easier to control. We will cover architecture patterns such as specialist model routing, SLM-based tool calling, hybrid SLM-LLM pipelines, and the engineering tradeoffs between cost, latency, accuracy, and operational complexity.

We will also walk through how to deploy SLMs on your own server infrastructure and use Lamatic to build a production-grade agentic system end to end.

If you are building AI-powered products and want to move beyond demo-grade agents, this talk will help you rethink your architecture and design systems that scale in production.

Key takeaways
- How to design agentic systems using small language models
- When SLMs outperform LLMs in real production workflows
- Architecture patterns for faster, cheaper, and more controllable AI agents
- The tradeoffs between latency, cost, capability, and reliability
- How to combine SLMs and LLMs effectively in hybrid systems
- How to deploy SLMs on your own servers and build a production-grade agentic system with Lamatic

Contact Info:
- Portfolio Profile: https://arunaddagatla.vercel.app/
- Phone: +918485019026
- LinkedIn: https://www.linkedin.com/in/arun-addagatla/

Stop Building Frameworks, Start Building Runtimes

Every team that pushed agents past the demo rebuilt the same thing: a runtime. Not a framework - a runtime. Something to schedule work, manage memory, mediate tools, and trace failures. We didn't plan to build an operating system. We just needed agents that survive production.

This talk names what's hiding under every serious agent platform: the LLM OS. I'll map the seven layers every team converges on - prompts as shell, tools as syscalls, context as RAM, memory as filesystem, agents as processes, orchestrators as schedulers, inference routers as kernel dispatch - then show exactly where the OS metaphor helps and where it dangerously breaks down.

The real point: frameworks stall at the runtime boundary. Chaining libraries get you to a working demo and abandon you at scheduling, isolation, durable state, and eval gates. I'll show which layers you can buy, which you're forced to build, and which bottlenecks quietly kill agents before they ship - drawn from building a platform running millions of agent executions a month.

You'll leave able to look at any agent tool, protocol, or startup and immediately know which OS layer it competes in - and what it's leaving for you to build.

ICT Academy - Applications of Artificial Intelligence

60-minute virtual seminar for ~100 BSc-IT students on where AI is already winning — software, healthcare, finance, education, and the GenAI wave — closing with a live demo that shipped a working web app to the internet in under 8 minutes using only natural language.

April 2026 Dehra Dūn, India

Why LLMs Need Memory

Explored why memory is the missing infrastructure layer for production AI agents, covering long-term memory implementation, reliable and explainable AI systems at scale, and a live deep dive into Lamatic.ai's agent-building platform.

March 2026 Mumbai, India

Why Prompting Isn't Enough: The Case for RAG

Discussed why RAG is a system design problem, not just a feature, covering common failure modes, retrieval strategies, evaluation loops, and why prompt engineering alone falls short in production.

January 2026 Mumbai, India

Daytona Developers Club Tour '25: What is MCP and how it works

Presented how Model Context Protocol (MCP) enables LLMs to connect with live data and tools in real-time, breaking free from rigid APIs and static integrations. Included hands-on Python and OpenAI demos.

May 2025 Mumbai, India

Arun Addagatla

Founding AI Engineer @ Lamatic.ai | AI Systems Infrastructure · Agent Runtimes · Production LLM Ops

Mumbai, India

Actions

Please note that Sessionize is not responsible for the accuracy or validity of the data provided by speakers. If you suspect this profile to be fake or spam, please let us know.

Jump to top