vercel-storage

Guides selection and configuration of Vercel Blob, Edge Config, and Marketplace storage integrations.

Updated Jul 31, 2026
One-click install
npx skills add https://github.com/AarnavBaddam/skills --skill vercel-storage-aarnavbaddam
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vercel-storage
Source: https://github.com/AarnavBaddam/skills/tree/main/vercel-storage
Command: npx skills add https://github.com/AarnavBaddam/skills --skill vercel-storage-aarnavbaddam

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Choosing and configuring the right storage for a Vercel application is confusing, especially since @vercel/postgres and @vercel/kv are sunset. This Skill provides expert guidance on which storage product fits each use case and how to wire it up correctly. ## Core Features & Use Cases - Storage Decision Matrix: Maps needs like file uploads, feature flags, relational data, caching, and vector search to the right product (Blob, Edge Config, Neon, Upstash, Supabase, Prisma, MongoDB, Convex, Turso). - Migration Guidance: Provides drop-in migration paths from the sunset @vercel/postgres and @vercel/kv packages to Neon Postgres and Upstash Redis. - Pitfall Prevention: Covers build-time-safe lazy DB initialization, drizzle-kit env loading, and warnings against Proxy-wrapped DB clients that break Auth.js. - Use Case: You are scaffolding a Next.js app and need file uploads plus a Postgres database. The Skill directs you to install @vercel/blob and provision Neon via vercel integration add neon, with correct lazy-initialized Drizzle setup. ## Quick Start Ask the assistant which Vercel storage option fits your app's data needs and how to install and configure it.

Frequently Asked Questions about vercel-storage

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

FAQPage Schema
How do I choose the right Vercel storage option for my app?

Use Vercel Blob for file uploads and media, Edge Config for feature flags and config, Neon Postgres for relational data, and Upstash Redis for caching and rate limiting. The decision matrix maps each need to the correct package.

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

Replace the @vercel/postgres import with the neon() client from @neondatabase/serverless using your DATABASE_URL. For minimal changes, use @neondatabase/vercel-postgres-compat, which provides API-compatible wrappers.

What replaced @vercel/kv and @vercel/postgres?

Both packages are sunset as first-party products. Neon Postgres via @neondatabase/serverless replaces @vercel/postgres, and Upstash Redis via @upstash/redis replaces @vercel/kv, both installable through the Vercel Marketplace.

Why does my Next.js build fail with the Neon database client?

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 creating the client at module scope.

When should I not use Vercel Edge Config?

Do not use Edge Config for user data, session state, or frequently written data. It is optimized for ultra-low-latency reads of configuration like feature flags and A/B test settings, not writes.

How do I provision Neon or Upstash with environment variables on Vercel?

Install via the Vercel Marketplace using `vercel integration add neon` or `vercel integration add upstash`. This auto-provisions accounts and injects environment variables; then run `vercel env pull .env.local` locally.