## TL;DR

drizzle-orm/neon-http (backed by the neon() fetch client) is the default in every serverless tutorial, and it is right for Vercel/Netlify one-shot queries. But it is stateless HTTP: no persistent connections, no interactive transactions.

## Steps

1. - Serverless one-shot queries -> `drizzle-orm/neon-http` with `neon(process.env.DATABASE_URL)`.
- Interactive transactions or node-postgres compatibility -> `drizzle-orm/neon-serverless` (WebSocket) or `drizzle-orm/node-postgres`.
- Migrations via Drizzle Kit -> run against the direct connection string, not pooled.

```ts
// HTTP: serverless one-shots
import { drizzle } from 'drizzle-orm/neon-http';
import { neon } from '@neondatabase/serverless';
const db = drizzle(neon(process.env.DATABASE_URL));

// WebSocket: interactive transactions
import { drizzle } from 'drizzle-orm/neon-serverless';
import { Pool, neonConfig } from '@neondatabase/serverless';
import ws from 'ws';
neonConfig.webSocketConstructor = ws; // Node.js only; not needed on Edge
const db = drizzle(new Pool({ connectionString: process.env.DATABASE_URL }));
```

## When to use

You are seeing this: drizzle-orm/neon-http (backed by the neon() fetch client) is the default in every serverless tutorial, and it is right for Vercel/Netlify one-shot queries. Use this skill when you run into "Drizzle + Neon: neon-http for serverless one-shots, neon-ws for transactions".

## When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

## Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

## Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.
