Everything Xovris does for what you run.

Find any feature by what you run.

NewProve a page reaches a person: run a drill on any escalation policy

Show every feature

Start free

Xovris at workReplaying work Xovris has done

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

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

New in Xovris, read from the release production runs.

This page is up to date with release da25ebb. A feature marked Next release arrives with the next update; everything else is in Xovris today.

  1. SecurityLive

    The AI review runs on every paid plan

    Every paid plan has the adaptive AI review of changes; on the free plan Xovris's own checks keep watch, and the plan says so.

  2. SecurityLive

    Your code's bill of materials in the command centre

    A connected repository's review shows its packages with their licences and advisories, and which of them are in a build that is live.

  3. SecurityLive

    See what people did beside what Xovris did

    Sign-ins, approvals, member, token, webhook, autonomy and settings changes join Xovris's own actions in one searchable record, under 'What people did'.

  4. RepairLive

    Undo a fix, or let Xovris put it back itself

    Every fix card has its change, its risk and one Approve; if the check after a change fails, Xovris restores the earlier version by itself.

  5. RepairLive

    Every step said before it runs

    Xovris says each step it will take and whether it is ready or waiting on your go, and never calls a step done before it has run and been checked.

  6. MonitoringLive

    The free check reads cookies and trackers

    The free website check names the cookies a page sets before anyone agrees and the trackers it loads, worst first among every other finding.

Every area, its strongest first.

One place for all of it. Told the way you work.

Everything you run, in one ring round Xovris – press any part to see what it does there.

Websites and services

Xovris reads the whole of what you run on the web – the site, its code and the services behind it – from several places, all the time. When something breaks it reads what is connected to it, follows the fault to its cause and puts that right on its own, with an undo.

xovris.ai, answered from every place it is checked

  • Website check

    The free website check shows what the outside world sees

    You can now type an address on xovris.ai and Xovris checks it from its own probes outside your network – the certificate, the page and DNS – beside what your browser can see, and says plainly what it could not confirm.

    Shipped 1 October 2026

    Read more

  • Browser quality runs

    Your website’s quality checked in a real browser, then every day

    Ask once and Xovris checks your site the way a visitor’s browser sees it – accessibility, whether tracking waits for consent, broken links, what search engines see and speed – keeps the report, alerts you once for each problem, and checks again every day.

    Shipped 2 October 2026

    Read more

  • Expiry alerts

    Free certificate and domain expiry alerts for anyone, with no account

    Give Xovris an email address and the sites you care about, confirm from the email, and Xovris checks each one every day: the certificate it serves and the domain’s registration, read from the registry itself.

    Shipped 4 October 2026

    Read more

  • App health

    Every app you add shows how it is doing

    Each app added to Xovris shows where it is called, what reached it and its last failure, with a signed test you can send from its card and a clear way to remove it.

    Shipped 2 October 2026

    Read more

Learn more

Incidents and alerts

Every alert becomes one incident with its evidence. Xovris works it in the open, fixes it on its own where your policy allows and calls a person only when one is needed.

Put right, and working again

  • Paging hand-off

    Every incident handed to PagerDuty, Jira Service Management, Opsgenie or incident.io – and kept in step

    Connect the tool your team already pages from and every incident Xovris raises is sent there, a person’s acknowledgement in Xovris and the verified resolve follow in order, each sent once and keyed to the incident, so the tool never shows a second copy.

    Shipped 4 October 2026

    Read more

  • Move from Opsgenie

    Move from Opsgenie in one step

    Give Xovris an Opsgenie API key (US or EU) or its export, on the business plans, and it brings across your people, teams, schedules with their overrides, escalations, routing rules, alert sources, heartbeats, maintenance windows and each person’s text and call steps – first as a plan you can read, then for real, every piece read back and undoable.

    Shipped 3 October 2026

    Read more

  • Alert channels

    Teams, Discord, PagerDuty and more set up in one step, the test seen arriving

    On Alerts every channel sets up from its own row: give it the address or key, press once, and Xovris adds it to the route every alert takes and sends a test.

    Shipped 3 October 2026

    Read more

  • Sentry inside Xovris

    Keep Sentry and see its issues inside Xovris

    Connect your Sentry organisation with a token and its unresolved issues appear on Issues beside Xovris’s own – events, users, project and a link straight back into Sentry.

    Shipped 2 October 2026

    Read more

