PPlatformAppStores

Vercel Marketplace

Cloud

Vercel Inc. · Cloud & infra marketplaces

Best for: Developer-tool and backend-service providers (databases, storage, AI) wanting native billing inside Vercel projects.

Overview

Vercel Marketplace turns Vercel's dashboard into a procurement and provisioning surface for the backing services that frontend and full-stack apps need — databases, caching, observability, auth, and AI. Its distinguishing feature is native integrations: a customer subscribes to a partner product directly inside Vercel without creating a separate account on the partner's site, and resources are provisioned through the Vercel UI or CLI.

The technical model is a two-way API contract. When a user installs an integration, Vercel calls the partner's integration server to create the installation and provision resources, and issues an OAuth2 access token the partner stores to call back into Vercel. Billing is unified: the partner reports usage to Vercel's billing endpoints, and charges appear on the customer's Vercel invoice — so Vercel handles the money movement and payout, functioning as the billing/MoR layer and taking a revenue share. Becoming a partner requires implementing the installation, resource, and billing endpoints and passing Vercel's Integration Approval Checklist. For developers the value is consolidation — one bill, one dashboard, one account for the whole stack.

How to build & ship

  1. 1Apply to and join the Vercel Marketplace / Integrations program as a partner
  2. 2Build an integration server that implements the Partner API endpoints Vercel calls (installations, resource provisioning, SSO)
  3. 3Authenticate installs using OpenID Connect (OIDC) with Vercel's signed JWTs verified via Vercel's JWKS
  4. 4Use the Vercel API to manage resources and submit usage/billing data (at least daily) for integrated billing
  5. 5Configure the integration listing and submit it to Vercel for review before it goes live

Key APIs & SDKs

Vercel Marketplace Partner API
Vercel Marketplace API
Submit Billing Data endpoint
OIDC / JWKS authentication
Vercel Integration Console

Integration types

Connector
Embedded app
Workflow action

Authentication & security

  • Primary auth: OAuth 2.0
  • Also supports: Webhook, API key
  • Security review: Required
  • Native integrations must pass Vercel's Integration Approval Checklist before being publicly listed.
  • Vercel reviews the integration's functionality, billing integration, and listing before approval; exact timelines are not published, so plan for a partner review cycle.
  • Vercel's platform APIs have documented rate limits; provider servers submit billing data on a cadence (at least daily).
Auth docs Store policies

Monetization

Free
Paid app
Usage-based
Revenue share
Onboarding
None documented
Commission
Vercel takes a revenue share on native-integration billing (rate not publicly disclosed)
Merchant of Record
Vercel acts as the billing/reseller layer for native integrations

Pros & cons for builders

Pros

  • Native install and integrated billing on the Vercel account (one-click onboarding, consolidated invoice)
  • Reaches frontend/full-stack developers directly in their deployment workflow
  • OIDC-based secure connection and provisioning model
  • Well-documented Partner/Vercel API split

Cons

  • Audience is scoped to the Vercel developer ecosystem
  • Requires building and hosting a compliant integration backend plus frequent billing submission
  • Newer marketplace with less public detail on review SLAs