Hyperdrive is Cloudflare's managed connection-pooler for Postgres databases. It sits between a Workers / OpenNext deployment and the upstream Postgres instance, holding a warm pool of TCP connections to the database and short-cutting the TLS / SCRAM handshake cost per request.
iso-compliant's Workers runtime uses Hyperdrive to talk to the upstream Supabase Postgres. The hot path is the per-request API-key signing-key lookup at apps/api/src/lib/signing-key.ts and the tenant resolver at apps/api/src/lib/tenant.ts. Without Hyperdrive, each Worker invocation would pay 50–200ms of TLS handshake to Supabase; with Hyperdrive, the same lookup completes in 5–20ms p50.
The architectural caveat: Hyperdrive caches connections by *worker invocation context*, not globally. A new Worker isolate cold-starts a fresh Hyperdrive client, so cold-start latency is bounded by the upstream cold pool warmup.
The wrangler.jsonc binding for Hyperdrive is at the project root.