Skip to content

PRICING

Priced per application, because that is what the work follows.

Every package includes the same analysis. What changes is how far we go with it — from telling you what matters, to putting a reviewed response in front of you.

Plans

Watch

$49per month, per application

We run the workspace, watch the incidents, and tell you which ones matter. You act on them.

Start a conversation
  • One application, all of its environments
  • Incident sync, analysis, and risk scoring
  • Alerts routed to the channels you choose
  • A reviewed summary for anything critical
  • Monthly review of what repeated
  • We do not prepare code changes on this package

Respond

Most chosen

$99per month, per application

Everything in Watch, plus a prepared response — reviewed by a person before it ever reaches you.

Start a conversation
  • Everything in Watch
  • A proposed fix as a pull request, ready for your review
  • Approval-gated file changes where there is no repository
  • A named channel with a four-hour response target
  • Quarterly review of root causes, not just incidents

Embedded

Customannual agreement

For teams that need commitments in writing, or an estate too large to price by the application.

Talk to us
  • Everything in Respond, across an unlimited estate
  • Written service-level agreement
  • Signed data-processing agreement
  • Regional hosting, or deployment inside your own network
  • A named engineer who knows your systems

SIDE BY SIDE

The analysis is the same. The involvement is not.

FeatureWatchRespondEmbedded
Incident sync and analysis
Rule-based risk scoring
Alerts to your channels
Applications coveredOneOneUnlimited
Reviewed by a personCritical onlyEvery alert sentEvery alert sent
Prepared pull requests
Approval-gated file changes
Response targetNext business day4 hoursBy agreement
Root-cause reviewMonthlyQuarterly, in depthQuarterly, in depth
Written SLA
Signed DPA
Runs inside your network

BEFORE YOU ASK

The questions that decide this.

Why is it priced per application?

Because that is what drives the work. A second environment of the same application costs us almost nothing to watch; a second application is a different codebase, a different failure vocabulary, and a different on-call.

Do you need access to our code?

Not to start. Analysis works from the error payload alone. A repository connection is only needed if you want a prepared pull request, and it is scoped to the repositories you choose.

Can you change things in production?

Only what you approve, and only where you connected a path for it. Every applied change records who approved it and keeps the backup taken beforehand.

What if the data cannot leave our network?

Then run the same workspace yourself. There is no licence cost — you provide the infrastructure and the model provider, and we are not in the path.

BEFORE YOU COMMIT

Start with the applications that keep you up at night.

One application is enough to see whether this changes anything. Add the rest when it has.

  • No agent to install and no change to your application
  • Every production change waits for your approval
  • Start with one application and add the rest when it has proved itself
Talk to us See how the service works

A scoping call, not a sales sequence.