Xovris is in early access. Every capability on this site is described as it ships at launch. Join early access
Free website check – no sign-up, nothing to install
Xovris is an AI that watches your website, app and domain the way a whole IT team would: it tells you the moment something breaks, works out why, fixes it where you allow it and proves the fix with the same test that failed.
Your browser asks public DNS and the domain’s registry now; the certificate and page checks from Xovris’s probe switch on at launch. Nothing is saved to an account. Once the probe runs, it keeps a keyed hash of your IP address – never the address itself – for 24 hours to count the different websites you check, and the result for 60 seconds. Your browser remembers the last address you checked. What the check keeps, and fair use: Privacy · Terms
2028-10-01Cloudflare, Incben.ns.cloudflare.combristol.ns.cloudflare.comMicrosoft 365SPF -allDMARC p=quarantinecomodoca.comdigicert.comletsencrypt.orgpki.googssl.comXovris has no customers to show yet, so this is what it has done on its own estate and in its own test lab. Every figure names the run that produced it.
Today that means OpenTelemetry for services in any language and signed webhooks for any tool that accepts them. Next, Xovris connects any other service through its own API, CLI or MCP server, asking your consent at each step and naming the mechanism it used. Every integration, its state and its permissions
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.
Every connection climbs the same four rungs. A rung moves only when Xovris has read the evidence back from its own storage – an acknowledgement is never enough.
Your credentials were checked with the provider and the answer was read back.
The first record – a check result or an event – is stored, not just accepted at the door.
A real event from your deployed app, or a full round of checks, is stored. A test event alone never counts.
Only if you choose it: a write grant you can read scope by scope, limited to the one zone or project it needs.
From the first release, you install the Xovris GitHub App on one repository. Once you agree to the exact words below, Xovris reads only the files its codemods need, commits the change to a new branch and opens one pull request whose description lists every change. Merging moves no rung – your first stored event does.
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? Closing the pull request deletes its branch, and Xovris reads the deletion back.
With the first release, Xovris opens this pull request through its GitHub App.
Email alerts are on from the start. 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 runEvery issue gets a tracker like a parcel delivery, moved only by stored events. A fix is called fixed only when a separate check – the same test that failed – passes again.
Nothing until you allow it. Watching needs no access at all. A fix runs only inside the one zone or project you granted, as one exact change you approved, with its undo written down first.
Every permission, scope by scopeWatching is free – 50 monitors, with no AI and no hidden model calls. Builder adds fixing: Xovris fixes and proves issues for US$39 a month, and an issue counts only once it is fixed and proven.
Pricing, in fullEvery change the wizard makes is recorded. One command reverses all of it and revokes the key, then reads the revocation back.
How removal worksCreate a free workspace and Xovris keeps checking, alerts you on the channel you choose and shows every fix as it is proven.