Skip to content

Get started with Xovris

Xovris watches what your business runs online, tells you the moment something breaks, works out why, and – where you have allowed it – fixes it and proves the fix worked. Setup says it is done only when it really is: when your first real event has arrived.

Ships with the first release

One command finds your framework, signs you in from your browser, installs Xovris, writes your settings and waits until a real event from your app arrives – nothing to copy or paste.

Email me the day it shipsCheck your website now

Check your website now – nothing to install

From the first release, add the Xovris MCP server to your agent, then paste the prompt. Your agent runs the same wizard and verify step as you would, and asks you to approve the sign-in in your browser – it never sees a key. More on the coding-agent path.

Ships with the first release

Each coding agent gets its own one-line way to add Xovris – a command, a setting or a link – and signs you in from your browser the first time.

  • Claude Code
  • Codex
  • Gemini CLI
  • GitHub Copilot CLI
  • VS Code
  • Cursor
  • LM Studio
  • Goose
  • Windsurf
  • ChatGPT
  • Claude
  • Any MCP client

Email me the day it shipsCheck your website now

Ships with the first release

Paste one prompt into your coding agent and it sets Xovris up for you: it shows you every change first and asks you to approve the sign-in.

Preview – this is the prompt you will paste
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`.

Email me the day it shipsCheck your website now

  1. Enter your website address. Your browser checks HTTPS, DNS and the domain’s registration now, and Xovris’s probe adds the certificate from launch. There is no code to install and no account to connect. How website checks work.
  2. Connect your app. From the first release, run one command in your project, let the Xovris GitHub App open the change as a pull request, or connect through Vercel for the variables. Choose your stack – each guide shows when its install test last passed:
  1. Get alerts where you will see them. Email alerts are on from the start. When you add Slack, a test alert shows Slack’s own acceptance. If a channel fails, Xovris tells you which one and sends the alert by email instead.

Everything here is published for machines as well as people: