# What changed in Xovris

Every change you can use, newest first – what changed in Xovris's AI included, as what it now does for you. Nothing has been released yet: each entry is built and tested, waiting for Xovris to open.

## A failing request is compared with the ones that worked

2 October 2026 · Built, not yet released · Errors · AI change

When requests start failing, Xovris sets them beside the ones that succeeded and names the release and the repository the difference points to, so you start from the change that matters.

Free, Builder – any stack

## Every incident is investigated before you are asked anything

2 October 2026 · Built, not yet released · Investigation · AI change

When something breaks, Xovris works out what happened from your own records and the providers you depend on, and shows you the cause in plain words, with the records that prove it.

Free, Builder – any stack

## Repairs run step by step, and anything that does not hold is put back

2 October 2026 · Built, not yet released · Repair · AI change

A fix runs only within what you allowed, each step recorded; if it does not pass its re-check, the change is put back exactly as it was and the next approach starts – the incident stays open and visibly progressing until a fix is proven.

Builder – any stack

## Tested before, tested after, checked by a separate verifier

2 October 2026 · Built, not yet released · Repair · AI change

Your own failing outcome is reproduced before anything changes, re-run after the fix with the checks around it, confirmed by a verifier separate from the fixer, and re-checked again later; a fix that does not pass is put back and the next approach starts, and you pay nothing for it until the after-test passes.

Free, Builder – any stack

## Every log, check and change in one place, in order, with secrets masked

2 October 2026 · Built, not yet released · Monitoring

Logs from your apps, the result of every check and every change Xovris makes land in one searchable place, kept in the order they really happened across machines, with passwords and keys masked before anything is stored – and every kind of line counted, so a new one stands out.

Free, Builder – any stack

## Connect by address alone, by app install or from your coding agent

2 October 2026 · Built, not yet released · Setup

Start with nothing but your website address, install the app on your platform, or let your coding agent set Xovris up – each connection is read back before it counts, and a connection that stops answering says so instead of staying green.

Free, Builder – any stack

## Uptime, APIs, journeys and scheduled jobs watched from outside

2 October 2026 · Built, not yet released · Monitoring

Pages, APIs, sign-in journeys and cron jobs are checked from Xovris’s probes on a schedule; a job that stops checking in is noticed by the silence, and every result is kept with where and when it was measured.

Free, Builder – any stack

## Domains, DNS and registration watched – and every change explained

2 October 2026 · Built, not yet released · Monitoring

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.

Free, Builder – any stack

## Alerts that say what happened, why, and what is already being done

2 October 2026 · Built, not yet released · Alerts

Every alert carries the exact error, what it means, the cause once found and what Xovris is doing about it; a test alert shows each provider’s own acceptance, built-in email is one press, and a failed channel falls back to email and says so.

Free, Builder – any stack

## API tokens that always expire, with their life shown

2 October 2026 · Built, not yet released · Plans

Named tokens, read-only or read and write, lasting 1 to 365 days with their remaining life as a meter; a token that never expires is not issued.

Free, Builder – any stack

## Every incident has a live tracker, like a parcel delivery

2 October 2026 · Built, not yet released · Repair

Detected, cause found, fix ready, approved, applied, verified – each step appears when its record exists, with its time, so you always know where a problem stands.

Free, Builder – any stack

## A Fix Report in plain words for every fix

2 October 2026 · Built, not yet released · Repair

What was wrong, how it was found, what changed and the before and after side by side – plain words first, the technical line under each, built only from the incident’s own records.

Free, Builder – any stack

## About 1,470 services from open catalogues, each licence checked

2 October 2026 · Built, not yet released · Integrations

The services Xovris connects to come from permissive open catalogues, each install-tested and carrying its licence read from its source; the build refuses one whose licence does not allow it.

Free, Builder – any stack

## Investigations read the providers your site depends on

1 October 2026 · Built, not yet released · Investigation · AI change

When your site fails, Xovris now checks the public status pages, advisories, release notes and issue trackers of the providers in front of it, and cites what it found with the date it was published. An outage at your provider is named as the cause, and your own settings are kept exactly as they are.

Builder – any stack

## A fix is proved on the request that failed – and on the pages around it

1 October 2026 · Built, not yet released · Repair · AI change

After you change something to fix an error, Xovris re-runs the exact request that failed and each workflow next to it, and keeps watching through a window before it calls the issue fixed. A fix that breaks something nearby is caught before it is called done.

Builder – Next.js, Node.js (Express, Fastify), React on Vite

## The free website check shows what the outside world sees

1 October 2026 · Built, not yet released · Monitoring

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.

Free, Builder – any stack

## Set up from your coding agent

1 October 2026 · Built, not yet released · Setup

Claude Code, Cursor and other agents that speak MCP can install Xovris in your project and confirm it is working: setup only counts once a real event from your app is stored.

Free, Builder – Next.js, Node.js (Express, Fastify), React on Vite

## Connect Vercel: every environment gets its own key, read back

1 October 2026 · Built, not yet released · Integrations

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

Free, Builder – Next.js

## Slack alerts, and a disconnect that proves the access is gone

1 October 2026 · Built, not yet released · Alerts

Alerts post to the Slack channel you choose. When you remove Slack, Xovris revokes its access and checks with Slack that the access really is gone before saying so.

Free, Builder – any stack

## Your existing browser tests become monitors

1 October 2026 · Built, not yet released · Monitoring

An existing Playwright test runs unchanged as a check from Xovris’s probes, so the journey you already test is the journey Xovris watches.

Free, Builder – any stack

## Know when a certificate is issued for your domain

1 October 2026 · Built, not yet released · Monitoring

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.

Free, Builder – any stack

## The same error stays one issue across releases

1 October 2026 · Built, not yet released · Errors

Errors from Next.js, Node.js and React apps are grouped the same way when a release changes file names or chunk numbers, so one fault is one issue, not a new one every deploy.

Free, Builder – Next.js, Node.js (Express, Fastify), React on Vite

## A flood of one error never hides the first of another

1 October 2026 · Built, not yet released · Errors

When one fault floods your app, Xovris drops only the repeats: the first occurrence of every other error still arrives in full.

Free, Builder – Next.js, Node.js (Express, Fastify), React on Vite

## Free has no AI anywhere – and every release proves it

1 October 2026 · Built, not yet released · Plans

Checks, alerts and diagnostics on the Free plan never call an AI model, and each release is checked to make sure none does.

Free – any stack

## Jump anywhere with Ctrl+K or Cmd+K

1 October 2026 · Built, not yet released · Command centre

The command centre opens a search-and-jump palette from anywhere, so every page and action is a few keystrokes away.

Free, Builder – any stack

