[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill-neon-neon-postgres":3,"mdc-trb84y-key":37,"related-repo-neon-neon-postgres":832,"related-org-neon-neon-postgres":841},{"slug":4,"name":4,"fn":5,"description":6,"org":7,"tags":12,"stars":24,"repoUrl":25,"updatedAt":26,"license":27,"forks":28,"topics":29,"repo":32,"sourceUrl":35,"mdContent":36},"neon-postgres","build apps with Neon serverless Postgres","Guides and best practices for working with Neon Serverless Postgres. Covers setup, connection methods and drivers, pooled vs direct connections, branching, autoscaling, scale-to-zero, instant restore, read replicas, connection pooling, IP allow lists, and logical replication. Use when users ask about \"Neon setup\", \"connect to Neon\", \"Neon project\", \"DATABASE_URL\", \"serverless Postgres\", \"Neon CLI\", \"neon\", \"Neon MCP\", \"Neon Auth\", \"@neondatabase\u002Fserverless\", \"@neondatabase\u002Fneon-js\", \"scale to zero\", \"Neon autoscaling\", \"Neon read replica\", or \"Neon connection pooling\".",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},"neon","Neon","https:\u002F\u002Fpexgzepcugksgbtrxkhf.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Forg-logos\u002Fneon.png","neondatabase",[13,15,18,21],{"name":9,"slug":8,"type":14},"tag",{"name":16,"slug":17,"type":14},"Database","database",{"name":19,"slug":20,"type":14},"PostgreSQL","postgresql",{"name":22,"slug":23,"type":14},"Serverless","serverless",321,"https:\u002F\u002Fgithub.com\u002Fneondatabase\u002Fwebsite","2026-07-27T06:08:14.168734",null,304,[30,31],"docs","website",{"repoUrl":25,"stars":24,"forks":28,"topics":33,"description":34},[30,31],"Official docs and website for Neon.","https:\u002F\u002Fgithub.com\u002Fneondatabase\u002Fwebsite\u002Ftree\u002FHEAD\u002Fpublic\u002Fdocs\u002Fai\u002Fskills\u002Fneon-postgres","---\nname: neon-postgres\ndescription: >-\n  Guides and best practices for working with Neon Serverless Postgres.\n  Covers setup, connection methods and drivers, pooled vs direct connections,\n  branching, autoscaling, scale-to-zero, instant restore, read replicas,\n  connection pooling, IP allow lists, and logical replication.\n  Use when users ask about \"Neon setup\", \"connect to Neon\", \"Neon project\",\n  \"DATABASE_URL\", \"serverless Postgres\", \"Neon CLI\", \"neon\", \"Neon MCP\",\n  \"Neon Auth\", \"@neondatabase\u002Fserverless\", \"@neondatabase\u002Fneon-js\",\n  \"scale to zero\", \"Neon autoscaling\", \"Neon read replica\", or\n  \"Neon connection pooling\".\nmetadata:\n  parent: neon\n---\n\n**FIRST**: Use the parent `neon` skill for a Neon platform overview, getting started with Neon, Neon development best practices, and more.\n\nIf the `neon` skill is not installed, fetch it from https:\u002F\u002Fneon.com\u002Fdocs\u002Fai\u002Fskills\u002Fneon\u002FSKILL.md or install it with:\n\n```bash\nnpx skills add neondatabase\u002Fagent-skills --skill neon\n```\n\n# Neon Serverless Postgres\n\nServerless Postgres is the core of the Neon platform. It separates compute and storage to offer autoscaling, branching, instant restore, and scale-to-zero. It's fully compatible with Postgres and works with any language, framework, or ORM that supports Postgres.\n\n## Setup Flow\n\n### 1. Select the organization and project\n\nUse the CLI (default) or MCP server to list organizations and projects. Let the user select an existing project or create a new one. Check the `.neon` file for an existing linked project or branch.\n\n### 2. Get the connection string\n\nUse the CLI (default), `neon env pull`, or the MCP server to get the connection string. Store it in `.env` as `DATABASE_URL`. Read the file first before modifying it, to avoid overwriting existing values.\n\n#### When to use pooled vs direct connections\n\n| Use case                                 | Connection type  |\n| ---------------------------------------- | ---------------- |\n| Web applications, serverless functions   | Pooled (-pooler) |\n| Schema migrations                        | Direct           |\n| pg_dump \u002F pg_restore                     | Direct           |\n| Logical replication                      | Direct           |\n| Long-running analytics with temp tables  | Direct           |\n| Admin tasks needing SET or session state | Direct           |\n| LISTEN \u002F NOTIFY                          | Direct           |\n\n### 3. Pick the connection method and driver\n\nAlways pair Neon with an ORM such as **Drizzle** for easy schema management and migrations. Refer to the connection methods guide to pick the correct driver based on how the runtime treats your code: https:\u002F\u002Fneon.com\u002Fdocs\u002Fconnect\u002Fchoose-connection.md.\n\nRecommendations:\n\n- Drizzle as ORM (see https:\u002F\u002Fneon.com\u002Fdocs\u002Fguides\u002Fdrizzle.md)\n- On Vercel, use `node-postgres` (`npm install pg`) with Vercel Fluid compute and `import { attachDatabasePool } from \"@vercel\u002Ffunctions\";`\n- On Cloudflare, use `node-postgres` with Cloudflare Hyperdrive\n- On Neon Functions, use `node-postgres`, as the functions are long-running and reuse the pool across requests.\n- Use the `@neondatabase\u002Fserverless` driver for serverless and edge environments (for example, when using Netlify) — HTTP transport for one-shot queries, WebSocket for transaction support. Link: https:\u002F\u002Fneon.com\u002Fdocs\u002Fserverless\u002Fserverless-driver.md\n\n### 4. Set up the schema\n\nManage schemas and migrations as code. Avoid running ad hoc schema migrations against your database, since they're hard to manage.\n\nIf you're using an ORM, follow your ORM's best practices to manage schemas and migrations. For example, if using Drizzle, only use Drizzle for schema and migration management unless instructed otherwise.\n\n## Branching\n\nUse this when the user is planning isolated environments, schema migration testing, preview deployments, or branch lifecycle automation.\n\nKey points:\n\n- Branches are instant, copy-on-write clones (no full data copy).\n- Each branch has its own compute endpoint.\n- Use the neon CLI or MCP server to create, inspect, and compare branches.\n\nLink: https:\u002F\u002Fneon.com\u002Fdocs\u002Fintroduction\u002Fbranching.md\n\nFor detailed branch creation workflows (normal vs schema-only branches, reset-from-parent, CLI\u002FMCP selection), use the `neon-postgres-branches` skill. If it isn't installed, fetch it from https:\u002F\u002Fneon.com\u002Fdocs\u002Fai\u002Fskills\u002Fneon-postgres-branches\u002FSKILL.md or install it with:\n\n```bash\nnpx skills add neondatabase\u002Fagent-skills --skill neon-postgres-branches\n```\n\n## Autoscaling\n\nUse this when the user needs compute to scale automatically with workload and wants guidance on CU sizing and runtime behavior.\n\nLink: https:\u002F\u002Fneon.com\u002Fdocs\u002Fintroduction\u002Fautoscaling.md\n\n## Scale to Zero\n\nUse this when optimizing idle costs and discussing suspend\u002Fresume behavior, including cold-start trade-offs.\n\nKey points:\n\n- Idle computes suspend automatically after a default of 5 minutes; the timeout is configurable, and suspension can only be disabled on the Launch and Scale plans.\n- First query after suspend typically has a cold-start penalty (around hundreds of ms)\n- Storage remains active while compute is suspended.\n\nLink: https:\u002F\u002Fneon.com\u002Fdocs\u002Fintroduction\u002Fscale-to-zero.md\n\n## Instant Restore\n\nUse this when the user needs point-in-time recovery or wants to restore data state without traditional backup restore workflows.\n\nKey points:\n\n- History windows for instant restore depend on plan limits.\n- Users can create branches from historical points-in-time.\n- Time Travel queries can be used for historical inspection workflows.\n\nLink: https:\u002F\u002Fneon.com\u002Fdocs\u002Fintroduction\u002Fbranch-restore.md\n\n## Read Replicas\n\nUse this for read-heavy workloads where the user needs dedicated read-only compute without duplicating storage.\n\nKey points:\n\n- Replicas are read-only compute endpoints sharing the same storage.\n- Creation is fast and scaling is independent from primary compute.\n- Typical use cases: analytics, reporting, and read-heavy APIs.\n\nLink: https:\u002F\u002Fneon.com\u002Fdocs\u002Fintroduction\u002Fread-replicas.md\n\n## Connection Pooling\n\nUse this when the user is in serverless or high-concurrency environments and needs safe, scalable Postgres connection management.\n\nKey points:\n\n- Neon pooling uses PgBouncer.\n- Add `-pooler` to endpoint hostnames to use pooled connections.\n- Pooling is especially important in serverless runtimes with bursty concurrency.\n\nLink: https:\u002F\u002Fneon.com\u002Fdocs\u002Fconnect\u002Fconnection-pooling.md\n\n## IP Allow Lists\n\nUse this when the user needs to restrict database access by trusted networks, IPs, or CIDR ranges.\n\nLink: https:\u002F\u002Fneon.com\u002Fdocs\u002Fintroduction\u002Fip-allow.md\n\n## Logical Replication\n\nUse this when integrating CDC pipelines, external Postgres sync, or replication-based data movement.\n\nKey points:\n\n- Neon supports native logical replication workflows.\n- Useful for replicating to\u002Ffrom external Postgres systems.\n\nLink: https:\u002F\u002Fneon.com\u002Fdocs\u002Fguides\u002Flogical-replication-guide.md\n",{"data":38,"body":40},{"name":4,"description":6,"metadata":39},{"parent":8},{"type":41,"children":42},"root",[43,65,87,136,143,148,155,162,175,181,210,217,331,337,357,362,450,456,461,466,472,477,482,500,511,531,566,572,577,587,593,598,602,620,630,636,641,645,663,673,679,684,688,706,716,722,727,731,757,767,773,778,788,794,799,803,816,826],{"type":44,"tag":45,"props":46,"children":47},"element","p",{},[48,55,57,63],{"type":44,"tag":49,"props":50,"children":51},"strong",{},[52],{"type":53,"value":54},"text","FIRST",{"type":53,"value":56},": Use the parent ",{"type":44,"tag":58,"props":59,"children":61},"code",{"className":60},[],[62],{"type":53,"value":8},{"type":53,"value":64}," skill for a Neon platform overview, getting started with Neon, Neon development best practices, and more.",{"type":44,"tag":45,"props":66,"children":67},{},[68,70,75,77,85],{"type":53,"value":69},"If the ",{"type":44,"tag":58,"props":71,"children":73},{"className":72},[],[74],{"type":53,"value":8},{"type":53,"value":76}," skill is not installed, fetch it from ",{"type":44,"tag":78,"props":79,"children":83},"a",{"href":80,"rel":81},"https:\u002F\u002Fneon.com\u002Fdocs\u002Fai\u002Fskills\u002Fneon\u002FSKILL.md",[82],"nofollow",[84],{"type":53,"value":80},{"type":53,"value":86}," or install it with:",{"type":44,"tag":88,"props":89,"children":94},"pre",{"className":90,"code":91,"language":92,"meta":93,"style":93},"language-bash shiki shiki-themes material-theme-lighter material-theme material-theme-palenight","npx skills add neondatabase\u002Fagent-skills --skill neon\n","bash","",[95],{"type":44,"tag":58,"props":96,"children":97},{"__ignoreMap":93},[98],{"type":44,"tag":99,"props":100,"children":103},"span",{"class":101,"line":102},"line",1,[104,110,116,121,126,131],{"type":44,"tag":99,"props":105,"children":107},{"style":106},"--shiki-light:#E2931D;--shiki-default:#FFCB6B;--shiki-dark:#FFCB6B",[108],{"type":53,"value":109},"npx",{"type":44,"tag":99,"props":111,"children":113},{"style":112},"--shiki-light:#91B859;--shiki-default:#C3E88D;--shiki-dark:#C3E88D",[114],{"type":53,"value":115}," skills",{"type":44,"tag":99,"props":117,"children":118},{"style":112},[119],{"type":53,"value":120}," add",{"type":44,"tag":99,"props":122,"children":123},{"style":112},[124],{"type":53,"value":125}," neondatabase\u002Fagent-skills",{"type":44,"tag":99,"props":127,"children":128},{"style":112},[129],{"type":53,"value":130}," --skill",{"type":44,"tag":99,"props":132,"children":133},{"style":112},[134],{"type":53,"value":135}," neon\n",{"type":44,"tag":137,"props":138,"children":140},"h1",{"id":139},"neon-serverless-postgres",[141],{"type":53,"value":142},"Neon Serverless Postgres",{"type":44,"tag":45,"props":144,"children":145},{},[146],{"type":53,"value":147},"Serverless Postgres is the core of the Neon platform. It separates compute and storage to offer autoscaling, branching, instant restore, and scale-to-zero. It's fully compatible with Postgres and works with any language, framework, or ORM that supports Postgres.",{"type":44,"tag":149,"props":150,"children":152},"h2",{"id":151},"setup-flow",[153],{"type":53,"value":154},"Setup Flow",{"type":44,"tag":156,"props":157,"children":159},"h3",{"id":158},"_1-select-the-organization-and-project",[160],{"type":53,"value":161},"1. Select the organization and project",{"type":44,"tag":45,"props":163,"children":164},{},[165,167,173],{"type":53,"value":166},"Use the CLI (default) or MCP server to list organizations and projects. Let the user select an existing project or create a new one. Check the ",{"type":44,"tag":58,"props":168,"children":170},{"className":169},[],[171],{"type":53,"value":172},".neon",{"type":53,"value":174}," file for an existing linked project or branch.",{"type":44,"tag":156,"props":176,"children":178},{"id":177},"_2-get-the-connection-string",[179],{"type":53,"value":180},"2. Get the connection string",{"type":44,"tag":45,"props":182,"children":183},{},[184,186,192,194,200,202,208],{"type":53,"value":185},"Use the CLI (default), ",{"type":44,"tag":58,"props":187,"children":189},{"className":188},[],[190],{"type":53,"value":191},"neon env pull",{"type":53,"value":193},", or the MCP server to get the connection string. Store it in ",{"type":44,"tag":58,"props":195,"children":197},{"className":196},[],[198],{"type":53,"value":199},".env",{"type":53,"value":201}," as ",{"type":44,"tag":58,"props":203,"children":205},{"className":204},[],[206],{"type":53,"value":207},"DATABASE_URL",{"type":53,"value":209},". Read the file first before modifying it, to avoid overwriting existing values.",{"type":44,"tag":211,"props":212,"children":214},"h4",{"id":213},"when-to-use-pooled-vs-direct-connections",[215],{"type":53,"value":216},"When to use pooled vs direct connections",{"type":44,"tag":218,"props":219,"children":220},"table",{},[221,240],{"type":44,"tag":222,"props":223,"children":224},"thead",{},[225],{"type":44,"tag":226,"props":227,"children":228},"tr",{},[229,235],{"type":44,"tag":230,"props":231,"children":232},"th",{},[233],{"type":53,"value":234},"Use case",{"type":44,"tag":230,"props":236,"children":237},{},[238],{"type":53,"value":239},"Connection type",{"type":44,"tag":241,"props":242,"children":243},"tbody",{},[244,258,271,283,295,307,319],{"type":44,"tag":226,"props":245,"children":246},{},[247,253],{"type":44,"tag":248,"props":249,"children":250},"td",{},[251],{"type":53,"value":252},"Web applications, serverless functions",{"type":44,"tag":248,"props":254,"children":255},{},[256],{"type":53,"value":257},"Pooled (-pooler)",{"type":44,"tag":226,"props":259,"children":260},{},[261,266],{"type":44,"tag":248,"props":262,"children":263},{},[264],{"type":53,"value":265},"Schema migrations",{"type":44,"tag":248,"props":267,"children":268},{},[269],{"type":53,"value":270},"Direct",{"type":44,"tag":226,"props":272,"children":273},{},[274,279],{"type":44,"tag":248,"props":275,"children":276},{},[277],{"type":53,"value":278},"pg_dump \u002F pg_restore",{"type":44,"tag":248,"props":280,"children":281},{},[282],{"type":53,"value":270},{"type":44,"tag":226,"props":284,"children":285},{},[286,291],{"type":44,"tag":248,"props":287,"children":288},{},[289],{"type":53,"value":290},"Logical replication",{"type":44,"tag":248,"props":292,"children":293},{},[294],{"type":53,"value":270},{"type":44,"tag":226,"props":296,"children":297},{},[298,303],{"type":44,"tag":248,"props":299,"children":300},{},[301],{"type":53,"value":302},"Long-running analytics with temp tables",{"type":44,"tag":248,"props":304,"children":305},{},[306],{"type":53,"value":270},{"type":44,"tag":226,"props":308,"children":309},{},[310,315],{"type":44,"tag":248,"props":311,"children":312},{},[313],{"type":53,"value":314},"Admin tasks needing SET or session state",{"type":44,"tag":248,"props":316,"children":317},{},[318],{"type":53,"value":270},{"type":44,"tag":226,"props":320,"children":321},{},[322,327],{"type":44,"tag":248,"props":323,"children":324},{},[325],{"type":53,"value":326},"LISTEN \u002F NOTIFY",{"type":44,"tag":248,"props":328,"children":329},{},[330],{"type":53,"value":270},{"type":44,"tag":156,"props":332,"children":334},{"id":333},"_3-pick-the-connection-method-and-driver",[335],{"type":53,"value":336},"3. Pick the connection method and driver",{"type":44,"tag":45,"props":338,"children":339},{},[340,342,347,349,355],{"type":53,"value":341},"Always pair Neon with an ORM such as ",{"type":44,"tag":49,"props":343,"children":344},{},[345],{"type":53,"value":346},"Drizzle",{"type":53,"value":348}," for easy schema management and migrations. Refer to the connection methods guide to pick the correct driver based on how the runtime treats your code: ",{"type":44,"tag":78,"props":350,"children":353},{"href":351,"rel":352},"https:\u002F\u002Fneon.com\u002Fdocs\u002Fconnect\u002Fchoose-connection.md",[82],[354],{"type":53,"value":351},{"type":53,"value":356},".",{"type":44,"tag":45,"props":358,"children":359},{},[360],{"type":53,"value":361},"Recommendations:",{"type":44,"tag":363,"props":364,"children":365},"ul",{},[366,380,407,419,431],{"type":44,"tag":367,"props":368,"children":369},"li",{},[370,372,378],{"type":53,"value":371},"Drizzle as ORM (see ",{"type":44,"tag":78,"props":373,"children":376},{"href":374,"rel":375},"https:\u002F\u002Fneon.com\u002Fdocs\u002Fguides\u002Fdrizzle.md",[82],[377],{"type":53,"value":374},{"type":53,"value":379},")",{"type":44,"tag":367,"props":381,"children":382},{},[383,385,391,393,399,401],{"type":53,"value":384},"On Vercel, use ",{"type":44,"tag":58,"props":386,"children":388},{"className":387},[],[389],{"type":53,"value":390},"node-postgres",{"type":53,"value":392}," (",{"type":44,"tag":58,"props":394,"children":396},{"className":395},[],[397],{"type":53,"value":398},"npm install pg",{"type":53,"value":400},") with Vercel Fluid compute and ",{"type":44,"tag":58,"props":402,"children":404},{"className":403},[],[405],{"type":53,"value":406},"import { attachDatabasePool } from \"@vercel\u002Ffunctions\";",{"type":44,"tag":367,"props":408,"children":409},{},[410,412,417],{"type":53,"value":411},"On Cloudflare, use ",{"type":44,"tag":58,"props":413,"children":415},{"className":414},[],[416],{"type":53,"value":390},{"type":53,"value":418}," with Cloudflare Hyperdrive",{"type":44,"tag":367,"props":420,"children":421},{},[422,424,429],{"type":53,"value":423},"On Neon Functions, use ",{"type":44,"tag":58,"props":425,"children":427},{"className":426},[],[428],{"type":53,"value":390},{"type":53,"value":430},", as the functions are long-running and reuse the pool across requests.",{"type":44,"tag":367,"props":432,"children":433},{},[434,436,442,444],{"type":53,"value":435},"Use the ",{"type":44,"tag":58,"props":437,"children":439},{"className":438},[],[440],{"type":53,"value":441},"@neondatabase\u002Fserverless",{"type":53,"value":443}," driver for serverless and edge environments (for example, when using Netlify) — HTTP transport for one-shot queries, WebSocket for transaction support. Link: ",{"type":44,"tag":78,"props":445,"children":448},{"href":446,"rel":447},"https:\u002F\u002Fneon.com\u002Fdocs\u002Fserverless\u002Fserverless-driver.md",[82],[449],{"type":53,"value":446},{"type":44,"tag":156,"props":451,"children":453},{"id":452},"_4-set-up-the-schema",[454],{"type":53,"value":455},"4. Set up the schema",{"type":44,"tag":45,"props":457,"children":458},{},[459],{"type":53,"value":460},"Manage schemas and migrations as code. Avoid running ad hoc schema migrations against your database, since they're hard to manage.",{"type":44,"tag":45,"props":462,"children":463},{},[464],{"type":53,"value":465},"If you're using an ORM, follow your ORM's best practices to manage schemas and migrations. For example, if using Drizzle, only use Drizzle for schema and migration management unless instructed otherwise.",{"type":44,"tag":149,"props":467,"children":469},{"id":468},"branching",[470],{"type":53,"value":471},"Branching",{"type":44,"tag":45,"props":473,"children":474},{},[475],{"type":53,"value":476},"Use this when the user is planning isolated environments, schema migration testing, preview deployments, or branch lifecycle automation.",{"type":44,"tag":45,"props":478,"children":479},{},[480],{"type":53,"value":481},"Key points:",{"type":44,"tag":363,"props":483,"children":484},{},[485,490,495],{"type":44,"tag":367,"props":486,"children":487},{},[488],{"type":53,"value":489},"Branches are instant, copy-on-write clones (no full data copy).",{"type":44,"tag":367,"props":491,"children":492},{},[493],{"type":53,"value":494},"Each branch has its own compute endpoint.",{"type":44,"tag":367,"props":496,"children":497},{},[498],{"type":53,"value":499},"Use the neon CLI or MCP server to create, inspect, and compare branches.",{"type":44,"tag":45,"props":501,"children":502},{},[503,505],{"type":53,"value":504},"Link: ",{"type":44,"tag":78,"props":506,"children":509},{"href":507,"rel":508},"https:\u002F\u002Fneon.com\u002Fdocs\u002Fintroduction\u002Fbranching.md",[82],[510],{"type":53,"value":507},{"type":44,"tag":45,"props":512,"children":513},{},[514,516,522,524,530],{"type":53,"value":515},"For detailed branch creation workflows (normal vs schema-only branches, reset-from-parent, CLI\u002FMCP selection), use the ",{"type":44,"tag":58,"props":517,"children":519},{"className":518},[],[520],{"type":53,"value":521},"neon-postgres-branches",{"type":53,"value":523}," skill. If it isn't installed, fetch it from ",{"type":44,"tag":78,"props":525,"children":528},{"href":526,"rel":527},"https:\u002F\u002Fneon.com\u002Fdocs\u002Fai\u002Fskills\u002Fneon-postgres-branches\u002FSKILL.md",[82],[529],{"type":53,"value":526},{"type":53,"value":86},{"type":44,"tag":88,"props":532,"children":534},{"className":90,"code":533,"language":92,"meta":93,"style":93},"npx skills add neondatabase\u002Fagent-skills --skill neon-postgres-branches\n",[535],{"type":44,"tag":58,"props":536,"children":537},{"__ignoreMap":93},[538],{"type":44,"tag":99,"props":539,"children":540},{"class":101,"line":102},[541,545,549,553,557,561],{"type":44,"tag":99,"props":542,"children":543},{"style":106},[544],{"type":53,"value":109},{"type":44,"tag":99,"props":546,"children":547},{"style":112},[548],{"type":53,"value":115},{"type":44,"tag":99,"props":550,"children":551},{"style":112},[552],{"type":53,"value":120},{"type":44,"tag":99,"props":554,"children":555},{"style":112},[556],{"type":53,"value":125},{"type":44,"tag":99,"props":558,"children":559},{"style":112},[560],{"type":53,"value":130},{"type":44,"tag":99,"props":562,"children":563},{"style":112},[564],{"type":53,"value":565}," neon-postgres-branches\n",{"type":44,"tag":149,"props":567,"children":569},{"id":568},"autoscaling",[570],{"type":53,"value":571},"Autoscaling",{"type":44,"tag":45,"props":573,"children":574},{},[575],{"type":53,"value":576},"Use this when the user needs compute to scale automatically with workload and wants guidance on CU sizing and runtime behavior.",{"type":44,"tag":45,"props":578,"children":579},{},[580,581],{"type":53,"value":504},{"type":44,"tag":78,"props":582,"children":585},{"href":583,"rel":584},"https:\u002F\u002Fneon.com\u002Fdocs\u002Fintroduction\u002Fautoscaling.md",[82],[586],{"type":53,"value":583},{"type":44,"tag":149,"props":588,"children":590},{"id":589},"scale-to-zero",[591],{"type":53,"value":592},"Scale to Zero",{"type":44,"tag":45,"props":594,"children":595},{},[596],{"type":53,"value":597},"Use this when optimizing idle costs and discussing suspend\u002Fresume behavior, including cold-start trade-offs.",{"type":44,"tag":45,"props":599,"children":600},{},[601],{"type":53,"value":481},{"type":44,"tag":363,"props":603,"children":604},{},[605,610,615],{"type":44,"tag":367,"props":606,"children":607},{},[608],{"type":53,"value":609},"Idle computes suspend automatically after a default of 5 minutes; the timeout is configurable, and suspension can only be disabled on the Launch and Scale plans.",{"type":44,"tag":367,"props":611,"children":612},{},[613],{"type":53,"value":614},"First query after suspend typically has a cold-start penalty (around hundreds of ms)",{"type":44,"tag":367,"props":616,"children":617},{},[618],{"type":53,"value":619},"Storage remains active while compute is suspended.",{"type":44,"tag":45,"props":621,"children":622},{},[623,624],{"type":53,"value":504},{"type":44,"tag":78,"props":625,"children":628},{"href":626,"rel":627},"https:\u002F\u002Fneon.com\u002Fdocs\u002Fintroduction\u002Fscale-to-zero.md",[82],[629],{"type":53,"value":626},{"type":44,"tag":149,"props":631,"children":633},{"id":632},"instant-restore",[634],{"type":53,"value":635},"Instant Restore",{"type":44,"tag":45,"props":637,"children":638},{},[639],{"type":53,"value":640},"Use this when the user needs point-in-time recovery or wants to restore data state without traditional backup restore workflows.",{"type":44,"tag":45,"props":642,"children":643},{},[644],{"type":53,"value":481},{"type":44,"tag":363,"props":646,"children":647},{},[648,653,658],{"type":44,"tag":367,"props":649,"children":650},{},[651],{"type":53,"value":652},"History windows for instant restore depend on plan limits.",{"type":44,"tag":367,"props":654,"children":655},{},[656],{"type":53,"value":657},"Users can create branches from historical points-in-time.",{"type":44,"tag":367,"props":659,"children":660},{},[661],{"type":53,"value":662},"Time Travel queries can be used for historical inspection workflows.",{"type":44,"tag":45,"props":664,"children":665},{},[666,667],{"type":53,"value":504},{"type":44,"tag":78,"props":668,"children":671},{"href":669,"rel":670},"https:\u002F\u002Fneon.com\u002Fdocs\u002Fintroduction\u002Fbranch-restore.md",[82],[672],{"type":53,"value":669},{"type":44,"tag":149,"props":674,"children":676},{"id":675},"read-replicas",[677],{"type":53,"value":678},"Read Replicas",{"type":44,"tag":45,"props":680,"children":681},{},[682],{"type":53,"value":683},"Use this for read-heavy workloads where the user needs dedicated read-only compute without duplicating storage.",{"type":44,"tag":45,"props":685,"children":686},{},[687],{"type":53,"value":481},{"type":44,"tag":363,"props":689,"children":690},{},[691,696,701],{"type":44,"tag":367,"props":692,"children":693},{},[694],{"type":53,"value":695},"Replicas are read-only compute endpoints sharing the same storage.",{"type":44,"tag":367,"props":697,"children":698},{},[699],{"type":53,"value":700},"Creation is fast and scaling is independent from primary compute.",{"type":44,"tag":367,"props":702,"children":703},{},[704],{"type":53,"value":705},"Typical use cases: analytics, reporting, and read-heavy APIs.",{"type":44,"tag":45,"props":707,"children":708},{},[709,710],{"type":53,"value":504},{"type":44,"tag":78,"props":711,"children":714},{"href":712,"rel":713},"https:\u002F\u002Fneon.com\u002Fdocs\u002Fintroduction\u002Fread-replicas.md",[82],[715],{"type":53,"value":712},{"type":44,"tag":149,"props":717,"children":719},{"id":718},"connection-pooling",[720],{"type":53,"value":721},"Connection Pooling",{"type":44,"tag":45,"props":723,"children":724},{},[725],{"type":53,"value":726},"Use this when the user is in serverless or high-concurrency environments and needs safe, scalable Postgres connection management.",{"type":44,"tag":45,"props":728,"children":729},{},[730],{"type":53,"value":481},{"type":44,"tag":363,"props":732,"children":733},{},[734,739,752],{"type":44,"tag":367,"props":735,"children":736},{},[737],{"type":53,"value":738},"Neon pooling uses PgBouncer.",{"type":44,"tag":367,"props":740,"children":741},{},[742,744,750],{"type":53,"value":743},"Add ",{"type":44,"tag":58,"props":745,"children":747},{"className":746},[],[748],{"type":53,"value":749},"-pooler",{"type":53,"value":751}," to endpoint hostnames to use pooled connections.",{"type":44,"tag":367,"props":753,"children":754},{},[755],{"type":53,"value":756},"Pooling is especially important in serverless runtimes with bursty concurrency.",{"type":44,"tag":45,"props":758,"children":759},{},[760,761],{"type":53,"value":504},{"type":44,"tag":78,"props":762,"children":765},{"href":763,"rel":764},"https:\u002F\u002Fneon.com\u002Fdocs\u002Fconnect\u002Fconnection-pooling.md",[82],[766],{"type":53,"value":763},{"type":44,"tag":149,"props":768,"children":770},{"id":769},"ip-allow-lists",[771],{"type":53,"value":772},"IP Allow Lists",{"type":44,"tag":45,"props":774,"children":775},{},[776],{"type":53,"value":777},"Use this when the user needs to restrict database access by trusted networks, IPs, or CIDR ranges.",{"type":44,"tag":45,"props":779,"children":780},{},[781,782],{"type":53,"value":504},{"type":44,"tag":78,"props":783,"children":786},{"href":784,"rel":785},"https:\u002F\u002Fneon.com\u002Fdocs\u002Fintroduction\u002Fip-allow.md",[82],[787],{"type":53,"value":784},{"type":44,"tag":149,"props":789,"children":791},{"id":790},"logical-replication",[792],{"type":53,"value":793},"Logical Replication",{"type":44,"tag":45,"props":795,"children":796},{},[797],{"type":53,"value":798},"Use this when integrating CDC pipelines, external Postgres sync, or replication-based data movement.",{"type":44,"tag":45,"props":800,"children":801},{},[802],{"type":53,"value":481},{"type":44,"tag":363,"props":804,"children":805},{},[806,811],{"type":44,"tag":367,"props":807,"children":808},{},[809],{"type":53,"value":810},"Neon supports native logical replication workflows.",{"type":44,"tag":367,"props":812,"children":813},{},[814],{"type":53,"value":815},"Useful for replicating to\u002Ffrom external Postgres systems.",{"type":44,"tag":45,"props":817,"children":818},{},[819,820],{"type":53,"value":504},{"type":44,"tag":78,"props":821,"children":824},{"href":822,"rel":823},"https:\u002F\u002Fneon.com\u002Fdocs\u002Fguides\u002Flogical-replication-guide.md",[82],[825],{"type":53,"value":822},{"type":44,"tag":827,"props":828,"children":829},"style",{},[830],{"type":53,"value":831},"html .light .shiki span {color: var(--shiki-light);background: var(--shiki-light-bg);font-style: var(--shiki-light-font-style);font-weight: var(--shiki-light-font-weight);text-decoration: var(--shiki-light-text-decoration);}html.light .shiki span {color: var(--shiki-light);background: var(--shiki-light-bg);font-style: var(--shiki-light-font-style);font-weight: var(--shiki-light-font-weight);text-decoration: var(--shiki-light-text-decoration);}html .default .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html .dark .shiki span {color: var(--shiki-dark);background: var(--shiki-dark-bg);font-style: var(--shiki-dark-font-style);font-weight: var(--shiki-dark-font-weight);text-decoration: var(--shiki-dark-text-decoration);}html.dark .shiki span {color: var(--shiki-dark);background: var(--shiki-dark-bg);font-style: var(--shiki-dark-font-style);font-weight: var(--shiki-dark-font-weight);text-decoration: var(--shiki-dark-text-decoration);}",{"items":833,"total":102},[834],{"slug":4,"name":4,"fn":5,"description":6,"org":835,"tags":836,"stars":24,"repoUrl":25,"updatedAt":26},{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[837,838,839,840],{"name":16,"slug":17,"type":14},{"name":9,"slug":8,"type":14},{"name":19,"slug":20,"type":14},{"name":22,"slug":23,"type":14},{"items":842,"total":1012},[843,850,864,876,891,904,918,933,945,964,982,999],{"slug":4,"name":4,"fn":5,"description":6,"org":844,"tags":845,"stars":24,"repoUrl":25,"updatedAt":26},{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[846,847,848,849],{"name":16,"slug":17,"type":14},{"name":9,"slug":8,"type":14},{"name":19,"slug":20,"type":14},{"name":22,"slug":23,"type":14},{"slug":851,"name":851,"fn":852,"description":853,"org":854,"tags":855,"stars":861,"repoUrl":862,"updatedAt":863},"add-neon-docs","add Neon docs to project AI docs","Use this skill when the user asks to add documentation, add docs, add references, or install documentation about Neon. Adds Neon best practices reference links to project AI documentation (CLAUDE.md, AGENTS.md, or Cursor rules). Does not install packages or modify code.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[856,857,860],{"name":16,"slug":17,"type":14},{"name":858,"slug":859,"type":14},"Documentation","documentation",{"name":9,"slug":8,"type":14},86,"https:\u002F\u002Fgithub.com\u002Fneondatabase\u002Fai-rules","2026-04-06T18:38:53.722898",{"slug":865,"name":865,"fn":866,"description":867,"org":868,"tags":869,"stars":861,"repoUrl":862,"updatedAt":875},"neon-auth","set up Neon Auth for apps","Sets up Neon Auth for your application. Configures authentication, creates auth routes, and generates UI components. Use when adding authentication to Next.js, React SPA, or Node.js projects.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[870,873,874],{"name":871,"slug":872,"type":14},"Auth","auth",{"name":16,"slug":17,"type":14},{"name":9,"slug":8,"type":14},"2026-04-06T18:38:52.386193",{"slug":877,"name":877,"fn":878,"description":879,"org":880,"tags":881,"stars":861,"repoUrl":862,"updatedAt":890},"neon-drizzle","set up Drizzle ORM with Neon","Creates a fully functional Drizzle ORM setup with a provisioned Neon database. Installs dependencies, provisions database credentials, configures connections, generates schemas, and runs migrations. Results in working code that can immediately connect to and query the database. Use when creating new projects with Drizzle, adding ORM to existing applications, or modifying database schemas.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[882,883,885,886,889],{"name":16,"slug":17,"type":14},{"name":346,"slug":884,"type":14},"drizzle",{"name":9,"slug":8,"type":14},{"name":887,"slug":888,"type":14},"ORM","orm",{"name":19,"slug":20,"type":14},"2026-04-06T18:38:56.217495",{"slug":892,"name":892,"fn":893,"description":894,"org":895,"tags":896,"stars":861,"repoUrl":862,"updatedAt":903},"neon-js","set up the Neon JS SDK for auth and queries","Sets up the full Neon JS SDK with unified auth and PostgREST-style database queries. Configures auth client, data client, and type generation. Use when building apps that need both authentication and database access in one SDK.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[897,898,899,900],{"name":871,"slug":872,"type":14},{"name":16,"slug":17,"type":14},{"name":9,"slug":8,"type":14},{"name":901,"slug":902,"type":14},"TypeScript","typescript","2026-04-06T18:38:51.116041",{"slug":905,"name":905,"fn":906,"description":907,"org":908,"tags":909,"stars":861,"repoUrl":862,"updatedAt":917},"neon-serverless","configure Neon serverless driver","Configures Neon Serverless Driver for Next.js, Vercel Edge Functions, AWS Lambda, and other serverless environments. Installs @neondatabase\u002Fserverless, sets up environment variables, and creates working API route examples with TypeScript types. Use when users need to connect their application to Neon, fetch or query data from a Neon database, integrate Neon with Next.js or serverless frameworks, or set up database access in edge\u002Fserverless environments where traditional PostgreSQL clients don't work.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[910,911,914,915,916],{"name":16,"slug":17,"type":14},{"name":912,"slug":913,"type":14},"Edge Functions","edge-functions",{"name":9,"slug":8,"type":14},{"name":19,"slug":20,"type":14},{"name":22,"slug":23,"type":14},"2026-04-06T18:38:54.97085",{"slug":919,"name":919,"fn":920,"description":921,"org":922,"tags":923,"stars":861,"repoUrl":862,"updatedAt":932},"neon-toolkit","create ephemeral Neon databases for testing","Creates and manages ephemeral Neon databases for testing, CI\u002FCD pipelines, and isolated development environments. Use when building temporary databases for automated tests or rapid prototyping.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[924,927,928,929],{"name":925,"slug":926,"type":14},"CI\u002FCD","cicd",{"name":16,"slug":17,"type":14},{"name":9,"slug":8,"type":14},{"name":930,"slug":931,"type":14},"Testing","testing","2026-04-06T18:38:57.490782",{"slug":934,"name":934,"fn":935,"description":936,"org":937,"tags":938,"stars":942,"repoUrl":943,"updatedAt":944},"claimable-postgres","provision temporary Postgres databases","Provision instant temporary Postgres databases via Claimable Postgres by Neon (neon.new) with no login, signup, or credit card. Supports REST API, CLI, and SDK. Use when users ask for a quick Postgres environment, a throwaway DATABASE_URL for prototyping\u002Ftests, or \"just give me a DB now\". Triggers include: \"quick postgres\", \"temporary postgres\", \"no signup database\", \"no credit card database\", \"instant DATABASE_URL\", \"npx neon-new\", \"neon.new\", \"neon.new API\", \"claimable postgres API\".",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[939,940,941],{"name":16,"slug":17,"type":14},{"name":9,"slug":8,"type":14},{"name":19,"slug":20,"type":14},81,"https:\u002F\u002Fgithub.com\u002Fneondatabase\u002Fagent-skills","2026-07-27T06:07:56.160588",{"slug":8,"name":8,"fn":946,"description":947,"org":948,"tags":949,"stars":942,"repoUrl":943,"updatedAt":963},"build applications on the Neon platform","Overview of the Neon platform for apps and agents, spanning Postgres, Auth, the Data API, Object Storage, Compute Functions, and the AI Gateway. Start here to route to the right Neon skill, set up the CLI or MCP server, and follow the branch-first workflow. Use when \"Neon\" is mentioned, or when any of its individual capabilities are the trigger: \"object storage\" or \"S3\", \"buckets\", \"serverless functions\", \"AI gateway\", \"call an LLM\", \"postgres\", \"database\", or \"backend\".",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[950,953,956,957,958,959,960],{"name":951,"slug":952,"type":14},"AI Infrastructure","ai-infrastructure",{"name":954,"slug":955,"type":14},"Authentication","authentication",{"name":16,"slug":17,"type":14},{"name":9,"slug":8,"type":14},{"name":19,"slug":20,"type":14},{"name":22,"slug":23,"type":14},{"name":961,"slug":962,"type":14},"Storage","storage","2026-07-27T06:08:01.383115",{"slug":965,"name":965,"fn":966,"description":967,"org":968,"tags":969,"stars":942,"repoUrl":943,"updatedAt":981},"neon-ai-gateway","call LLMs via Neon AI Gateway","One API and one credential for frontier and open-source LLMs, built into your Neon branch and powered by Databricks. Use when a user wants to call an LLM, add AI\u002Fchat\u002Fan agent to their app, route between model providers (OpenAI, Anthropic, Google\u002FGemini, Meta, Alibaba, DeepSeek), or avoid juggling separate provider API keys and accounts — especially when they already use Neon and want AI requests to branch with their project. Works with the OpenAI SDK, Anthropic SDK, google-genai, the Vercel AI SDK, and Mastra by changing only the base URL. Triggers include \"call an LLM\", \"add AI to my app\", \"chat completion\", \"model routing\", \"LLM proxy\u002Fgateway\", \"one API for all models\", \"use Claude\u002FGPT\u002FGemini\", \"AI SDK\", \"Mastra agent\", \"Neon AI Gateway\", and \"log\u002Frate-limit AI calls\".",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[970,971,974,977,980],{"name":951,"slug":952,"type":14},{"name":972,"slug":973,"type":14},"API Development","api-development",{"name":975,"slug":976,"type":14},"Databricks","databricks",{"name":978,"slug":979,"type":14},"LLM","llm",{"name":9,"slug":8,"type":14},"2026-07-27T06:08:00.288175",{"slug":983,"name":983,"fn":984,"description":985,"org":986,"tags":987,"stars":942,"repoUrl":943,"updatedAt":998},"neon-functions","deploy serverless functions on Neon","Long-running, serverless Node.js HTTP functions deployed onto your Neon branch, with DATABASE_URL injected automatically and compute that runs next to your data. Use when a user wants to host an API, an AI agent with long streaming responses, a WebSocket or server-sent-events (SSE) server, a webhook handler, a Discord bot, an MCP server, or any request\u002Fresponse workload that risks timing out on short, lambda-style serverless functions — and wants it to branch with their database. Triggers include \"serverless function\", \"deploy an API\", \"long-running function\", \"streaming agent\", \"SSE server\", \"WebSocket server\", \"webhook handler\", \"MCP server\", \"run code next to my database\", \"function that won't time out\", \"Neon Functions\", and \"Neon Compute\".",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[988,989,992,993,994,997],{"name":972,"slug":973,"type":14},{"name":990,"slug":991,"type":14},"Backend","backend",{"name":912,"slug":913,"type":14},{"name":9,"slug":8,"type":14},{"name":995,"slug":996,"type":14},"Node.js","node-js",{"name":22,"slug":23,"type":14},"2026-07-27T06:07:59.147675",{"slug":1000,"name":1000,"fn":1001,"description":1002,"org":1003,"tags":1004,"stars":942,"repoUrl":943,"updatedAt":1011},"neon-object-storage","manage Neon object storage","S3-compatible object storage that branches with your Neon project, so files and the database stay in sync across every branch. Use when a user wants object storage, a bucket, blob\u002Ffile storage, or somewhere to put uploads, images, documents, avatars, or user-generated files for their app or agent — especially when they already use (or are setting up) Neon Postgres and don't want to add a separate storage provider like AWS S3, Cloudflare R2, or Supabase Storage. Triggers include \"object storage\", \"bucket\", \"blob storage\", \"file storage\", \"store uploads\u002Fimages\u002Ffiles\", \"S3-compatible storage\", \"presigned URL\", \"where do I put files\", \"Neon Object Storage\", \"Neon Storage\", and \"storage that branches with my database\".",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[1005,1006,1009,1010],{"name":16,"slug":17,"type":14},{"name":1007,"slug":1008,"type":14},"File Storage","file-storage",{"name":9,"slug":8,"type":14},{"name":961,"slug":962,"type":14},"2026-07-27T06:07:57.150892",19]