Hello from Morse: what the product posts will cover
We're opening Morse to teams the week of November 3. Here is the question the product is built around, what a performance brief is for, and what you'll read in this lane.
Start with Product →The Morse Blog
Engineering notes, product updates and field notes on AI-agent observability and evals, from the team building Morse.
We're opening Morse to teams the week of November 3. Here is the question the product is built around, what a performance brief is for, and what you'll read in this lane.
Start with Product →Agents moved from demos to production faster than the tools for watching them. What the industry posts will cover, and the few positions we start from.
Start with Industry →How we build an observability product for agents, the few rules we hold ourselves to, and what you'll read in the engineering posts.
Start with Engineering →Why Morse opens on a ranked performance brief instead of a wall of traces, and how every claim in the brief links back to the spans, logs and infra evidence you can open when you need it.
Read post →Using a model to grade your agent's output is useful and cheap to start. Here is how to keep it honest: sample, calibrate against people, keep it apart from hard outcomes, and watch what it costs.
Read post →How Morse accepts an OpenTelemetry export fast, stages the encrypted raw bytes on a Redis Stream, and persists them in a worker. Covers the failure modes and what we chose not to build yet.
Read post →A single blended number for agent cost and quality feels tidy, but it hides the tradeoffs you need to see. Here is how to read them next to each other instead.
Read post →Why every span Morse stores carries a type, how OTLP and our REST path normalize into one model, and what the typing buys you once the data lands.
Read post →A performance brief is a ranked answer to one question: which of your production agents deserves attention first? Here is what goes into it, what stays out, and how teams use it week to week.
Read post →