Neon · Class

PrismaNeon

PrismaNeon is Neon’s Prisma driver adapter for serverless applications. Construct it with a Neon connection string and pass it to PrismaClient.

How it works

PrismaNeon adapts Neon’s serverless driver for Prisma Client. Construct it with the application connection string, then pass the adapter into PrismaClient so queries use Neon’s serverless-compatible connection path.

Syntax

new PrismaNeon({ connectionString: process.env.DATABASE_URL })

Parameters

Name	Type	Description
`options`	`object`	Options object containing the Neon connection string.
`options.connectionString`	`string`	Neon PostgreSQL connection URL used by the adapter.

Returns

A PrismaNeon adapter instance for use with PrismaClient.

Key points

The documented Prisma integration uses @prisma/adapter-neon as the recommended adapter.
Use the pooled endpoint, recognizable by -pooler in its hostname, for application traffic.
Reserve the direct endpoint for Prisma CLI tasks including migrations and introspection.
Current Prisma setup places CLI connection configuration in prisma.config.ts.
Install the Prisma client, Neon adapter, and dotenv packages for the documented setup.

Common mistakes

Use the pooled application URL for runtime queries rather than the direct URL intended for Prisma CLI operations.
Prisma CLI schema operations such as migrations need the unpooled connection string.

Example: Prisma Client with PrismaNeon

import 'dotenv/config';
import { PrismaNeon } from '@prisma/adapter-neon';
import { PrismaClient } from './generated/prisma/client';

const adapter = new PrismaNeon({
  connectionString: process.env.DATABASE_URL
});
const prisma = new PrismaClient({ adapter });

const posts = await prisma.post.findMany();
console.log(posts);

Creates Prisma Client with the Neon serverless driver adapter and queries posts.

When to use it

Run Prisma queries through Neon’s serverless driver

Serverless Node.js or TypeScript application

Use a pooled Neon endpoint for runtime database access

Prisma application deployment

Use a direct Neon endpoint for Prisma CLI migrations and introspection

Schema management

Interview questions

QWhat does PrismaNeon do?

PrismaNeon is the Prisma driver adapter for connecting Prisma ORM to Neon through the Neon serverless driver. Instantiate it with a connection string and provide it to PrismaClient.

Follow-up: Why should the application and Prisma CLI use different URLs? The application uses a pooled endpoint for runtime connections, while migrations and other schema operations require a direct endpoint.

QHow do you initialize Prisma Client with Neon?

Create PrismaNeon with the pooled DATABASE_URL, then pass the resulting adapter to PrismaClient. This lets application queries run through Neon’s serverless-compatible connection mechanism.

Follow-up: What must be configured for migrations? Supply DATABASE_URL_UNPOOLED as the direct connection in Prisma’s CLI configuration.

QWhich Neon connection strings are needed?

The application should use the pooled hostname containing the -pooler suffix. Prisma CLI commands such as migrations and introspection should use the direct, unpooled URL.

Follow-up: What problem does this separation avoid? It keeps schema-changing commands from going through the pooled connection layer.

@prisma/adapter-neon
@prisma/client
Prisma Client
Prisma Migrate
Neon serverless driver
DATABASE_URL
DATABASE_URL_UNPOOLED
prisma.config.ts

Source: Connect from Prisma to Neon - Neon Docs. Checked 2026-10-16.