Learn more

Devices and networks

Anything with a network, whatever it is – a laptop, a printer or a factory controller, for example. Xovris names each by make and model, notices a new one joining and checks it for known holes.

  • Every device page says what Xovris reads from it

    The devices page shows every kind of device as a tile lit by a real device of that kind, and each device's page says what Xovris reads from it.

    Shipped 31 October 2026

    Read more

  • The free tools, redesigned

    The free tools and the is-it-down pages read clearly on a phone and a desktop.

    Shipped 28 October 2026

    Read more

  • The what-is-my-IP tool holds still while it loads

    On a phone, the free what-is-my-IP tool no longer moves the page when its answer arrives.

    Shipped 27 October 2026

    Read more

  • The free tools on one board

    The free tools page is one board: a box that checks anything you own, 'Is a service down?', and every free check, grouped by what you run.

    Shipped 24 October 2026

    Read more

Learn more

Email and domains

Your domain read whole, all the time – its registration, DNS, mail protection and certificates, for example. Xovris warns you sixty days before it runs out, and when mail stops arriving it follows the fault to the record, setting or provider behind it and puts that right.

xovris.ai’s addresses, checked on the public block lists

  • Domain watch

    Domains, DNS and registration watched – and every change explained

    Xovris reads each domain’s registration from its registry – expiry, renewal, transfer lock and registrar – and its DNS, and tells you in plain words when anything changes or is about to lapse.

    Shipped 2 October 2026

    Read more

  • Renewal warnings

    Domain renewals warned about 60 days ahead, and only while auto-renew is really off

    Xovris reads whether a domain renews itself from the registrar itself, through your own connection, and warns you 60, 30, 14, 7 and 1 days before it lapses – earlier than the registry’s own reminders.

    Shipped 4 October 2026

    Read more

  • Dangling records

    Know when an old DNS record lets a stranger take over part of your domain

    Xovris now looks at every address record in your domain every five minutes for ones that still point at a service you no longer use – an old Azure app, an S3 bucket, a Heroku or GitHub Pages site, a domain nobody renewed, a cloud address you gave back.

    Shipped 2 October 2026

    Read more

  • Certificate watch

    Know when a certificate is issued for your domain

    Xovris watches the public Certificate Transparency logs and tells you when a certificate is issued for one of your domains – including one you did not ask for.

    Shipped 1 October 2026

    Read more

Learn more

Security, watched all the time

Everything that could let someone in – a sign-in from a new place, a hole in a device or in code, a leaked key or spoofed email, for example. Xovris watches for all of it all the time, follows each to its cause and acts on its own where your policy allows.

xovris.ai’s own security headers, graded

  • The AI review runs on every paid plan

    Every paid plan has the adaptive AI review of changes; on the free plan Xovris's own checks keep watch, and the plan says so.

    Shipped 1 November 2026

    Read more

  • Your code's bill of materials in the command centre

    A connected repository's review shows its packages with their licences and advisories, and which of them are in a build that is live.

    Shipped 1 November 2026

    Read more

  • See what people did beside what Xovris did

    Sign-ins, approvals, member, token, webhook, autonomy and settings changes join Xovris's own actions in one searchable record, under 'What people did'.

    Shipped 1 November 2026

    Read more

  • Know which vulnerable packages are actually served

    Xovris lists every package in your code with its licence and advisories, and says which vulnerable ones your live site actually serves.

    Shipped 31 October 2026

    Read more

Learn more

Cloud and connected tools

Wherever you already work – your host, your chat or your paging tool, for example. Xovris connects to it and reads what is there by itself, from Vercel and Cloudflare to Sentry, Slack and PagerDuty.

  • Vercel

    Connect Vercel: every environment gets its own key, checked

    Connecting Vercel writes a separate key into production, preview and development, reads each one back, and removes them all when you disconnect.

    Shipped 1 October 2026

    Read more

Learn more

Code and releases

One command connects your app. Xovris finds the framework, signs you in from the browser, watches every release from then on and follows each fault to the release and the change that caused it.

Set upnpx xovris init

