Skip to content
xovris.ai · 5 of 5 fine · 2 Oct, 01:49 UTC
Join early access
Menu

Investigation and repair

Finds the cause. Makes the fix. Proves it worked.

When something breaks, Xovris finds the cause, makes the change that fixes it and runs the check that failed again before it calls anything resolved. Step through two recorded runs below.

Recorded investigation

Sample data
Critical

example.com stopped answering

The alert

Checked from 3 locations, the request that matters failed. Xovris keeps this failing test: the fix is judged by it.

  • The site answers over HTTPS0 of 3 locations passed
  • The checkout page loads0 of 3 locations passed

What broke

Written by Xovris

A DNS record on the path changed.

The proposed change

example.com (A)Now198.51.100.66After203.0.113.10

The 5 other records in the zone stay exactly as they are, byte for byte.

The access it uses

  • Can readSee your zones and their settings
  • Can readRead DNS records
  • Can changeChange DNS records

If it does not work

Can be undone: the record's state just before the restore is captured first and is written back the same way if verification fails.

Your approval

Why Xovris asked

  • This kind of change is not under your standing policy, so it needs your approval.

Approved by the workspace owner. The approval covers this exact change only; any other change would need its own.

With a standing policy for this kind of change, Xovris makes it without asking – and still proves it.

The change

  1. Applied: the record was written
  2. Proven: the test that failed now passes

The same test, run again

The check that failed runs again from 3 locations. The incident is called fixed only when it passes.

The same test, run againBeforeAfter
The site answers over HTTPS0 of 3 locations passed3 of 3 locations passed
The checkout page loads0 of 3 locations passed3 of 3 locations passed

The receipt

Resolved: fixed and verified

  • The record reads back as restoredPassed
  • Every authoritative name server answers the restored addressPassed
  • Resolvers return the restored addressPassed
  • The site answers healthy againPassed
  • Every other record is byte-for-byte unchangedPassed
  • Email records stay exactly as they werePassed

Investigating and proving this fix used none of your plan’s fixes. Recorded from the product itself on a test domain, example.com. No customer was involved.

After every incident, the whole story in plain words

What you read once Xovris has worked an incident – each sentence linked to the record it stands on, so every statement opens to its evidence.

The incident as a story

What happened, what Xovris changed and the proof that it worked, in plain words – with anything it still needs from you named.

  1. Every sentence links to its record; a sentence with no record is never shown.
  2. Pressing a link moves you to that record, ready to read.
  3. Story or Engineer detail, remembered for each person.

In the command centre: Incidents, then any incident.

The same test, before and after

The check that failed is kept and runs again after the fix, from the same places. You see it fail before and pass after.

  1. The failing result is stored the moment something breaks.
  2. After the change, the same check runs again from the same locations.
  3. Only a pass closes the incident; anything less keeps it open.

In the command centre: on every fixed incident.

Fixed and proven, or nothing to pay

A fix counts towards your plan only once its test passes. Until then the issue stays open, shows where it stands and costs you nothing.

  1. An attempt that does not pass its test is put back, and work continues.
  2. The issue shows where it stands until it is fixed.
  3. Your plan counts an issue once – when it is fixed and proven.

On every plan that includes fixing – see Pricing.

You choose how far Xovris goes

Turn the dial to see what each level lets Xovris do and the exact access it asks for, before you connect anything. Nothing above the level you choose ever runs.

Level of autonomy

Fix with approval

Makes the change itself once you approve that exact change. One approval covers one change.

Can read

  • Can readSee your zones and their settings – To find the zone you chose and confirm its name servers.
  • Can readRead DNS records – To keep every verified version of your records, so a change can be explained and undone.

Can change

  • Can changeChange DNS records – Only if you allow repairs: to put a changed record back to its last verified version under your standing policy.

Before any change, policy requires

  • Your approval of the exact change, every time
  • Repairs are part of Builder
  • Every safety check holds at the moment of the change
  • The change stays inside the evidence you were shown

This is the optional fourth step of setup: Repair authorised.

At every level, the checker that proves a fix and the investigation can never change anything, and one switch in your settings stops every change at once.

What Xovris reads, and what it never does with it

What it reads

  • Your site's public answers – DNS, certificates and HTTPS – as anyone on the internet sees them.
  • The DNS records of the zones you connect (Read DNS records).
  • The error events your app sends to Xovris.
  • Your deployments and releases from Vercel (See your projects and deployments).
  • Public status pages and advisories of the providers your site depends on.

What it never does

  • Your data never trains anyone else’s AI. Xovris learns from fixes only after names, addresses, secrets and content are removed, and only as your settings allow. Xovris only uses providers whose terms forbid training on customer content.
  • Nothing from one workspace is ever visible to another – the database itself enforces it.
  • It never changes anything above the level you chose.

Where it is kept

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

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

Sub-processors

None yet. Xovris processes no customer data until it opens, and every sub-processor that will handle your data, and where, is listed here before it does.

People in the loop

A person approves every change unless you set a standing policy for that kind of change.

Everything else about security and data is in the trust centre

Priced in fixes, not in tokens

An issue counts only once it is fixed and proved. Investigating, retrying and checks that find nothing cost nothing.

Need more fixes? 10 more for US$49, bought ahead – never charged in the middle of an incident.

See it on your own site

Start free: Xovris checks your site in the first minute, and you choose later how far it may go.

Join early accessNo card. Free stays free.