vercel-storage

Guides selection, configuration, and migration of Vercel Blob, Global Config, and Marketplace storage services.

Updated Sep 17, 2026
One-click install
npx skills add https://github.com/ridhijain709/AIPORSCHE --skill vercel-storage-ridhijain709
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vercel-storage
Source: https://github.com/ridhijain709/AIPORSCHE/tree/main/.agents/skills/vercel-storage
Command: npx skills add https://github.com/ridhijain709/AIPORSCHE --skill vercel-storage-ridhijain709

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Choosing and configuring the right storage backend for a Vercel application is confusing, especially since @vercel/postgres and @vercel/kv are sunset and Edge Config was renamed to Global Config. This Skill provides authoritative guidance on which storage product to use, how to provision it, and how to migrate away from deprecated packages. ## Core Features & Use Cases - Storage Decision Matrix: Maps needs like file uploads, feature flags, relational data, caching, and vector search to the correct product (Vercel Blob, Global Config, Neon Postgres, Upstash Redis, Supabase, Prisma, MongoDB Atlas, Convex, Turso). - Deprecation & Migration Guidance: Detects usage of sunset packages (@vercel/postgres, @vercel/kv, @vercel/edge-config) and provides drop-in migration paths to @neondatabase/serverless, @upstash/redis, and @vercel/global-config. - Provisioning Workflows: Covers Vercel Marketplace installation via vercel integration add, automatic environment variable provisioning, and fallback manual setup with vercel env pull. - Use Case: You import @vercel/kv in a Next.js project and need to migrate to Upstash Redis with Marketplace provisioning and unified billing without breaking your build. ## Quick Start Ask the agent to help you choose and set up the right Vercel storage option for your project, or to migrate an existing @vercel/postgres or @vercel/kv integration to its supported replacement.

Frequently Asked Questions about vercel-storage

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I migrate from @vercel/postgres to Neon?

Replace @vercel/postgres with @neondatabase/serverless by calling neon(process.env.DATABASE_URL) to get a sql tagged-template client. For minimal changes, use the @neondatabase/vercel-postgres-compat package, and provision Neon via `vercel integration add neon`.

What replaces @vercel/kv for Redis on Vercel?

Upstash Redis replaces @vercel/kv. Install @upstash/redis, create a client with Redis.fromEnv(), and provision it through the Vercel Marketplace with `vercel integration add upstash` for automatic environment variable setup.

Which Vercel storage should I use for file uploads?

Use Vercel Blob for file uploads, media, and documents. It supports public and private access modes, client-side uploads up to 5 TB, and listing or deleting objects through the @vercel/blob package.

Is @vercel/edge-config still supported?

Edge Config was renamed to Global Config, and @vercel/global-config is a drop-in replacement that reads GLOBAL_CONFIG with fallback to EDGE_CONFIG. The legacy package cannot read newly connected stores, so upgrade before connecting a new store.

Why does my Next.js build fail with the Neon serverless driver?

The neon() call throws when DATABASE_URL is unset, and Next.js evaluates top-level module code at build time. Use lazy initialization with a getDb() function instead of a module-level client, and avoid JavaScript Proxy wrappers which break auth adapters.

When should I not use Vercel Global Config?

Do not use Global Config for user data, session state, or frequently written data, since it is optimized for reads at the edge. Use it only for feature flags, A/B testing config, routing rules, and maintenance toggles.