Connecting Vercel

Vercel is a service that puts websites and web apps online. If your product already lives on Vercel, connecting it lets Praxeri show you each change working in a private preview of your own Vercel project, before anything reaches your live site.

What it’s for

Previews of your own Vercel project. Once connected, Praxeri can:

link the Vercel project that belongs to your Praxeri project (or create one for it, inside the account you connected);
set the preview and development settings it manages for that project;
start a preview of a change, and read whether it built, its address and a short build summary.

In the beta, Praxeri works with a personal Vercel account (Vercel teams aren’t supported yet) and uses one Vercel project per connection. Vercel bills any usage to your own Vercel account under your Vercel plan. Connecting costs nothing extra from Praxeri.

What Praxeri never does without your approval

Your live site is yours. Praxeri doesn’t deploy to production, promote a preview to production, roll production back, change production settings, or add or change a domain without your approval.

In the beta, these are switched off completely: Praxeri doesn’t publish for you at all. When publishing arrives, each of these steps will wait for you to approve that exact step.

And never, at any stage: delete a Vercel project, change your Vercel plan or billing, buy a domain, or show a secret value again after it’s saved.

One thing to know: if your Vercel project is set to build automatically from GitHub, then adding a change to your project (which only happens when you choose Add to my project) may update your live site through Vercel, the same way it would if you had made the change yourself.

What access the integration asks for

When you connect, Vercel shows you a list of permissions. Here is each one in plain words, and what Praxeri uses it for.

Vercel permissionWhat Praxeri uses it for

Projects · read and writeFind or create the project for your product and read its settings.

Deployments · read and writeStart previews and read whether they built.

Project environment variables · read and write, only the ones the integration createdManage the preview and development settings Praxeri sets up. It can’t see or change the ones you created yourself.

Domains · read and writeSee which domains your project uses. Vercel asks for this up front; Praxeri doesn’t change domains in the beta.

Team · readSee which Vercel account the integration is installed on.

User · readShow you which Vercel account is connected.

Integration configuration · read and writeRead its own installation, and remove it when you disconnect.

What Praxeri may actually do with these permissions is limited by the approval rules above.

How to connect

In Praxeri, open Account, then Connections, and choose Connect Vercel.
Vercel opens. Choose your personal account and the project Praxeri may use, then approve.
You come back to Praxeri. Choose which Vercel project belongs to which Praxeri project.

How to disconnect

In Praxeri: Account, then Connections, then Vercel, then Disconnect. Praxeri stops using Vercel at once and removes its access on Vercel where Vercel allows it.
Or in Vercel: open your account’s Settings, then Integrations, find Praxeri and choose Manage, then Uninstall.

Disconnecting never deletes your Vercel projects, deployments or domains.

Questions