Build anything. Keep everything working.

Xovris builds it, watches it and fixes what breaks.

Auto
More: what Xovris does with it, planning first, an idea or an import
What Xovris does with it
Enter to send · Shift+Enter for a new line

Xovris at workReplaying work Xovris has done

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

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

Measured on Xovris’s own service, each figure with when it was read

  • 95–365 ms

    xovris.ai from every continent Xovris asks from

    Answering everywhere

  • 10–74 ms

    api.xovris.ai since Xovris put it right

    Moved the database onto a dedicated core of its own

We send a sign-in code to this address.

Set up with your AI

Xovris sets itself up in your project and asks you before it changes anything.

https://api.xovris.ai/v1/mcp
Add Xovris monitoring to this project.
1. Call the xovris tool install_plan and show me the changes it lists before making any.
2. Run `npx xovris@latest init --yes` in the project folder. When it prints a sign-in link and code, ask me to approve it in my browser - never type a key yourself.
3. Once I have deployed, call run_verify with the connection id the wizard printed and tell me only what it reports.
If I ask to undo it, run `npx xovris@latest remove`.
npx xovris@latest init

How it works

Made with Xovris – and still being improved.

Real pages Xovris made, each running exactly as it came out. Open one and keep shaping it, one message at a time.

The prompt

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

Made by Xovris on 5 Nov from this message – where it began, ready to keep shaping Unedited

Keep building itBuild your own

Open full page

It doesn’t stop at the first answer.

Hand Xovris something once and it stays on it – day and night, for as long as you want it to.

  • It keeps building with you

    Ask for a change whenever you like – the same project picks up where it left off, and the change is there in seconds.

    1. “Make it feel more luxurious - a deep charcoal background with warm gold accents - and add a gallery of my work”Changed in 17 s – the same page, carried on ·
    2. “Let people choose a stylist and a time slot when they book”Changed in 40.6 s – the same page, carried on ·
    Start building
  • It keeps everything you run working

    Whatever you connect, Xovris reads what it is from the thing itself and watches all of it around the clock – when something breaks it follows the fault to its cause and puts that right. Each thing you connect gives it more to follow a fault through.

    xovris.aiAnswering everywhere · Asked it from every place Xovris checks from, at once · 245 ms at the median ·

    What it looks after
  • It remembers

    Xovris remembers everything you tell it, until you ask it to forget.

    Nothing is kept on this browser. Xovris asks before it keeps a conversation, and in your workspace “Forget this” works the same way.

    Every forget comes back with its receipt.

    How your data is kept
  • You stay in charge

    You choose how much it does on its own. Spending money is always your call.

    No spending limit kept on this deviceThe limit you set on /build, kept in this browser only

    How Xovris keeps to it

What will you build, or hand over, today?

Auto
More: what Xovris does with it, planning first, an idea or an import
What Xovris does with it
Enter to send · Shift+Enter for a new line

What will Xovris change on my systems?

Whatever you allow it to fix. Watching needs no access at all. Each connection you grant extends what Xovris can fix, and every fix stays inside what you granted: the exact change you approved, with its undo written down first.

Every permission, scope by scope
What does it cost me?

Watching is free: 50 monitors, for good. Personal adds fixing: Xovris puts problems right for £55.99 a month, and an issue counts only once it works again.Watching is free: 50 monitors, for good. Personal adds fixing: Xovris puts problems right for €65.99 a month, and an issue counts only once it works again.Watching is free: 50 monitors, for good. Personal adds fixing: Xovris puts problems right for US$74.99 a month, and an issue counts only once it works again.

Pricing, in full
How do I undo it?

Everything setup changes is recorded, and one command reverses all of it and revokes the key.

How removal works

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.

Ask Xovris

Open the full page