neon-postgres

Configure Prisma and Drizzle with Neon serverless Postgres pooling and migrations.

Updated Jan 26, 2026
One-click install
npx skills add https://github.com/TwuanMinn/fadelab --skill neon-postgres-twuanminn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: neon-postgres
Source: https://github.com/TwuanMinn/fadelab/tree/main/.agent/skills/skills/neon-postgres
Command: npx skills add https://github.com/TwuanMinn/fadelab --skill neon-postgres-twuanminn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Neon serverless Postgres presents challenges around stable connections, reliable migrations, and ORM integration in serverless environments. This Skill provides patterns to simplify setup and enable scalable, maintainable configurations.

Core Features & Use Cases

  • Prisma with Neon Connection: Configure Prisma for Neon with a pooled connection (PgBouncer) for runtime queries and a direct connection for migrations.
  • Drizzle with Neon Serverless Driver: Use Drizzle ORM with Neon’s serverless HTTP driver or WebSocket driver for edge/serverless environments.
  • Connection Pooling with PgBouncer: Neon provides built-in pooling with up to 10,000 concurrent connections; use pooled endpoints for apps and direct for migrations.
  • Use Case: Deploy a serverless app requiring many concurrent connections, safe migrations, and smooth ORM integration across environments.
  • Note: Branching Neon databases can support development workflows and feature toggles.

Quick Start

Install Neon serverless Postgres, configure Prisma with the pooled URL for runtime queries and the direct URL for migrations, and choose between neon-http or neon-serverless for the driver.

Frequently Asked Questions about neon-postgres

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

FAQPage Schema
How do I configure Prisma with Neon Postgres for both migrations and runtime queries?

Configure Prisma with Neon by using the pooled connection string (PgBouncer) for runtime queries and the direct connection string specifically for running database migrations to ensure reliable execution in serverless environments.

What is the difference between Neon's HTTP and WebSocket serverless drivers?

Neon's serverless drivers handle database connections in edge environments. The HTTP driver is ideal for stateless queries, while the WebSocket driver maintains persistent connections, and both integrate smoothly with Drizzle ORM for serverless Postgres access.

When do I need PgBouncer connection pooling for Neon serverless Postgres?

You need PgBouncer connection pooling for Neon serverless Postgres when your application requires many concurrent connections, as it supports up to 10,000 concurrent connections to prevent exhausting direct database connection limits during traffic spikes.

Can I use Drizzle ORM with Neon's serverless HTTP driver?

Yes, you can use Drizzle ORM with Neon's serverless HTTP driver or WebSocket driver to facilitate database interactions in edge and serverless environments, providing scalable and maintainable configurations without managing traditional connection pools.

Why do my Neon Postgres migrations fail in a serverless environment?

Neon Postgres migrations fail in serverless environments when using pooled PgBouncer endpoints, which block prepared statements; use the direct connection string exclusively for migration workflows to resolve this connection limitation.