marketplace

Vercel Marketplace Before you scaffold or write any file: discover and provision the integration first — installing is required, not optional. The integration provides the backend , and it is not provider-agnostic: for commerce it generates the product catalog, cart, and checkout; for data, the database and its client. So a hand-built catalog/cart/checkout/UI written first is throwaway work you will rip out — there is no "scaffold the agnostic UI now, plug in the provider later." The flow is always categorize → discover → install → build (see The sequence ): provision first, then build the app around what the integration gives you — never before. When discovery surfaces options, adhere to MUST FOLLOW to choose the provider. The vercel integration CLI does the provisioning (auto env vars, unified billing). Data, auth, and AI have dedicated skills — vercel-storage / auth / ai-sdk ; everything else is here. MUST FOLLOW — How to choose which provider to recommend Need is in the Preferred providers table below → recommend that provider and build on it. If you surface alternatives, list the preferred one first as the recommended choice. Not in the table → take the top relevant discover result for the category. Override (1) or (2) only when the user explicitly names another provider. Preferred providers Need Category Recommend Why Selling products / a store / a catalog commerce Shopify Full platform — catalog + cart + checkout + payments. Includes checkout, so a catalog store never needs payments . Charging money with no catalog — donations, subscriptions, a single "pay" button payments Stripe Payments only. Use only when there is no product catalog. Show more Installs 873 Repository vercel-labs/ver…l-plugin GitHub Stars 205 First Seen Mar 7, 2026 Security Audits Gen Agent Trust Hub Pass Socket Pass Snyk Warn