Apps · Beta
Hear about every error in your app before your customers do
One command connects your app. Xovris groups each error into one issue, ties it to the release that shipped it and keeps the stack trace readable.
The wizard finding the app and signing in, from a real run.
- ◆ Found Next.js, using npm.
- ◆ Sign in
- ✔ Signed in to acme
- ✔ Created an ingestion-only key
- ◆ 4 changes in ~/acme-web
- ✔ Wrote 4 changes; each is listed in .xovris/manifest.json
- ✔ Telemetry received – stored 2026-10-01T19:20:09.213Z
- ◆ Next
Recorded wizard run, 1 October 2026, commit fdc8aa0
The setup change arrives as a pull request you review.
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.
The rungs this connection reached, each from stored evidence.
- Connected
- Telemetry received
- Monitoring verified
- Repair authorised
What Xovris watches
- Server and browser errors, grouped into issues
- The release that shipped each error
- Readable stack traces
- Traces through OpenTelemetry
What Xovris may change
- The setup change, as one pull request you review – never your default branch
What it fixes with your permission
- Your source code reaching an AI model without your recorded consent
How you start
Let Xovris open the pull request, ask your coding agent, or run one command in your project.
- Next.jsBeta
- React on ViteBeta
- Node.js (Express, Fastify)Beta
- Python (Django, FastAPI)Planned
The proof, step by step
The claim, what was recorded, how you can test it and what the result says – each from a record you can follow.
Claim
Hear about every error in your app before your customers do
One command connects your app. Xovris groups each error into one issue, ties it to the release that shipped it and keeps the stack trace readable.
Evidence
Recorded from a real setup run
The recorded run reached each step in the window above, 8 lines of it shown there.
Test
Test it on your own site
Connect your own project with the setup paths on the home page; the first result is your own record.
Your browser and Xovris’s probe, when you run it
Verdict
What the evidence says
The run recorded on 1 October 2026 reached every step shown, from the first command to the verified connection.
Recorded wizard run, 1 October 2026, commit fdc8aa0
What is new here
Built and tested in the product, each tied to the change that built it. Preview means it runs in the product and opens to everyone at launch.
Every log, check and change in one place, in order, with secrets masked
Built, not yet releasedLogs from your apps, the result of every check and every change Xovris makes land in one searchable place, kept in the order they really happened across machines, with passwords and keys masked before anything is stored – and every kind of line counted, so a new one stands out.
Connect by address alone, by app install or from your coding agent
Built, not yet releasedStart with nothing but your website address, install the app on your platform, or let your coding agent set Xovris up – each connection is read back before it counts, and a connection that stops answering says so instead of staying green.
A failing request is compared with the ones that worked
Built, not yet releasedWhen requests start failing, Xovris sets them beside the ones that succeeded and names the release and the repository the difference points to, so you start from the change that matters.
Uptime, APIs, journeys and scheduled jobs watched from outside
Built, not yet releasedPages, APIs, sign-in journeys and cron jobs are checked from Xovris’s probes on a schedule; a job that stops checking in is noticed by the silence, and every result is kept with where and when it was measured.
Every incident is investigated before you are asked anything
Built, not yet releasedWhen something breaks, Xovris works out what happened from your own records and the providers you depend on, and shows you the cause in plain words, with the records that prove it.
Alerts that say what happened, why, and what is already being done
Built, not yet releasedEvery alert carries the exact error, what it means, the cause once found and what Xovris is doing about it; a test alert shows each provider’s own acceptance, built-in email is one press, and a failed channel falls back to email and says so.
API tokens that always expire, with their life shown
Built, not yet releasedNamed tokens, read-only or read and write, lasting 1 to 365 days with their remaining life as a meter; a token that never expires is not issued.
Every incident has a live tracker, like a parcel delivery
Built, not yet releasedDetected, cause found, fix ready, approved, applied, verified – each step appears when its record exists, with its time, so you always know where a problem stands.
Tested before, tested after, checked by a separate verifier
Built, not yet releasedYour own failing outcome is reproduced before anything changes, re-run after the fix with the checks around it, confirmed by a verifier separate from the fixer, and re-checked again later; a fix that does not pass is put back and the next approach starts, and you pay nothing for it until the after-test passes.
A Fix Report in plain words for every fix
Built, not yet releasedWhat was wrong, how it was found, what changed and the before and after side by side – plain words first, the technical line under each, built only from the incident’s own records.
About 1,470 services from open catalogues, each licence checked
Built, not yet releasedThe services Xovris connects to come from permissive open catalogues, each install-tested and carrying its licence read from its source; the build refuses one whose licence does not allow it.
Recipes, each a verified run
Xovris with the tools you already use. A recipe is published only with the date and commit of the run that verified it, and a stale one is taken down until it is re-run.
Connect a Next.js app with one command
The wizard finds Next.js, signs you in through your browser, writes the configuration and waits until the first event is stored.
Verified 1 October 2026 · commit fdc8aa0
See the run
Questions
- Does Xovris need access to my accounts to watch?
- No. Watching needs nothing beyond what anyone on the internet can see. When you want Xovris to fix things, you grant access scope by scope, for as many zones and projects as you choose.
- Is Xovris's AI used on the free plan?
- No. The free plan makes no calls to any AI model. Builder adds fixing: Xovris fixes and proves issues, and an issue counts only once it is fixed and proven.
- Can I undo a fix?
- Yes. Every fix has its undo written down before it runs, and a fix that fails its after-test is undone automatically.