Sandbox
Try the real product. No account, no email.
Watch Xovris work, break a sample yourself and watch it find and fix it, then check your own address – all in this page.
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”
northmerefreight.com is unreachable at /checkout
Activity
- Xovris opened the incident: no place reaches /checkout
- Xovris found what changed
- Xovris put it right on its own
- 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
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
- Started the page: Booking – My Hair Salon
- Built Prices
- Built Opening Hours
- Built Book an Appointment
- Checked it: accessibility 100, best practices 100, performance 100 – no failed request, console error or spill at any width
- 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.
Break something, and watch Xovris fix it Watch it found, fixed and proved.
A sample shop’s email setup, held in your browser. Break one record the way a hurried change does, then watch Xovris’s own email check find it, put it right on its own and prove it with the same check. No sign-up, and nothing is sent anywhere.
Every record is in place and the check passes. Break one thing to see what happens.
The domain’s records corner-shop.example
corner-shop.example MX 10 mail.corner-shop.example.corner-shop.example TXT "v=spf1 include:_spf.mail.example ~all"_spf.mail.example TXT "v=spf1 ip4:192.0.2.0/24 -all"_dmarc.corner-shop.example TXT "v=DMARC1; p=quarantine; rua=mailto:dmarc@corner-shop.example"selector1._domainkey.corner-shop.example TXT "v=DKIM1; k=rsa; p=sample-public-key"
- You broke it
- Xovris runs its email check on the domain
- What it found
- It asks before it changes anything
- It writes the change its own finding names
- The same check again: the proof
Would the big mailbox providers take the shop’s mail?
- Gmail Yes
- Yahoo Yes
- Outlook Yes
Could someone else send mail as the shop and have it delivered? No
Now yours. The same checks, on your address.
Type a website or a domain and Xovris reads it in your browser – nothing is saved and you need no account.
Keep it watched, and fixed on its own
Words on this page, in plain English
Each technical word this page uses, said simply.
- 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.
- 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.
- 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.
- Allowed senders record (SPF)
- An address-book record listing the servers allowed to send email as the domain.