> This page location: Connect to Neon > Choosing your connection method > Full Neon documentation index: https://neon.com/docs/llms.txt # Choosing your connection method Find the right driver and connection type for your deployment platform Your connection method depends on where your code runs. Use the table below for a quick lookup, or read the scenario sections for detailed guidance. ## Quick reference by environment Each scenario is [described in detail](https://neon.com/docs/connect/choose-connection#find-your-scenario) further down the page. | Environment | Recommended driver | Pooling | Guide | | ---------------------------------------------------------------------------------------------------------------------------------- | -------------------------- | ------------------------------------------------------------------------------- | ----------------------------------------------------------------------- | | [Any platform (non-JS/TS)](https://neon.com/docs/connect/choose-connection#not-using-javascript-or-typescript) | Native Postgres driver | [Neon pooled connection](https://neon.com/docs/connect/connection-pooling) | [Language guides](https://neon.com/docs/get-started/languages) | | [Railway / Render / VPS / Docker](https://neon.com/docs/connect/choose-connection#running-on-a-long-lived-server-jsts) | `pg` or `postgres.js` | Client-side or [Neon pooling](https://neon.com/docs/connect/connection-pooling) | [Framework guides](https://neon.com/docs/get-started/frameworks) | | [Vercel (Fluid)](https://neon.com/docs/connect/choose-connection#deploying-to-vercel-or-cloudflare-with-platform-pooling) | `pg` (node-postgres) | [`@vercel/functions`](https://www.npmjs.com/package/@vercel/functions) | [Vercel guide](https://neon.com/docs/guides/vercel-connection-methods) | | [Cloudflare + Hyperdrive](https://neon.com/docs/connect/choose-connection#deploying-to-vercel-or-cloudflare-with-platform-pooling) | `pg` (node-postgres) | [Hyperdrive](https://developers.cloudflare.com/hyperdrive/) | [Hyperdrive guide](https://neon.com/docs/guides/cloudflare-hyperdrive) | | [Cloudflare Workers](https://neon.com/docs/connect/choose-connection#deploying-to-another-serverless-or-edge-platform) | `@neondatabase/serverless` | N/A | [Serverless driver](https://neon.com/docs/serverless/serverless-driver) | | [Netlify / Deno Deploy](https://neon.com/docs/connect/choose-connection#deploying-to-another-serverless-or-edge-platform) | `@neondatabase/serverless` | N/A | [Serverless driver](https://neon.com/docs/serverless/serverless-driver) | | [Client-side (browser)](https://neon.com/docs/connect/choose-connection#building-a-client-side-app-without-a-backend) | `@neondatabase/neon-js` | N/A | [Data API](https://neon.com/docs/data-api/overview) | ## Find your scenario ### Not using JavaScript or TypeScript? Use a standard TCP-based Postgres driver with a [pooled connection](https://neon.com/docs/connect/connection-pooling). Connect from a secure backend server using your language's native driver. | Language/Framework | Guide | | ------------------- | ----------------------------------------------------------- | | Django (Python) | [Django](https://neon.com/docs/guides/django) | | SQLAlchemy (Python) | [SQLAlchemy](https://neon.com/docs/guides/sqlalchemy) | | Elixir Ecto | [Elixir Ecto](https://neon.com/docs/guides/elixir-ecto) | | Laravel (PHP) | [Laravel](https://neon.com/docs/guides/laravel) | | Ruby on Rails | [Ruby on Rails](https://neon.com/docs/guides/ruby-on-rails) | | Go | [Go](https://neon.com/docs/guides/go) | | Rust | [Rust](https://neon.com/docs/guides/rust) | | Java | [Java](https://neon.com/docs/guides/java) | For the full list, see [Language quickstarts](https://neon.com/docs/get-started/languages). ### Running on a long-lived server (JS/TS)? If you deploy a JavaScript or TypeScript app to Railway, Render, a VPS, Docker, or any self-hosted environment with persistent processes, use a standard TCP driver with [connection pooling](https://neon.com/docs/connect/connection-pooling). Your server can maintain a connection pool across requests, making TCP the fastest and most efficient option. Recommended drivers: [`pg` (node-postgres)](https://node-postgres.com/), [`postgres.js`](https://github.com/porsager/postgres), or [`Bun.SQL`](https://bun.com/docs/runtime/sql#postgresql). ### Deploying to Vercel or Cloudflare with platform pooling? These platforms provide their own connection pooling, which makes standard TCP the best choice. **Vercel (Fluid compute):** Use `pg` (node-postgres) with [`@vercel/functions`](https://www.npmjs.com/package/@vercel/functions). Vercel Fluid keeps functions warm long enough to reuse TCP connections, so you skip the connection setup cost on subsequent requests. See the [Vercel connection methods guide](https://neon.com/docs/guides/vercel-connection-methods) for details. **Cloudflare (Hyperdrive):** Use `pg` (node-postgres) with [Hyperdrive](https://developers.cloudflare.com/hyperdrive/), which provides connection pooling for Workers. See the [Cloudflare Hyperdrive guide](https://neon.com/docs/guides/cloudflare-hyperdrive) for setup. ### Deploying to another serverless or edge platform? For platforms like Netlify Functions, Deno Deploy, or Cloudflare Workers (without Hyperdrive), use the [Neon serverless driver](https://neon.com/docs/serverless/serverless-driver) (`@neondatabase/serverless`). It connects over HTTP or WebSockets instead of TCP, reducing connection setup latency. Choose your transport based on your query pattern: use **HTTP** for single queries and non-interactive transactions, or **WebSocket** for interactive transactions and `node-postgres` compatibility. See [HTTP vs. WebSocket](https://neon.com/docs/connect/choose-connection#http-vs-websocket-serverless-driver) for details. ### Building a client-side app without a backend? Use the [Neon Data API](https://neon.com/docs/data-api/overview) via [`@neondatabase/neon-js`](https://www.npmjs.com/package/@neondatabase/neon-js). Browsers cannot open TCP connections to Postgres, so the Data API provides a secure HTTP interface with Row-Level Security support. **Note:** The Data API is currently in beta. See the [JavaScript SDK reference](https://neon.com/docs/reference/javascript-sdk) for full documentation. ## Understanding the options ### Pooled vs. direct connections A **pooled connection** routes traffic through PgBouncer, which manages a pool of reusable Postgres connections. Use pooled connections by default. They handle up to 10,000 concurrent client connections and work well for serverless apps and high-concurrency workloads. A **direct connection** connects straight to Postgres without PgBouncer. Use direct connections for operations that require stable, long-lived connections or features PgBouncer does not support, such as: - Schema migrations (Prisma Migrate, Drizzle Kit, django-admin migrate) - `CREATE INDEX CONCURRENTLY` - `LISTEN` / `NOTIFY` - Temporary tables or prepared statements across multiple queries Direct connections are limited by `max_connections`, which ranges from about 100 to 4,000 depending on your [compute size](https://neon.com/docs/reference/compatibility#parameter-settings-that-differ-by-compute-size). You select pooled or direct by choosing the right connection string. Pooled strings include `-pooler` in the hostname: ```text # Pooled postgresql://user:pass@ep-cool-rain-123456-pooler.us-east-2.aws.neon.tech/neondb?sslmode=require&channel_binding=require # Direct postgresql://user:pass@ep-cool-rain-123456.us-east-2.aws.neon.tech/neondb?sslmode=require&channel_binding=require ``` See [Connection pooling](https://neon.com/docs/connect/connection-pooling) for details. ### HTTP vs. WebSocket (serverless driver) The [Neon serverless driver](https://neon.com/docs/serverless/serverless-driver) supports two transports: - **HTTP** uses `fetch` requests. It is faster for single queries (~3 round trips vs. ~8 for TCP) and supports non-interactive transactions. Choose HTTP when your queries are independent, one-shot operations. - **WebSocket** maintains a persistent connection within a request. It supports interactive transactions and is compatible with the `node-postgres` API (`Pool`, `Client`). Choose WebSocket when you need multi-step transactions or `pg` compatibility. ### Data API The [Data API](https://neon.com/docs/data-api/overview) provides a REST interface to your database over HTTP. It works in browsers, edge runtimes, and anywhere you can make HTTP requests. It validates JWTs from any authentication provider and enforces PostgreSQL [Row-Level Security](https://neon.com/docs/guides/row-level-security), making it suitable for client-side apps that query the database directly. ## ORM compatibility Popular JavaScript and TypeScript ORMs work with Neon across all connection methods. For non-JS/TS ORMs (Django, SQLAlchemy, ActiveRecord, Ecto), use your language's native Postgres driver with a [pooled connection](https://neon.com/docs/connect/choose-connection#pooled-vs-direct-connections). | ORM | Supported drivers | Guide | | ------- | ----------------------------------------------- | ----------------------------------------------------- | | Drizzle | `pg`, `postgres.js`, `@neondatabase/serverless` | [Drizzle guide](https://neon.com/docs/guides/drizzle) | | Kysely | `pg`, `postgres.js`, `@neondatabase/serverless` | [Kysely guide](https://neon.com/docs/guides/kysely) | | Prisma | `pg`, `@neondatabase/serverless` | [Prisma guide](https://neon.com/docs/guides/prisma) | | TypeORM | `pg` | [TypeORM guide](https://neon.com/docs/guides/typeorm) | Choose the driver based on your platform (see the scenarios above), then configure your ORM to use it. ## Common pitfalls | Issue | Description | | -------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Double pooling | **Neon-side pooling** uses PgBouncer to manage connections between your app and Postgres. **Client-side pooling** occurs within your driver before connections reach PgBouncer.

