Apps

Hear about every error in your app before your customers do

Every error, one readable issue.

Start freeSee the plans

api.xovris.aiXovris’s own app, live
API
Answering
Database
Working, 18 ms

npx xovris init

TerminalNext.js
npx xovris init
Xovris – connect your appWhat Xovris foundApp: Next.js - A real install with npm from the public registry passed on 2026-11-15, but not yet on the newest next release (16.3.8).Supported: next 16.0.0 is in the supported range (from 15.3, below 17).Supported: Node.js 22.22.0 on this machine is in the supported range (20.19 or newer).Found: npm (from package-lock.json)Xovris will: Install Xovris into this Next.js app with npm, write its settings and send a test event. Next.js is supported here and every version check passed.Also possible: Watch the app from the outside by its web address. Works for any app on any stack, with nothing installed.Found Next.js, using npm.Waiting for you to approve in the browserSign inYour browser opened to approve this sign-in.Check the browser shows the same code: VJHR-KTCSYour data is never used to train our AI.Signed in to acmeCreating an ingestion key for this appCreated an ingestion-only key5 changes in ~/acme-webinstall @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';  + create instrumentation-client.ts – Reports browser errors and unhandled rejections (Next.js 15.3+ client instrumentation).  + // Added by npx xovris init - remove with npx xovris remove  + import '@xovris/next/client';

XovrisOn its own

  1. 30 lines run, 9 changes shown before any was written
Recorded from npx xovris init on the Next.js test project in the install suite, 15 November 2026, exit code 0

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.

Apps, installed by Xovris

Out of 686 listed for this area; 2,021 ready to connect in all

Search the Apps ones
Xovris at workReplaying work Xovris has done

Noticed by Xovris

