Vercel

#What Opriven does with Vercel

• List teams and projects to know what's deployed where
• Track deployment history and find the release that preceded a failure
• Retrieve build logs to debug why a deployment failed during build
• Query runtime logs filtered by status code, source, and time range
• Read project configuration and settings for deployment context

#Connecting Vercel

Prerequisites

• A Vercel account with permissions to create access tokens
• If using Vercel Teams, your team slug (found in your team's URL: vercel.com/)

1. Create a Vercel access token

   Go to Vercel Access Tokens and click Create. Name it Opriven, choose Full Account scope (or scope it to a specific team), and set an expiration that fits your security policy.

   Save the token securely — it won't be shown again.

2. Enter the token in Opriven

   Paste your access token on the Opriven integration page.

3. Enter your team slug (optional)

   We recommend entering your Vercel team slug to scope queries to the right team — it's the value in your team's URL, vercel.com/<team-slug>.

#Permissions and access

Opriven uses your access token for read-only operations. No deployments are triggered, no settings are modified, and no data is written to your Vercel account.

All tenant data is processed in isolated environments. See security and compliance for details.