Skip to content

Get started with Xovris

  • Watches what you run
  • Says when it breaks
  • Works out why
  • Fixes it, if you allow
  • Proves the fix
Terminal window
npx xovris@latest init
Check your website now
  • GitHub: one pull request with every change your app needs, for you to review and merge.
  • Vercel: its variables written into the projects you choose, and read back.
  • Slack: a test alert sent, and Slack’s own acceptance shown.

You sign in and approve – only the account’s owner can – and Xovris does the rest, waiting with you while you do. Setup says it is done only when it really is: when your first real event has arrived.

  1. Enter your website address. Your browser checks HTTPS, DNS and the domain’s registration now, and Xovris’s probe adds the certificate. There is no code to install and no account to connect. How website checks work.
  2. Connect your app. Xovris opens the change as a pull request through the Xovris GitHub App, or writes the variables through Vercel – nothing to paste. Do it yourself instead: run one command in your project. Choose your stack – each guide takes you through it:
  1. Get alerts where you will see them. Email alerts are on from the start, and Xovris adds Slack for you after one approval in Slack – it sends a test alert and shows Slack’s own acceptance. Do it yourself instead: add Slack or a webhook on Alerts whenever you like. 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:

Ask Xovris

Open the full page

Your data is never used to train our AI. How your data is kept

A problem is called fixed only once it works again. How each fix is checked

XOVRIS LTD, registered in England and Wales, company number 17499910. Registered office: 66 Paul Street, London EC2A 4NA.