Connect through Vercel
If your app is deployed on Vercel, Xovris does the setup from Vercel’s side: you approve the Xovris integration once in the Vercel Marketplace and choose the projects, and Xovris writes its configuration into each one – nothing to paste and no key to copy. Your app still needs the Xovris SDK to send events, and Xovris adds that too: the Xovris GitHub App opens the change as a pull request for you to approve. Approving stays yours, because only the account’s owner may grant access; Xovris waits while you do and carries on the moment it can. If you prefer to do it yourself instead, run the one command for your stack. These are the variables it writes into each project you choose:
XOVRIS_INGEST_URLXOVRIS_INGEST_KEYWhat it writes
Section titled “What it writes”For each project you select, and for production and preview, it writes exactly these variables:
XOVRIS_INGEST_URLXOVRIS_INGEST_KEY
The key is stored as a sensitive variable: Vercel never shows it again, and it can only send events, never read them.
Environments and releases
Section titled “Environments and releases”Every deployment is mapped to an environment: production deployments to production, preview deployments to preview, and a custom environment to its own name. The commit of each deployment becomes its release, so an error is tied to the change that shipped it.
Removing a project or the integration
Section titled “Removing a project or the integration”- Removing a project from the integration revokes that project’s key, so it stops sending.
- Uninstalling deletes only the variables Xovris added, revokes every key it issued, and reads both back.
Every request from Vercel to Xovris is signed, and an unsigned or forged one is rejected.
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.