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

# Vercel

> Steadwing connects to Vercel to monitor deployments, build logs, and serverless functions, helping you identify deployment-related root causes automatically.

## What does the Vercel integration do?

Steadwing accesses deployment logs, build events, and project configurations from your Vercel account to diagnose deployment-related incidents. During root cause analysis, Steadwing investigates deployment failures, build errors, and runtime issues to identify the underlying causes of frontend and deployment problems.

## Why Use Vercel with Steadwing?

<CardGroup cols={2}>
  <Card title="Deployment Monitoring" icon="rocket">
    Track deployment status, failures, and build errors in real-time
  </Card>

  <Card title="Build Log Analysis" icon="file-text">
    Analyze complete build logs to identify compilation and dependency issues
  </Card>

  <Card title="Runtime Insights" icon="gauge">
    Monitor runtime logs and errors from deployed applications
  </Card>

  <Card title="Configuration Review" icon="settings">
    Inspect project settings, environment variables, and Edge Config
  </Card>
</CardGroup>

## Connection Methods

There are two ways to connect Vercel to Steadwing. You can use one or both together.

| Method                      | Best For                                                 |
| --------------------------- | -------------------------------------------------------- |
| **Marketplace App (OAuth)** | Auto-triggering RCA when a Vercel deployment event fires |
| **API Token**               | Querying Vercel as a data source during RCA              |

***

## Method 1: Marketplace App (OAuth)

Install Steadwing directly from the Vercel Marketplace. Once installed, Steadwing automatically launches root cause analysis when Vercel deployment events fire no manual intervention needed.

<CardGroup cols={3}>
  <Card title="1-Click Installation" icon="mouse-pointer">
    Install Steadwing directly from the Vercel Marketplace no manual configuration needed.
  </Card>

  <Card title="Auto-Trigger on Events" icon="bell">
    Steadwing automatically kicks off root cause analysis on Vercel deployment events.
  </Card>

  <Card title="In-Depth Analysis & Noise Reduction" icon="magnifying-glass-chart">
    Get comprehensive analysis of every deployment issue while filtering out noise.
  </Card>
</CardGroup>

### Step 1: Install from the Vercel Marketplace

1. Go to the [Steadwing app on Vercel Marketplace](https://vercel.com/marketplace/steadwing/new)
2. Click **Add Integration**
3. Select the Vercel team or personal account to connect
4. Vercel will redirect you to Steadwing to complete the setup

### Step 2: Link to your Steadwing organization

1. After the redirect, select your Steadwing organization from the dropdown
2. Click **Connect** to link the Vercel installation to your organization
3. The app status will show **App installed** on your Vercel integration card in Steadwing Settings

<Note>
  The Marketplace App handles webhook delivery. Steadwing receives Vercel deployment events automatically without any additional configuration.
</Note>

***

## Method 2: API Token

Connect Vercel as a **data source**, allowing Steadwing to query deployment and build data during root cause analysis.

### Step 1: Create Vercel API Token

1. Log in to your Vercel account at [vercel.com](https://vercel.com)
2. Navigate to **Settings** → **Tokens**
   * Direct link: [https://vercel.com/account/tokens](https://vercel.com/account/tokens)
3. Click **Create Token**
4. Configure the token:
   * **Token Name:** Steadwing Integration
   * **Scope:** Select the team/account you want to monitor
   * **Expiration:** Choose an appropriate expiration period (or no expiration)
5. Click **Create Token**
6. Copy the generated token immediately

<Warning>
  Save your token immediately! Vercel only shows it once. If you lose it, you'll
  need to create a new token.
</Warning>

### Step 2: Connect Vercel in Steadwing

1. Navigate to [Steadwing Settings](https://app.steadwing.com/settings)
2. Find the **Vercel** integration card
3. Click **Connect via API Token**
4. Fill in the required fields:
   * **API Token:** Your Vercel API token
5. Click **Connect**

***

## What data does Steadwing pull from Vercel?

Steadwing can query Vercel for:

* **Deployments** - All deployments across your projects with status and timing
* **Build Logs** - Complete build output including errors and warnings
* **Runtime Logs** - Application logs from deployed functions and pages
* **Deployment Events** - Lifecycle events (queued, building, ready, error, canceled)
* **Deployment Checks** - Automated checks and their pass/fail status
* **Project Information** - Project configurations, settings, and metadata
* **Edge Config** - Feature flags and configuration values
* **Domain Aliases** - Custom domains and routing configuration

## Available Capabilities

### Deployment Analysis

* List all deployments with filtering by project, status, and time
* Get detailed deployment information including build configuration
* Retrieve complete build logs with error highlighting
* Track deployment events and state transitions
* Review automated deployment checks and results

### Project Management

* List all projects in your Vercel account
* Get project configuration and settings
* Review environment variables (names only, not values)
* Inspect build and output settings

### Edge Configuration

* List Edge Configs for feature flags and dynamic configuration
* Get specific Edge Config items and their values
* Review Edge Config tokens and access controls

### Team & Access

* List teams and their members
* Review authentication tokens (metadata only)
* Check domain aliases and routing

## What permissions does the Vercel integration need?

The Vercel API token requires:

* **Read access** to deployments and build logs
* **Read access** to project configurations
* **Read access** to Edge Config (if used)
* **Create deployments** — trigger redeployments as part of automated remediation

Steadwing does **NOT** have permission to:

* Change project settings
* Delete resources
* Access environment variable values (only names)
* Modify Edge Config values

<Note>
  Write access to deployments is required for Steadwing to trigger redeployments as part of automated remediation, only after user's approval.
</Note>

### Token Scopes

When creating your token, you can limit access to:

* Specific teams or personal account
* Specific projects (via team selection)

## FAQs

<AccordionGroup>
  <Accordion title="Do I need both connection methods?">
    No. The Marketplace App auto-triggers RCA on deployment events. The API Token lets Steadwing query Vercel as a data source during analysis. Using both together gives you full coverage — automatic triggers plus deep data access.
  </Accordion>

  <Accordion title="What Vercel data does Steadwing access?">
    Steadwing reads deployment logs, build outputs, project configurations, and Edge Config. It does NOT access environment variable values, source code, or modify any settings.
  </Accordion>

  <Accordion title="Can I limit Steadwing's access to specific projects?">
    Yes, when creating the API token, select a specific team scope. This limits access to only that team's projects.
  </Accordion>

  <Accordion title="Does Steadwing trigger new deployments?">
    Yes, Steadwing can trigger redeployments as an automated remediation action when approved by the user. All deployment actions require explicit user approval before execution.
  </Accordion>

  <Accordion title="How does Steadwing use Vercel data during RCA?">
    When a deployment-related incident occurs, Steadwing queries deployment logs, build errors, and configuration to identify issues like failed builds, missing dependencies, or environment problems.
  </Accordion>

  <Accordion title="What if my API token expires?">
    If your token expires or is revoked, the API Token connection will stop working. Create a new token and update it in Steadwing Settings to reconnect.
  </Accordion>

  <Accordion title="Can Steadwing see my environment variables?">
    No, Steadwing can only see environment variable names, not their values. This protects sensitive credentials and secrets.
  </Accordion>
</AccordionGroup>

Need additional help? Please reach out to us at [hello@steadwing.com](mailto:hello@steadwing.com)