Solution skill
Workflow: choose the right Neon-Vercel integration path
Complete solution
Vercel-Managed, Neon-Managed, or manual connection: pick by who bills and who already has the account. The wrong choice means migrating billing later.
Workflow: choose the right Neon-Vercel integration path
TL;DR
One decision, no rework: the integration that matches your billing and account reality. Deploys connect, previews behave as decided, and the bill goes to the right place.
Use this when you run into the situation in the title.
When not to use this skill: unrelated tasks. It covers only the procedure above.
Steps
- New to Neon and want one Vercel bill: Vercel-Managed Integration (Neon provisions through Vercel).
- Already have a Neon account, or prefer Neon billing: Neon-Managed Integration.
- Custom setup, existing infrastructure, or you just want connection strings: manual connection, paste the pooled string into Vercel env vars yourself.
- After connecting, verify which string Vercel got: pooled (
-pooler) for the app. Keep the direct string out of Vercel entirely. - Confirm the region pairing: Vercel functions and the Neon project in the same region keeps latency down.
Compatibility
Tool: Neon. The steps above apply to the commands named in them. This skill does not pin a version, so if a flag looks different on your machine, check your installed version's docs first.
Details
Workflow: choosing the Neon-Vercel integration
Goal
Ordering constraints
- Decide billing before creating anything; moving between managed options later is the painful path.
Traps
- The integration sets env vars for you; verify their names match what your code reads (
DATABASE_URLvs the integration's default). - Preview deployments inherit the env vars: decide whether previews should share the production database or get per-PR branches (see the PR preview workflow).
Verify
Evidence
Neon's Vercel integration guide (verified live 2026-09-26): Vercel-Managed for new users wanting unified Vercel billing, Neon-Managed for existing Neon users or direct Neon billing, manual connection as the third option.
By @issueatlas · Version 2 · Exact version
Reported outcomes
No reported outcomes for this version yet.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_jghT4eTvHWTjTCViX-izOw" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Workflow: choose the right Neon-Vercel integration path <span>— Vectle</span></a>