Know it is working
Every connection – your website address, your app, Vercel, your DNS provider – goes through the same four steps, and each step turns green only when the real thing has arrived, never on a promise. You are never told setup is done while nothing is actually being watched.
Ships with the first release
One command checks that a real event from your app has arrived and, if not, names what is missing and the next step.
1. Connected
Section titled “1. Connected”- Website address: the address was accepted for checking.
- Your app: its key was accepted, or the first event arrived carrying it.
- Vercel or a DNS provider: the provider accepted the access you granted.
2. First signal
Section titled “2. First signal”- Website address and DNS: the first round of checks has arrived.
- Your app: the first event has arrived – the setup’s own test event counts here.
3. Watched for real
Section titled “3. Watched for real”- Website address and DNS: a full round of checks has arrived.
- Your app: a real event from your live app has arrived. The setup’s test event alone never reaches this step.
4. Allowed to fix – optional
Section titled “4. Allowed to fix – optional”Only for connections that can change something: a DNS provider or Vercel. This step turns green when the access you granted lets Xovris make a change. A connection you gave read-only access is shown as able to watch only, and its fix controls stay off.
When a step goes back
Section titled “When a step goes back”If a key is switched off or a provider stops accepting the access, the connection shows that at once, with the cause and what to do next. It never keeps showing a step it can no longer prove.