More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Neon Postgres: Serverless Databases Without the Outages

    1

    Run Postgres on Neon without the classic outage: pooled vs direct connections, per-PR preview branches, migration rehearsal, and scale-to-zero cost control.

    $5

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Neon Postgres: Serverless Databases Without the Outages

    Neon Postgres: Serverless Databases Without the Outages

    Example session with this skill installed

    Our Next.js app on Neon keeps failing on migrations and every preview deploy shares one database. Set up pooled/direct connections and per-PR preview branches so deploys stop stepping on each other.

    • Read your context and instructions
    • Compiled the neon postgres

    Split the URLs first: DATABASE_URL pooled for the app, DATABASE_URL_DIRECT unpooled for migrations, seeds, and admin scripts — and the migration tooling was changed to use the direct one explicitly, which stopped the prepared-statement failures that were the outage. Serverless functions now use the HTTP driver instead of holding sockets open across invocations, and the ORM owns the pooled connection everywhere else — one query pattern per codebase. CI creates a branch per pull request (preview/pr-482 from main), runs migrations against it on the direct URL, and injects the branch pooled URL into the Vercel preview deployment. Reviewers click through against realistic data and e2e tests run against the branch. On merge the branch is deleted, and a scheduled job sweeps branches older than 7 days. Migration rehearsal happens on a branch of production before the real run — the branch costs almost nothing, copy-on-write. Dev and preview databases scale to zero by default, with alerts on primary compute hours instead of dashboards nobody reads. The next incident review answered 'did the migration break prod?' by pointing at the branch rehearsal log, not by memory. The pattern is boring on purpose: boring connections do not page anyone at 2am.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Neon is Postgres with compute separated from storage — databases that scale to zero, branch instantly, and restore to any point in time — and the mistakes are all in connection handling and treating branches as free. This skill settles the one decision that matters: pooled connections for app runtime, direct connections for migrations, seeds, and admin scripts, with both URLs in env and the migration tooling pinned to the direct one. It covers the HTTP driver for serverless functions, per-PR preview branches in CI, safe migration rehearsal on a branch of production, backwards-compatible expand/contract migrations, and the cost hygiene that keeps scale-to-zero actually cheap.

    It covers connection, branching, and migration discipline on Neon — not the design of your schema or your queries. Cold starts are real: the first query after idle pays a wake-up cost, and latency-sensitive paths need a minimum compute or a warm path, measured first. Branches are not backups — point-in-time restore is the backup story — and stale branches drift, so they get deleted aggressively.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 3 days ago

    Permissions

    Environment Variables
    Listed3 days ago

    What's inside

    Frequently Asked Questions

    No — it is the signal. PgBouncer transaction mode breaks prepared statements and session features. Point the ORM at the pooled URL for runtime and run migrations on the direct URL.

    Do not. Concurrent deploys mean concurrent migration attempts. Migrations run from CI, against the direct URL, exactly once, in order.

    They are cheap, not free, and they drift. Delete on merge and sweep anything older than 7 days — a 6-month-old branch someone 'might need' is how you get surprised.