---
title: "Vercel Marketplace"
description: "Provision a PgBeam project from the Vercel Marketplace, get its proxy connection string as Vercel environment variables, and pay for usage on your Vercel invoice."
canonical: "https://pgbeam.com/docs/vercel-marketplace"
last-updated: "2026-10-30T13:45:52.000Z"
---

# Vercel Marketplace

> Provision a PgBeam project from the Vercel Marketplace, get its proxy connection string as Vercel environment variables, and pay for usage on your Vercel invoice.

URL: https://pgbeam.com/docs/vercel-marketplace

The [Vercel Marketplace](https://vercel.com/marketplace) integration creates PgBeam projects from your Vercel dashboard and bills them through Vercel. Each resource you provision is a PgBeam project. The integration does not register an upstream database or create database credentials, so the `DATABASE_URL` it sets is a template you complete before your app can connect.

> The integration is built and ready. The public Vercel Marketplace listing goes
> live at launch. Until then, provision PgBeam from the
> [dashboard](https://dash.pgbeam.com/sign-up).

## How it works

### Install from Vercel Marketplace

Find PgBeam in the Vercel Marketplace and click **Add Integration**. PgBeam
creates an organization for the installation on the Starter plan.

### Provision a resource

From the integration page, create a PgBeam resource with a name and a
billing plan. PgBeam creates an empty project with that name, applies the
plan's limits, and counts it against the organization's project limit. No
upstream database is attached at this point.

### Complete the connection string

PgBeam returns two environment variables to Vercel:

| Variable            | Value                                                     |
| ------------------- | --------------------------------------------------------- |
| `PGBEAM_PROJECT_ID` | The ID of the PgBeam project                              |
| `DATABASE_URL`      | `postgresql://USER:PASSWORD@<project-host>:5432/DATABASE` |

`<project-host>` is the project's PgBeam proxy hostname. `USER`, `PASSWORD`
and `DATABASE` are literal placeholders, so `DATABASE_URL` does not connect
as set. Register your upstream database on the project, then replace the
placeholders with that database's name and credentials before your app
uses the variable.

## Features

* **Provisioning from Vercel**: create, rename and change the plan of PgBeam projects from the integration page
* **Environment variables**: `DATABASE_URL` (a template to complete) and `PGBEAM_PROJECT_ID` set on provisioning
* **Unified billing**: PgBeam usage appears on your Vercel invoice
* **Per-resource projects**: each resource is its own PgBeam project, and deleting the resource deletes the project

## Billing

PgBeam usage provisioned through the Vercel Marketplace is billed through Vercel. The same plan tiers (Starter, Pro, Scale) and overage rates apply. See [Plans and Limits](/docs/plans) for details.

## Further reading

* [Serverless Connections](/docs/serverless): optimizing for serverless
* [Connection Pooling](/docs/pooling): pool modes and sizing
* [Caching](/docs/cache): query caching and SWR
* [Plans](/docs/plans): plan limits and pricing