stacktrace

Seed round · 2026

Production monitoring for software teams

Know which deploy broke production.

Stacktrace checks every release against the one before it, names the change that slowed production down, and puts the rollback one click away.

Raising a $14m seed · illustrative

production · today
  • 14:02deployv2.40.3checkouthealthy
  • 15:18deployv2.40.4searchhealthy
  • 16:41deployv2.41.0checkout3.5× slower
  • 16:46causea91f3cpricingroll back?
Stacktrace · fictional company · dgitl studio demonstration01
stacktrace

The problem · illustrative

Problem

Most incidents start with a deploy. Most tools start with a dashboard.

3

tools open during a typical incident: metrics, traces and the deploy log

47m

median time to resolve at a 200-engineer team, before Stacktrace

1 in 3

rollbacks start with a guess about which release caused it

Stacktrace · fictional company · dgitl studio demonstration02
stacktrace

Why now

Why now

Teams ship ten times a day. On-call stayed the same size.

Every release is a chance to break something. The person holding the pager needs the cause, fast.

Deploys per engineer, per week · illustrative

  • 20191.2
  • 20201.6
  • 20212.3
  • 20223.1
  • 20234.2
  • 20245.4
  • 20257.1
Stacktrace · fictional company · dgitl studio demonstration03
stacktrace

Product

One screen: what changed, what it broke, and the way back.

checkout-api · productionDeploy check
200ms400ms600msv2.41.013:0014:0214:40
Slower after deploy

v2.41.0 made checkout 3.5× slower.

Response time
172ms → 618ms
Errors
0.2% → 2.9%

a91f3c now looks up prices one item at a time.

Roll backOpen trace
Stacktrace · fictional company · dgitl studio demonstration04
stacktrace

How it works

How it works

Ten minutes to set up. Five minutes to a verdict.

  1. 01

    Connect

    One OpenTelemetry exporter. No agents to install on every host.

  2. 02

    Compare

    Latency and errors in the five minutes either side of each release.

  3. 03

    Name

    The commit, the author and the slow step inside the request.

  4. 04

    Roll back

    One click from the page that woke you up.

Stacktrace · fictional company · dgitl studio demonstration05
stacktrace

Customer outcome · illustrative

“The page arrives with the deploy that caused it. Half our incidents now end with a rollback before anyone opens a dashboard.”
Staff SRE, Larkspur · fictional customer

Median time to resolve, minutes

Before Stacktrace47

Two quarters later11

Stacktrace · fictional company · dgitl studio demonstration06
stacktrace

Traction · illustrative

Traction

300 teams, most of them found us during an incident.

300
teams
140%
net retention

ARR by quarter, $m · $3.1m today

$0.4mQ1 25$0.7mQ2 25$1.1mQ3 25$1.6mQ4 25$2.3mQ1 26$3.1mQ2 26
Stacktrace · fictional company · dgitl studio demonstration07
stacktrace

Market · illustrative

Market

Every team that deploys is a buyer.

We start with software companies of 50 to 1,000 engineers, where on-call is shared and tooling is still a choice.

  • $15bn

    Total

    Observability spend worldwide

  • $2.8bn

    Serviceable

    Teams of 50 to 1,000 engineers

  • $400m

    First target

    Teams already on OpenTelemetry

Stacktrace · fictional company · dgitl studio demonstration08
stacktrace

Business model

Business model

Priced by data, so every engineer gets a seat.

Start

Free for 14 days

Your real traffic, every feature, one service to begin.

Team

$0.30 per GB

Unlimited users and dashboards. Most teams land at $2k a month.

Enterprise

Annual contract

SSO, EU or US regions, and a named on-call partner.

Illustrative unit economics: 81% gross margin, 11-month payback on sales-assisted accounts.

Stacktrace · fictional company · dgitl studio demonstration09
stacktrace

Landscape

Landscape

The only tool that starts from the change.

Suites show everything and leave the diagnosis to you. Stacktrace names the cause and is running before lunch.

Self-hosted stacks
APM suites
Log search
Error trackers
Stacktrace
← Shows the dataNames the cause →
Stacktrace · fictional company · dgitl studio demonstration10
stacktrace

Roadmap

Roadmap

From naming the bad deploy to stopping it.

  1. Now

    Deploy checks

    A verdict on every release, with the commit and the slow step named.

  2. 2027

    Rollback rules

    Teams set the limits. Stacktrace rolls back when a release breaks them.

  3. 2028

    Risk before merge

    Flag the pull requests most likely to slow production, before they ship.

Stacktrace · fictional company · dgitl studio demonstration11
stacktrace

The ask · illustrative

The ask

$14m seed.

Twenty-four months to reach $12m ARR, with deploy checks for every major language and rollback rules in production.

$14muse of funds
  • Engineering and data55%
  • Go-to-market25%
  • Infrastructure12%
  • Operations8%
Stacktrace · fictional company · dgitl studio demonstration12
← Case studiesStacktrace websiteWant a deck like this? Start a project
1 / 12