Setting up a real app, in one line

  • One-command setup

    One command sets Xovris up on Nuxt, SvelteKit, React Router and Astro

    The set-up command now starts Xovris in both halves of a Nuxt, SvelteKit or React Router app – the browser and the server – at the places each framework names for it, and reports Astro’s server errors through middleware.

    Shipped 3 October 2026

    Read more

  • Connect any way

    Connect by address alone or by app install

    Start with nothing but your website address or install the app on your platform – each connection is checked before it counts, and a connection that stops answering says so instead of staying green.

    Shipped 2 October 2026

    Read more

  • App store watch

    A release that makes your app crash, caught from its crash rate and its store reviews – and every reviewer answered once it is fixed

    Connect your app on the App Store or Google Play (and Sentry if you use it).

    Shipped 2 October 2026

    Read more

Learn more

Your code, with Xovris inside

Xovris finds what broke in your code on its own, proves the fix on a copy and opens the pull request – you read the report and merge.

APIhttps://api.xovris.ai/v1/

The address your AI tool adds

  • Open pages Xovris built and use them

    The home page and the build page open two pages Xovris's own builder made, byte for byte, each beside the request that made it.

    Shipped 1 November 2026

    Read more

  • Limit a key to the sites you choose

    An API key can be limited to what it may do and which domains, sites and servers it may touch, and Xovris enforces both on every call.

    Shipped 1 November 2026

    Read more

  • Code review knows every deprecated Node API

    Code review flags calls Node has deprecated, from Node's own published list, kept current by itself.

    Shipped 19 October 2026

    Read more

  • API keys that never expire, made safe

    An API key can be set never to expire wherever leaked keys are scanned for; where they are not, Xovris says so and keeps an end date.

    Shipped 19 October 2026

    Read more

Learn more

People and access

Xovris holds only the access a fix needs and puts things right on its own, inside the limits you set in your own policy.

On its own: anything you hand itSpending money: you decide

Your policy, set by you

  • Cyber Essentials

    Your Cyber Essentials readiness, read from your real computers and accounts – with the two automatic fails raised the moment they appear

    Xovris reads what it already watches – your computers through the Xovris app, your people’s accounts in Google Workspace, Microsoft 365, Okta or GitHub, and the software updates still waiting – and shows each Cyber Essentials requirement as met, not met or not read yet, never assumed.

    Shipped 2 October 2026

    Read more

Learn more

Money and plans

Xovris watches your Stripe sales, failed payments and disputes. Its own prices are published in full, in your currency, with the tax beside each.

  • Stripe watch

    Your Stripe account watched: sales, failed payments and disputes, each with its alert

    Connect Stripe with a restricted key and Xovris reads its event log every five minutes – sales, failed payments with Stripe’s own reason, disputes, refunds, payouts, subscriptions, invoices it could not collect and payments held for review – and raises one alert for each dispute, failed payout and cluster of failed payments, beside the rest of your alerts.

    Shipped 2 October 2026

    Read more

Learn more

These are examples, never the edge: a thing with a network that is not here, Xovris identifies by make and model and looks after the same way.

Everything with a network. Looked after on its own.

Every device on your network, whatever its make: Xovris learns each one, keeps it up to date and fixes it when it breaks.

Learn more
SD-WAN edgeFirewall AFirewall BRemote accessServersCore switchStorageUPSAccess switchWi-FiAccess switchLaptopsPhonesPrintersCamerasBuilding systemsSD-WAN edgeFirewall AFirewall BRemote accessServersCore switchStorageUPSAccess switchWi-FiAccess switchLaptopsPhonesPrintersCamerasBuilding systems

And the everyday work of an IT team, done on its own

Start with what you have.

The fix on this page is a real one Xovris made on 19 October 2026, from detected to proved; the investigations in step 01 ran on 19 October 2026.

Start freeSee the plans

Words on this page, in plain English

Each technical word this page uses, said simply.

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.
A message sent to your own system (webhook, webhooks)
An automatic message one service sends to an address you choose the moment something happens.
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.
Domain Name System (DNS)
The internet’s address book: it turns a name you type into the number of the computer that answers for it.
Signed address-book answers (DNSSEC)
A signature on a domain’s address-book answers, so a computer can tell they were not forged on the way.
Allowed senders record (SPF)
An address-book record listing the servers allowed to send email as the domain.
Email rules record (DMARC)
An address-book record telling mailboxes what to do with email that fails the domain’s sender checks – deliver it, mark it as spam or refuse it – and where to send reports.
Certificate permission record (CAA)
An address-book record naming the companies allowed to issue a security certificate for the domain.

Ask Xovris

Open the full page