What is
Mezmo
?
Most platform initiatives fail the same way: they start too big, get funded like projects instead of products, build for too long without testing with users, and confuse renaming an infrastructure team with building a platform team. Instead, start small, learn fast and scale deliberately.
At a glance
Attribute | Value |
|---|---|
Primary use case | AI-agent orchestration for production incident investigation and approved remediation |
Deployment type | Self-hosted AURA agent with CLI and web server; remote Mezmo MCP service |
Pricing model | Open source (AURA); commercial pricing not specified |
API compatibility | Model Context Protocol (MCP), HTTP streamable transport, OpenAI function calling, PromQL, server-sent events (SSE) |
Supported integrations | Kubernetes, Prometheus, PagerDuty, OpenAI, Claude, AWS Systems Manager Parameter Store, GitHub |
Source type | Open |
Cloud provider | Cloud Agnostic |
Required skills | SRE incident response, Kubernetes operations, Prometheus and PromQL, MCP server configuration, API credential management, TOML configuration |
AEP branch | Agent Infrastructure |
AEP category | Harness |
AEP subcategory | Execution |
AEP detail | Orchestration |
Profile
Orchestration is Mezmo’s role in the AEP taxonomy: its open-source AURA agent coordinates agents and operational tools for production SRE work.
AURA runs in the user’s environment with its tools, telemetry, and operational context. The showcased configuration combines specialist workers, MCP tool servers, and a workflow gateway; Mezmo’s remote MCP service provides log analysis, trace topology, root-cause analysis, and log histograms.
Focus
AURA is designed for SRE teams investigating production incidents and carrying out approved operational changes. In the showcased Kubernetes workflow, a cluster inspector checks live cluster state, a metrics analyst runs PromQL queries, and a remediator applies Kubernetes fixes after approval.
Background
Company-background research identifies Mezmo as formerly LogDNA and reports that it was founded in 2015 through Y Combinator. The supplied research does not specify funding amounts or terms.
Mezmo describes AURA as an open-source agentic harness. The company has also described its log agent, which reads files and uploads log lines to an account, as open source.
Features
Agent orchestration
AURA coordinates specialist agents for production SRE tasks. Its configuration defines workers, models, and a workflow gateway, and the website describes orchestration mode with three workers and four MCP servers.
Kubernetes cluster investigation
The cluster inspector helps examine operational symptoms using live cluster information. It can inspect pods, events, logs, and resources through a Kubernetes MCP server.
Prometheus metrics analysis
The metrics analyst helps confirm incident symptoms with metrics. It runs PromQL queries against Prometheus, including instant and range queries, and can inspect targets and metadata.
Approved Kubernetes remediation
AURA supports controlled changes to Kubernetes resources. The showcased configuration gates the resource update tool behind human-in-the-loop approval through a workflow MCP server.
Mezmo MCP observability analysis
The remote Mezmo MCP service gives agents access to observability analysis for incident investigation. Its listed capabilities include log search, trace topology, root-cause analysis, and log histograms, accessed using HTTP streamable transport.
CLI and web server
AURA can be run through a command-line interface or web server, providing local ways to operate the agent. The showcased CLI reports its local server endpoint as http://localhost:8080, and the configuration shows a local web-server command.
Pros and cons
Pros
AURA runs in the user’s environment with the team’s tools, telemetry, and operational context.
Specialist workers separate Kubernetes inspection, Prometheus metrics analysis, and remediation tasks.
The showcased workflow gates state-modifying Kubernetes operations behind human approval and includes an audit trail and PagerDuty paging.
The Mezmo MCP service exposes log and trace investigation capabilities, including root-cause analysis and log histograms.
Cons
The showcased Kubernetes incident-response configuration requires several separately configured components and credentials, including OpenAI, Mezmo, and PagerDuty credentials, plus Kubernetes, Prometheus, Mezmo, and workflow MCP servers.
Commercial pricing is not specified in the supplied research, so the cost of commercial Mezmo capabilities cannot be determined from these sources.
FAQs
Mezmo FAQs
What does Mezmo do during a Kubernetes incident?
Mezmo's showcased workflow assigns live cluster inspection to a cluster inspector, PromQL analysis to a metrics analyst, and remediation to a remediator; Kubernetes changes are gated by human approval.
Which tools does Mezmo integrate with?
Mezmo's listed supported integrations are Kubernetes, Prometheus, PagerDuty, OpenAI, Claude, AWS Systems Manager Parameter Store, and GitHub.
What does Mezmo cost?
Mezmo's pricing model is Open source (AURA); commercial pricing not specified.
What skills are required to operate Mezmo?
The listed required skills for Mezmo are SRE incident response, Kubernetes operations, Prometheus and PromQL, MCP server configuration, API credential management, and TOML configuration.
What are the limitations of Mezmo's showcased incident-response setup?
Mezmo's showcased Kubernetes incident-response setup requires several separately configured components and credentials, including OpenAI, Mezmo, and PagerDuty credentials, plus Kubernetes, Prometheus, Mezmo, and workflow MCP servers.
