Mezmo helps SRE teams run agents safely in production. AURA provides the open harness and control layer, with Mezmo adding governance and auditability.

San Francisco, CA
Joined August 2015
The cards have spoken. All Things Open was one for the books. 🔮✨ Great conversations about AI agents in production, AURA readings, and a reminder that fortune tellers make bad SREs. We're packing up the tarot cards and heading west to AGNTCon + MCPCon! ✈️ #opensourceSRE
1
23
Your AI agent has opinions. Cool. Can it back them up? Jev brings structured decisions to the incident workflow. AURA brings the context, permissions, and guardrails to keep those decisions from becoming production disasters. 🔗 mezmo.com/blog/where-jev-fit… #opensourceSRE
47
We've spent decades figuring out how to run production reliably. That experience still matters as agents take on more of the work. Mezmo CEO Tucker Callaway on why “You Can't Trust Vibes in Production” in CIO Dive. ciodive.com/spons/you-cant-t…
32
“You don’t try to control the toddler, you toddler-proof your house.” Mezmo CEO Tucker Callaway on governing AI agents, building trust in production, and Mezmo’s evolution. Read the feature in The AI & Software Report: theaisoftwarereport.com/tuck…
1
1
35
“There's no stack trace for ‘the agent was sure, and the agent was wrong.’” Green dashboards. Bad agent decisions. Welcome to a new kind of incident. Mezmo weighs in on why AI agents are rewriting the incident response playbook in @APMdigest. ow.ly/n64G50ZVH2G #OSS #SRE
60
That’s a wrap on DevOpsDays Rockies 🏔️ Great couple of days connecting with the community, talking all things AI, and sharing what we’re building with AURA. Thanks to everyone who connected with our team and to DevOpsDays Rockies for having us! #AURA #opensource #DevOpsDays
1
64
Got something weird happening with your agents? Bring it to AURA Office Hours. 💜 Bugs, broken workflows, unexpected behavior, half-built ideas. Bring what you’re working on and troubleshoot with the team. 📅 Today at 11 AM PDT 🔗 lnkd.in/gRFxky5v #AURA #SRE
68
Bring the weird things. 💜 Bugs, broken workflows, strange agent behavior, “why is it doing that?” moments. Bring it to AURA Office Hours. No deck. No pitch. Just engineers + AURA. 📅 Wednesdays @ 11 AM PDT 🔗 mezmo.zoom.us/meetings/97561… #AURA #OpenSource #SRE
66
Day 31 of 31 days of ✨AURA✨: Last day of the series. Greg gives AURA a Lambda function that can't reach an S3 bucket, and AURA finds the exact missing permission needed to fix it. The same pattern scales to bigger AWS problems. 🎬 youtu.be/4iPa3Aaugvc #31DaysOfAURA
1
106
Day 30 of 31 days of ✨AURA✨: Mike shows how AURA's approvals forward real identity, not just a yes or no. A fake key gets denied downstream. A real key runs under the approver's actual permissions, tracked end-to-end. 🎬 youtu.be/GbtJzJLXlfo #31DaysOfAURA #RuleProd
1
60
Day 29 of 31 days of ✨AURA✨: Mike shows how AURA keeps keys out of the agent entirely, forwarding request headers straight to downstream MCP servers at call time. No headers, no access. Built for multi-tenant setups and identity forwarding. 🎬 youtu.be/Jp3TccO4_Ak #SRE
1
84
Day 28 of 31 days of ✨AURA✨: Behind the scenes on how AURA goes from Grafana alert to talking in your Slack incident channel, approvals included. Built in about an hour. 🎬 youtu.be/9hWlh-xCzhQ #31DaysOfAURA #RuleProd
78
Day 27 of 31 days of ✨AURA✨: Nobody wants to hand-query system tables at 3 a.m. Three read-only workers check workload, storage, and replication across every replica, then send a trimmed report to Slack every 10 minutes. 🎬 youtube.com/watch?v=5WIJmQ0n… #31DaysOfAURA
1
89
Day 26 of 31 days of ✨AURA✨: Runbooks go stale. AURA finds 38 workloads and 0 runbooks, then opens a PR with real runbooks and proposes alert rules to address gaps that caused past outages. Nothing merges without approval. 🎬 youtu.be/eo8iUDkw3tE #31DaysOfAURA #SRE
1
83
Questions about AURA, or want to bring your own use case? Join us for AURA office hours every Wednesday at 11 am PDT, starting TODAY! Add it to your calendar: evt.to/dfqkvrm58wg111 #opensource #AURAmaxxing
1
49
Day 25 of 31 days of ✨AURA✨: AURA + Codex + Temporal handle a real product catalog bug end to end. AURA finds the cause in ClickHouse, Codex fixes and tests it, a human approves the diff, and AURA verifies the fix against live data. 🎬 youtu.be/kuUsojClQcA #31DaysOfAURA
1
1
264
Day 24 of 31 days of ✨AURA✨: The alert blamed checkout. AURA traced the 502s to unbounded memory growth in the cart service, then to the GitHub PR behind it. It paused for human approval before opening the issue. 🎬 youtube.com/watch?v=TERHoRzT… #31DaysOfAURA
2
107
Day 23 of 31 days of ✨AURA✨: Yes, it does Windows. AURA finds the Minecraft service, checks drives, processes, CPU + memory, and flags a privileged-access risk nobody asked about. Same agent. Same questions. Different OS. 🎬 youtube.com/watch?v=7nFvKJpp… #31DaysOfAURA
1
91
Day 22 of 31 days of ✨AURA✨: "Trust me" is not an incident report. Open the trace in Phoenix. AURA shows why the coordinator answered directly instead of handing off, plus latency, tokens, and cost. No vibes. A span tree. 🎬 youtube.com/watch?v=F8zkJvCI… #31DaysOfAURA
58