Connect through Vercel

If your app is deployed on Vercel, the integration writes Xovris’s configuration from Vercel’s side – nothing to paste and no key to copy. It writes the variables only: your app still needs the Xovris SDK to send events. From the first release, let the Xovris GitHub App open that change as a pull request for you, ask your coding agent, or run the one command for your stack. These are the variables it writes into each project you choose:

XOVRIS_INGEST_URL
XOVRIS_INGEST_KEY

See when a project counts as connected

What it writes

For each project you select, and for production and preview, it writes exactly these variables and then reads them back from Vercel before it reports the project as connected:

• XOVRIS_INGEST_URL
• XOVRIS_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

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

• 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.