Xovris looks after everything you run – websites, apps, domains, email, code and security – tells you the moment something breaks and works out why, then fixes it with your permission and proves the fix with the same test that failed.
The check runs from your browser and nothing is saved to an account. To keep it free and fair, Xovris counts checks for 25 hours without keeping the readable address and holds a result for 60 seconds; your browser remembers the last address you checked. What the check keeps, and fair use: Privacy · Terms
You sign in and approve. Xovris writes the configuration, proves the first event arrived and moves each rung only on stored evidence. The command line is there if you prefer it.
Setup says done only when it has seen the evidence
Each connection shows where it stands – connected, data arriving, alerts reaching you, fixes allowed – and moves only when Xovris has really received each one.
1
Connected
Your credentials were checked with the provider and the answer was read back.
2
Telemetry received
The first record – a check result or an event – is stored, not just accepted at the door.
3
Monitoring verified
A real event from your deployed app, or a full round of checks, is stored. A test event alone never counts.
4
Repair authorisedOptional
When you choose it: a write grant you read scope by scope, covering each zone or project you want Xovris to fix.
Pull request
Vercel
Coding agent
Command
Xovris opens the pull request Beta
From the first release, you install the Xovris GitHub App on one repository. Once you agree to the exact words below, Xovris makes the setup change on a new branch and opens a pull request that lists every change – you review it and merge it.
What you agree to, word for word
Xovris may read the files it needs from the repository you choose – package manifests and the files that start your app – and open one pull request on a new branch. Nothing is pushed to its default branch. No file is sent to an AI model.
Changed your mind? Close the pull request and its branch is deleted.
With the first release, Xovris opens this pull request through its GitHub App.
Alerts you have seen arrive before anything breaks
Alerts reach your own email from the first minute – one press on Alerts adds your verified address, nothing to set up. When you add Slack, a test alert shows Slack's own acceptance – and if a channel fails, Xovris says which and sends the alert by email instead.
npx xovris inita recorded run
┌Xovris – connect your app
◆Found Next.js, using npm.
◇Sign in
│Your browser opened to approve this sign-in.
│Check the browser shows the same code: FVVG-XSWG
◒Waiting for you to approve in the browser
✔Signed in to acme
◒Creating an ingestion key for this app
✔Created an ingestion-only key
◇4 changes in ~/acme-web
│install @xovris/next with npm – The Xovris layer over OpenTelemetry for this stack.
│create instrumentation.ts – Starts Xovris on the server and reports request errors (Next.js instrumentation hook).
│ + // Added by npx xovris init - remove with npx xovris remove
│ + export async function register() {
│ + if (process.env.NEXT_RUNTIME === 'nodejs') await import('@xovris/next/register');
│ + }
│ +
│ + export { onRequestError } from '@xovris/next';
│ + // Added by npx xovris init - remove with npx xovris remove
│ + import '@xovris/next/client';
│ +
│set XOVRIS_INGEST_URL, XOVRIS_INGEST_KEY, NEXT_PUBLIC_XOVRIS_INGEST_URL, NEXT_PUBLIC_XOVRIS_INGEST_KEY in .env.local – The ingest address and an ingestion-only key. The key can only send events.
✔Wrote 4 changes; each is listed in .xovris/manifest.json
◒Sending a labelled test event from this machine
✔Telemetry received – stored 2026-10-01T19:20:09.213Z
◇Next
│Deploy this change. Monitoring is verified when the first real event from your deployed app is stored.
│Follow it live: https://acme.xovris.ai/
└Xovris is installed. Remove it any time with npx xovris remove.
What every fix gives you
What broke, what changed and the same test that failed, passing again – in a plain report you keep. Until that test passes, the issue stays open and you pay nothing for it.
You pay nothing for a fix until the test that failed passes. Until then the issue stays open and Xovris keeps working on it.
Recorded from the product itself on a test domain, example.com. No customer was involved.
Three things to know before you start
What will Xovris change on my systems?
Whatever you allow it to fix. Watching needs no access at all; each connection you grant extends what Xovris can fix, and every fix runs inside what you granted, as the exact change you approved, with its undo written down first.
Watching is free – 50 monitors, for good. Builder adds fixing: Xovris fixes and proves issues for US$39 a month, and an issue counts only once it is fixed and proven.
Join early access and Xovris starts on everything you run the day accounts open – it keeps checking, alerts you on the channel you choose and shows every fix as it is proven.