Jengo
Get a demoFR
Resolue Production incidents

Production broke.The fix is waiting for your review.

Resolue goes from an alert to its root cause, writes the fix, verifies it on a preview and opens a pull request with the evidence. Merging stays your move.

Get a demo See the sequence
Incident in progressResolue
Error detectedFour signals correlated to one incident
00:00
Root cause foundOne line, in a commit from this morning
00:08
Fix verified on previewTests replayed, video and screenshots attached
01:45
Pull request readyDiagnosis, diff, evidence, confidence score
To merge
Nobody has been woken up yet. Nobody has merged yet.
Wired into your pipelineSentryGitHubVercelDatadogPlaywright
The sequence

From alert to evidence,without waking anyone.

An alert rarely costs you the fix: it costs you the diagnosis. Resolue covers that ground, and stops before the merge.

Step 01

The signals converge

Several tools, several alerts: Resolue correlates them into one incident, with the number of users affected.

Step 02

The cause, not the symptom

Stack traces and recent commits are read together to name the file, the line and the change at fault.

Step 03

A minimal fix, on a branch

The smallest change that settles the problem, pushed to a branch; your platform builds the preview.

Step 04

Verified against running code

Tests run against the preview URL; the path is replayed, recorded, captured.

Step 05

You read, you merge

The pull request carries the cause, the diff, the tests, the video and a confidence score. Resolue does not merge.

What you get

Not every bug hasa fix to propose.

A tool that opens a pull request on every incident teaches you to stop looking. Resolue adapts what it delivers to what it understood.

High confidence: verified pull request

A clear cause: the fix is written, replayed on the preview and recorded. The pull request arrives ready to review.

Pull requestVideo and tests

Medium confidence: draft and caveats

The fix spans several files: the draft states what was verified and what is left to settle.

DraftPreview

Low confidence: diagnostic report

Outside visible code: no pull request, but the likely cause, the files involved and the related commits.

AnalysisContext
What it plugs into

Your tools stayyour tools.

Resolue replaces neither your monitoring, nor your forge, nor your deployment platform: it sits between them.

  • Sentry
  • Alerts
  • Datadog
  • Stack traces
  • OpenTelemetry
  • GitHub
  • Recent commits
  • Vercel
  • Previews
  • Playwright

CloudWatch, PagerDuty, Slack, GitHub Actions, Cloudflare Pages and Netlify are being connected.

Going further

The questionswe get asked.

01Can Resolue merge on its own?

No, and it is not a setting to switch on. Resolue opens a pull request and stops. Merging, deploying to production and rolling back stay human acts, subject to your repository's rules.

02What does Resolue see of our code?

What its access allows, repository by repository, and nothing beyond. Scope, data residency and log retention are settled with your team before the first connection, on the same rules as the rest of the platform.

Start with the everyday

Start with your next alert.The one nobody wants to take at three in the morning.

Get a demo

Thirty minutes to scope the process, the systems and the approvals. Or write to us at [email protected]