> ## Documentation Index
> Fetch the complete documentation index at: https://docs.superlog.sh/llms.txt
> Use this file to discover all available pages before exploring further.

# Vercel

> Connect Vercel so Superlog can read projects, deployments, and logs, and receive traces and logs through drains.

Superlog reads your Vercel projects, deployments, and logs. When you connect from setup, it also creates drains that send traces and logs to Superlog.

## What Superlog reads

* Projects, deployments, deployment checks, and domains.
* Logs.

Superlog does not request write access to deployments or access to environment variables, tokens, or secrets.

## Connect Vercel

**1. Open the Vercel page**

Open **Setup → Sources**, click **Add source**, and choose **Vercel**.

**2. Install the integration**

Click **Continue to Vercel** and install the Superlog integration on your team. Share the projects Superlog should read.

**3. Check the drains**

Back in Superlog, the page lists the drains under **Telemetry from**. A new drain shows **Waiting for data** until Vercel's first delivery.

In **Integrations**, **Add** on Vercel installs the same integration without drains. Workspaces with **Overview** in the sidebar can create drains there. See [Vercel telemetry](https://docs.superlog.sh/collect-telemetry/vercel.md).

## How findings use Vercel

* **New errors.** Drains send your deployments' traces and logs to Superlog. Errors in them become error issues, and Superlog investigates new and regressed ones.
* **Investigations.** Superlog reads deployments and logs for evidence, for example to match an error to a deployment.

## Limits

* Drains need a Vercel Pro or Enterprise team.
* Drains cover the projects you share with the integration.
* Environment variables are not readable.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.