The AI

Tell it what you need. It does the work, and keeps doing it.

Build something, hand over something you run, or ask for a job done – in your own words. Xovris does it on its own, keeps it working day and night, and tells you what it did.

Start free

Xovris at workReplaying work Xovris has done

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

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

What you get is the fix, never a dashboard to watch.

Xovris does the looking after, and tells you what it did.

  • It notices first

    When something starts to go wrong, Xovris has seen it before the people who rely on it do.

  • It puts it right

    It makes the fix itself, as far as you allow, and anything it changes can be put back in one press.

  • It shows you

    Every job comes with a plain account of what it did, in words you can forward.

Everything you run, round the window: these are examples, never the edge - anything with a network is looked after the same way

What was asked

“Keep the checkout on northmerefreight.com working”

BrokenFixingFixednorthmerefreight.com/checkout

northmerefreight.com is unreachable at /checkout

Activity

  1. Xovris opened the incident: no place reaches /checkout
  2. Xovris found what changed
  3. Xovris put it right on its own
  4. Every place reaches /checkout again

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

“Look after my Next.js app”

$ npx xovris init
Found Next.js, using npm.
Signed in to acme
Created an ingestion-only key
5 changes in ~/acme-web
Wrote 5 changes; each is listed in .xovris/manifest.json
Xovris received the test event
Telemetry received – your first event is in Xovris

“Keep xovris.ai working, wherever people are”

  • Germany328 ms
  • United States365 ms
  • Brazil245 ms
  • Japan124 ms
  • Australia195 ms
  • South Africa95 ms

Where it stands now

Working again from every place – 18 October 2026

Live since 19 October 2026 – still growing Keep building it

Connected with one line on 15 November 2026 – a sample app Connect yours

Answering from every place in 95 ms to 365 ms – read 18 November 2026 23:05:29 UTC

XovrisWorkingWorkingWorked for 1.52 s

What Xovris did

On it – reading how /checkout answers from each place, and its records

The causeDNS

northmerefreight.com now points to 198.51.100.66, changed 5 minutes ago

Put right on its ownRehearsal

  1. Started the page: Booking – My Hair Salon
  2. Built Prices
  3. Built Opening Hours
  4. Built Book an Appointment
  5. Checked it: accessibility 100, best practices 100, performance 100 – no failed request, console error or spill at any width
  6. Kept it, ready to change by talking to it - its history starts here
  • Found Next.js, using npm.
  • Signed in to acme
  • Created an ingestion-only key
  • 5 changes in ~/acme-web
  • Wrote 5 changes; each is listed in .xovris/manifest.json
  • Xovris received the test event
  • Telemetry received – your first event is in Xovris
  • Read it from every place at once: Germany, United States, Brazil, Japan, Australia and South Africa
  • Reads it again all the time, and tells you the moment a place stops reaching it

Xovris

Fixed on its own: /checkout

northmerefreight.com is working again from every place.

On your phone

#website

Xovris

Put /checkout on northmerefreight.com right on its own – it is working again.

In your team’s chat

Jobs done by Xovris: a page from the builder, an app connected with one command, and a site put right on its own.

You choose how far Xovris goes and nothing goes further.

Turn it to see what Xovris does at each level. One switch in your settings stops every change at once.

Fix with approval

Your own setting, for when you want to see each change: on the connection the incident is on, Xovris gets the exact change ready – a pull request, an environment setting, a DNS record – makes it the moment you press ‘Yes’ and proves it. One ‘Yes’ covers one change.

Everything it looks after, working today

Every capability built and working now, in its group - each opens the page that shows it in full.

Every capability here is built and working today, each in its group.

Xovris does it for you

Tell Xovris what you use and what you want done. It does the work and stops only for your yes – and doing it yourself always stays one press away.

  • Sets up what you use
  • Ask for it in your own words
  • Asks only for the access it needs
  • Every yes in one sitting
  • Your tools found from your domain
  • Undo for everything it does
  • Explained at your level
  • Keeps itself up to date
  • One place that says how everything is

Fixes problems, and stops them coming back

Problems worked until they are fixed and the fix is confirmed, changes made safely, and the ones Xovris sees coming stopped before they start.

  • Fixed, and working again
  • Repairs, rollbacks and recovery
  • Fixed once, not twice
  • Safe changes
  • Xovris deals with the supplier
  • Your whole IT team
  • Auto-fix for your code

Finds the cause, and shows you the proof

Every look into a problem ends in a report you can check: what happened, what was done and what it saved you.

  • Finds the real cause
  • A report that proves it
  • What Xovris saved you
  • A live tracker and a fixed-by time
  • Results you can check
  • Finds everything you have

Looks after what you connect

Websites and apps are only the start. Each of these is something Xovris looks after once you connect it.

Keeps you and your family safe

Security that acts – weaknesses closed, accounts recovered, scams caught – and help that keeps working when the internet does not.

  • Security
  • Firewall and web filtering
  • Is it a scam?
  • One button for an emergency
  • Protected by what others went through
  • Works when the internet is down

Works with your people

Alerts that reach the right person, people joining and leaving handled, and Xovris there to talk to.

  • Incidents, on-call and status pages
  • Joiners and leavers
  • Glyph and the helper
  • Remembers your setup
  • Your workspace and plan

Build on Xovris

Xovris open to your own programs, the tools you already use, your partners and your own customers.

Your data stays yours, always.

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. What Xovris remembers about your setup is yours to see, correct, pause and delete.

Everything else about security and data is in the trust centre
  • Nothing from one workspace is ever visible to another.
  • It acts up to the level you chose, and nothing beyond it.

Your data lives in the EU (Netherlands and Germany) site, chosen when you sign up.

Where it is kept
  • Your account, checks, incidents and changes the Netherlands
  • Error events and check results the Netherlands
  • The history of each repair while it runs Germany

Every service Xovris relies on is bound by terms that forbid it to train on what you share. Their terms, on the trust centre

Let Xovris look after it.

Start freeEverything each plan includes, side by side

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.
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.
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.

Ask Xovris

Open the full page