If you use a pooled Neon connection, avoid adding client-side pooling on top. Let Neon handle it. If you must use client-side pooling, release connections back to the pool promptly to avoid conflicts with PgBouncer. | | Understanding limits | `max_connections` is the maximum number of concurrent Postgres connections, determined by your [compute size](https://neon.com/docs/connect/connection-pooling#connection-limits-without-connection-pooling). `default_pool_size` is the maximum number of backend connections PgBouncer maintains per user/database pair.

Increasing your compute to raise `max_connections` may not help if `default_pool_size` is the bottleneck. To increase `default_pool_size`, contact [Support](https://neon.com/docs/introduction/support). | | Use request handlers | In serverless environments (Vercel Edge Functions, Cloudflare Workers), WebSocket connections cannot outlive a single request. Create, use, and close `Pool` or `Client` objects **within the same request handler**. Do not create them outside a handler or reuse them across handlers. See [Pool and Client](https://github.com/neondatabase/serverless?tab=readme-ov-file#pool-and-client) for details. | --- ## Related docs (Connect to Neon) - [Connect to Neon](https://neon.com/docs/connect/connect-intro) - [Connect from any app](https://neon.com/docs/connect/connect-from-any-app) - [Neon serverless driver](https://neon.com/docs/serverless/serverless-driver) - [Neon SQL Editor](https://neon.com/docs/get-started/query-with-neon-sql-editor) - [Passwordless auth](https://neon.com/docs/connect/passwordless-connect) - [Securing connections](https://neon.com/docs/connect/connect-securely) - [Connection pooling](https://neon.com/docs/connect/connection-pooling) - [Latency benchmarks](https://neon.com/docs/guides/benchmarking-latency)