Storage on Vercel Marketplace

The Vercel Marketplace provides integrations with different storage providers to provision databases and data stores directly from your Vercel dashboard.

• For Postgres, you can use providers like Neon, Supabase, or AWS Aurora Postgres.
• For KV (key-value stores), you can use Redis or Upstash Redis.

The integration automatically injects credentials into your projects as environment variables.

When you install a storage integration from the Marketplace, you get:

• Simplified provisioning: Create databases without leaving the Vercel dashboard
• Automatic configuration: Vercel injects connection strings and credentials as environment variables
• Unified billing: Pay for storage resources through your Vercel account

You can add a storage integration from the CLI or the dashboard. Both paths provision the resource, connect it to your Vercel project, and inject credentials as environment variables.

Use vercel install (or its full form, vercel integration add) to provision a resource without leaving your terminal:

vercel install neon

The command installs the integration if it isn't already on your team, provisions the resource, connects it to the currently linked project, and runs vercel env pull to sync credentials into .env.local.

To skip prompts in CI or scripted agent flows, pass options as flags:

vercel install neon --name my-database --plan free -e production -e preview

Run vercel install <integration-name> --help to see the available products, metadata keys, and billing plans for a specific integration. For the full reference, see vercel integration add.

1. Go to the Vercel Marketplace and browse storage integrations.
2. Select an integration and click Install.
3. Choose a pricing plan that fits your needs.
4. Configure your database (name, region, and other options).
5. Connect the storage resource to your Vercel project.

Once connected, the integration automatically adds environment variables to your project. You can then use these variables in your application code to connect to your database.

For detailed steps, see Add a Native Integration.

Vercel can scope a Native Marketplace resource's project environment variables to an exact Custom Environment. For example, a staging deployment can use a staging database without adding the database variables to Production, Preview, or Development in Project Settings.

1. Open the project in the Vercel dashboard.
2. Select Settings, and then select Environments. Create the Custom Environment if the project does not have one.
3. Open Integrations, select Manage for the integration, and open the resource.
4. Select Projects, and then select Connect Project.
5. Select the project. Under Environments, clear all selected built-in environments, including Production and Preview. Then select only the Custom Environment, such as staging. Select a built-in environment only when that environment must also use the resource.
6. Select Connect Project.

You can also connect a resource from the CLI. vercel integration add (also available as vercel install) and vercel integration resource connect accept a Custom Environment slug or stable ID. When you pass a slug, the CLI resolves it to the stable ID before it sends the connection request. vercel integration add resolves the environment against the linked project. vercel integration resource connect resolves the environment against the project argument, or the linked project if you omit the argument.

# Provision a resource and connect it to staging in the linked project
vercel integration add neon --environment staging
 
# Connect an existing resource to staging in the linked project
vercel integration resource connect my-database --environment staging

Repeat --environment to connect more environments. If you omit the option, the commands connect production, preview, and development. The default does not include Custom Environments.

1. Open Project Settings, and then select Environment Variables. Confirm that the integration variables have the exact Custom Environment scope.
2. Deploy to the Custom Environment. For a Custom Environment with the staging slug, run vercel deploy --target=staging.
3. Verify that the deployment can connect to the resource. Do not print secret values.
4. Create a deployment in an environment that you did not select. When no Preview Deployment Action fallback applies, confirm that the environment variables provided by the resource are not available.

For a Custom Environment, Vercel first uses the provider's Preview secret value. If the provider did not set a Preview value, Vercel uses the default secret value.

Existing deployments do not get new or changed variables. Create a new deployment after you connect a resource, change the environment scope, or rotate a secret.

Open the resource's Projects section to change the selected environments. Removing one environment keeps the other selected environments connected. Create a new deployment after each change.

After installation, you can manage your storage resources from the Vercel dashboard:

• View connected projects: See which projects use each storage resource
• Monitor usage: Track storage consumption and costs
• Update configuration: Modify settings or upgrade plans
• Access provider dashboard: Link directly to the provider's management interface
• Browse and query your database: For supported integrations, run queries or commands, view and edit data, and inspect your schema directly from the dashboard
• Transfer resources: For supported integrations, move a resource to a different team

For more details, see Manage Native Integrations.

You can browse, edit, and manage your data directly from the Vercel dashboard, without external tools like psql, redis-cli, or third-party database UIs.

This feature is available for the following integrations:

• Postgres
  • AWS Aurora Postgres
  • Neon
  • Prisma Postgres
  • Supabase
• Redis
  • Redis
  • Upstash for Redis

Support for more integrations will be added over time.

To access the database browser:

1. Open your project in the Vercel dashboard
2. Navigate to the Storage tab and select your database resource
3. Go to the Database section of the database page

You need Owner permissions to access the database browser.

The tabs available in the database section depend on the type of database.

For Postgres integrations, the Query tab lets you run SQL queries and view results in a table. You can copy results as CSV, JSON, or Markdown for use in other tools.

For Postgres integrations, the Data tab displays your table data in a spreadsheet-like interface where you can:

• Sort and filter rows
• Copy data as CSV, JSON, or Markdown
• Edit data
• Insert and delete rows

When you confirm your changes, the data editor applies them to the database as a single transaction.

For Postgres integrations, the Schema tab shows your tables and their relations in a visual graph layout. Use it to understand your database structure without writing queries.

For Redis integrations, the CLI tab allows you to run Redis commands and inspect the results. Run multiple commands by separating them with newlines or semicolons, with support for MULTI/EXEC to run commands in a transaction.

For Redis integrations, the data Browser lets you:

• List keys (optionally grouped by prefix), and filter by type and pattern
• View values for String, JSON, Hash, List, Set, and Sorted set data types
• Inspect metadata for a key, including type, TTL, encoding, and size

Consider these factors when selecting a storage provider:

• Locate data close to your Functions: Deploy databases in regions near your Functions to minimize latency.
• Use connection pooling: In serverless environments, use connection pooling (e.g., built-in pooling or PgBouncer) to manage database connections efficiently.
• Implement caching strategies:
  • Data Cache to cache fetch responses and reduce load
  • Global Config for low-latency reads of config data
  • Redis for frequently accessed, periodically changing data
  • CDN caching with cache headers for static content
• Secure your connections:
  • Store credentials only in environment variables, never in code
  • Use SSL/TLS connections when available

• Add a Native Integration
• Integrations Overview
• Environment Variables
• Functions Regions