POST /total started failing – TypeError: Cannot read properties of undefined (reading 'valueOf')

  1. Traced it to lib/total.js, line 5
  2. Found the change that caused it: “Read the quantity straight from the order line (#212)”
  3. Ran the failing request on that change and on the one before, to be sure
  4. Took back what that change did in lib/total.js
  5. Opened a pull request with the fix

POST /total answers again

· 43 s start to finish

lib/total.js
4- const qty = item.qty;
4+ const qty = item.quantity;

Asked

“A 3D solar system I can orbit and zoom with the mouse, with each planet labelled and a slider for how fast time runs”

  1. Wrote it – 4 files, 66 KB
  2. Drew it in 3D, right in the browser
  3. Running, exactly as it came out

Live – use it, or keep building it

Asked

“A booking page for my hair salon with prices, opening hours and a contact form”

  1. Built in 27.6 s
  2. Then asked“Make it feel more luxurious - a deep charcoal background with warm gold accents - and add a gallery of my work”
  3. Changed in 17 s – the same page, carried on
  4. Then asked“Let people choose a stylist and a time slot when they book”
  5. Changed in 40.6 s – the same page, carried on

One page, carried on from each message to the next

  1. The page as it stood at 00:31:03 UTCAt 00:31:03 UTC
  2. The page as it stood at 00:31:20 UTCAt 00:31:20 UTC
  3. The page as it stood at 00:32:01 UTCAt 00:32:01 UTC
Keep building it

Asked

“A drum machine with a 16-step grid, kick, snare, hi-hat and clap sounds, tempo control, and play and stop”

  1. Wrote it – 5 files, 43 KB
  2. Running, exactly as it came out

Live – use it, or keep building it

Noticed by Xovris

greenhouse-controller stopped working

  1. Read 11 records from 2 sources
  2. Found the cause: greenhouse-controller's firmware channel changed from stable to nightly at 01:48 UTC, 12 minutes before greenhouse-controller first failed
  3. Put greenhouse-controller back to stable, its last good setting

greenhouse-controller is back on its last good setting

greenhouse-controller · firmware channel

stable

Asked

“A music player page for a band's new EP with track list, play and pause, a progress bar and tour dates”

  1. Wrote it – 16 files, 3,450 KB
  2. Running, exactly as it came out

Live – use it, or keep building it

Asked

“Start the network map from our NetBox”

  1. Read NetBox 4.7.3: 2 devices with their sites and cables
  2. Matched 1 of them to a device Xovris reads itself
  3. Marked 2 that differ from what is really there

The map stands, and what differs is marked on it

Asked

“A 3D spinning product viewer for a pair of trainers that I can rotate with the mouse, with colour options”

  1. Wrote it – 8 files, 7,729 KB
  2. Drew it in 3D, right in the browser
  3. Running, exactly as it came out

Live – use it, or keep building it

Noticed by Xovris

A switch’s link to its router went down

  1. Read the switch and its router – 17 reads in 73 s
  2. Found it: port 1 was shut by the switch’s own loop protection, a second cable closing a loop
  3. Said which cable to pull, then turned the port back on the moment the loop was gone

The link is back up and the router answers again

Port 1 – the link to the router

ShutBack on

Asked

“Look over this firewall’s set-up”

  1. Read its whole set-up through its own sign-in, changing nothing
  2. Found 3 things to tighten
  3. Tightened 1 thing and read each change back

Safer than it was, each change read back

Noticed by Xovris

Is xovris.ai answering for everyone?

  1. Asked it from every place Xovris checks from, at once
  2. 95 ms from South Africa up to 365 ms from United States

Answering everywhere

Read while this page was built

Noticed by Xovris

api.xovris.ai outgrew the database server it shared

  1. Found the cause: connections held open on a shared database server
  2. Moved the database onto a dedicated core of its own

Put right on 23 October – answering in 10–74 ms since

Noticed by Xovris

Something new joined the network at 192.168.1.30

  1. Looked over the whole network – 7 devices answered
  2. Named it HP LaserJet Pro M404: it answers a print service (ports 80, 631, 9100)

HP LaserJet Pro M404 is on the map with everything else

  • Router
  • Dell
  • 192.168.1.21
  • Synology DiskStation
  • Philips hue - bridge
  • Network Camera
  • HP LaserJet Pro M404

Asked

“A synth keyboard I can play with the mouse or my computer keys, with a choice of waveform, volume and a little echo”

  1. Wrote it – 4 files, 55 KB
  2. Running, exactly as it came out

Live – use it, or keep building it

Asked

“npx xovris init”

  1. Found Next.js, using npm.
  2. Signed in to acme
  3. Created an ingestion-only key
  4. Wrote 5 changes; each is listed in .xovris/manifest.json
  5. Xovris received the test event
  6. Telemetry received – your first event is in Xovris

Xovris is installed. Remove it any time with npx xovris remove.

$ npx xovris init
✓ install @xovris/next with npm
✓ create instrumentation.ts
✓ create instrumentation-client.ts
✓ create app/xovris/route.ts
✓ set XOVRIS_INGEST_URL, XOVRIS_INGEST_KEY, NEXT_PUBLIC_XOVRIS_INGEST_URL, NEXT_PUBLIC_XOVRIS_INGEST_KEY, NEXT_PUBLIC_XOVRIS_TUNNEL in .env.local

Asked

“A 3D viewer for a wristwatch I can rotate and zoom, with strap colour options and a close-up of the dial”

  1. Wrote it – 5 files, 76 KB
  2. Drew it in 3D, right in the browser
  3. Running, exactly as it came out

Live – use it, or keep building it

What Xovris read on its own domain.

The wizard finding the app and signing in.

Connect15 November 2026
  1. What Xovris found
  2. Found Next.js, using npm.
  3. Sign in
  4. Signed in to acme
  5. Created an ingestion-only key
  6. 5 changes in ~/acme-web
  7. Wrote 5 changes; each is listed in .xovris/manifest.json
  8. Xovris received the test event
  9. Telemetry received – your first event is in Xovris

XovrisOn its own

  1. Connected
  2. Telemetry received
  3. Monitoring verified
  4. Repair authorised
The setup wizard on a Next.js app

From the deploy to the pull request, on its own

43 s from the failure to the pull request, nobody asked

  1. The change landsRead the quantity straight from the order line (#212)
  2. POST /total answers 500TypeError: Cannot read properties of undefined (reading 'valueOf')
  3. Traced to lib/total.js line 5sum += item.price * qty.valueOf();
  4. Proved on a copy: 500 before, 200 afterBoth sides run – never a guess from blame
  5. Pull request #1 openedXovris: fix TypeError at lib/total.js line 5
  6. Your step: mergeNothing is merged until you merge it. CI runs again on the branch.

What it watches, may change, and what stays yours.

Xovris raises the pull request for you once GitHub is connected – every change listed, for you to review and merge. Rather do it yourself? One command in your project does the same, from your editor or your terminal.

What Xovris watches

  • Server and browser errors, grouped into issues
  • The release that shipped each error
  • Readable stack traces
  • Traces through OpenTelemetry
  • A release that makes your app crash, caught from its crash rate and its store reviews

What Xovris puts right

  • The setup change, as one pull request you review – never your default branch

What waits for your permission

  • Your source code read by Xovris without your consent

Try it now, on your own.

Each of these runs in your own browser in seconds. Here is what each says for xovris.ai, checked 18 November 2026, 23:05:28 UTC – open one to run it on yours.

  • API health check

    Address Browsers can find it.

    Certificate Valid until 31 December 2026 – 42 days left.

    Registration Registered until 1 October 2028.

  • Repository health check

    Asks GitHub or GitLab for the repository’s own public record and OpenSSF for its Scorecard. You give it an address, never a token.

  • Dependency vulnerability check

    Checks every package in a package.json, package-lock.json, requirements.txt or go.mod against OSV in one go.

  • JWT decoder and checker

    Decodes a token’s header and claims in your browser and flags “none”, missing or past expiry and long lives.

What shipped for Apps, strongest first.

Each one looks after this area today, with the day it shipped and the plan it starts on.

Every feature

Lit: live and workingOpen: Xovris is still working on it

  • Every change is made safely, under your policy

    Before any change Xovris shows exactly what it would send, the one reading that would move and the way back, rehearsed on a copy first; the real change follows once the rehearsal passes, under your policy.

    Shipped 9 October 2026From PersonalAsk

  • Your repository’s own scripts run sealed off, and Xovris finishes the work around a change – from a chat message to the follow-ups after the merge

    Every linter config, build file, setup script and test command from your repository runs in its own sealed copy that holds no secret of yours or Xovris’s, reaches no network and starts nothing else, so a config that tries to read keys or phone home finds nothing.

    Shipped 7 October 2026From PersonalAsk

  • Every fix says Verified, Not verified or Reverted – on the page, in the email and on your status page

    No change is ever shown as done before it is proven.

    Shipped 7 October 2026From PersonalAsk

  • See what code review found and what your team did with it, week by week

    Every review Xovris makes of a pull request is kept with its findings, and each finding settles by what really happened: fixed by Xovris with a proven fix, taken up by your team on a later commit, dismissed, or never merged.

    Shipped 6 October 2026From PersonalAsk

  • Code review you can act on: accept a finding and Xovris fixes it

    Accept any review finding and Xovris shows the exact patch first, then fixes it in a safe copy.

    Shipped 6 October 2026From PersonalAsk

  • Every change Xovris makes does what you asked and can be undone in one press

    Before Xovris changes anything in one of your systems it reads the record first, rehearses the change on a copy of your system, and changes only the fields you named – a request that matches no record, or more than one, is stopped and explained rather than guessed.

    Shipped 6 October 2026From PersonalAsk

  • Repository fixes, your badge and your free check go onto your pages as one pull request – Xovris writes them

    When a fix is a change to your repository – the CA bundle in a minimal image, a liveness probe that waits on a database, container limits, a connection pool that drops idle connections, the JVM heap, ASP.NET Core's stdout log, rotating container logs or the dashboard panel on your page - pressing the step now does it.

    Shipped 6 October 2026From PersonalAsk

  • Review code on a Git server inside your own network, with nothing opened to the internet

    You can now run the Xovris connector inside your network and Xovris reviews and fixes code on GitHub Enterprise Server, self-managed GitLab or Bitbucket Data Center without a single inbound port: the connector only ever calls out, keeps your Git server’s token inside your network, and refuses anything but that server’s review requests.

    Shipped 6 October 2026From PersonalAsk

Recipes Xovris runs and verifies.

Xovris with the tools you already use – each recipe set up in minutes, working end to end.

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.

What does the free plan include?

Watching and alerts, free for good. Personal adds fixing: Xovris puts problems right, and an issue counts only once it works again.

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.

Is my data used to train AI?

No. Your data is never used to train our AI. Your systems, files, logs and settings stay yours: they are never used to train any AI, ours or anyone else’s, and nothing of yours ever reaches another customer.

Words on this page, in plain English

Each technical word this page uses, said simply.

Program-to-program connection (API, APIs)
A way for one program to ask another for information or to do something, without a person clicking through a website.
Plain-text data (JSON)
A common way of writing data as named values, readable by people and programs alike.
Data an app reports about itself (telemetry)
The errors, timings and records an app sends out so problems can be spotted and explained.
The open standard for app data (OpenTelemetry)
A free, widely used standard for collecting an app’s errors, timings and records and sending them to any monitoring service.

Ask Xovris

Open the full page