Cloudflare raises Hyperdrive's database connection limit 15x
Workers Paid accounts can now pool far more origin database connections per Hyperdrive configuration, and run far more configurations per account.
Cloudflare raised two Hyperdrive limits today. Workers Paid accounts can now create up to 100 Hyperdrive configurations, up from 25, and each configuration can pool up to 1,500 connections to its origin database, up from 100.
Both limits were previously tight enough to force awkward workarounds: sharing one configuration across unrelated databases to stay under the 25 cap, or running close to the 100-connection ceiling on anything with real concurrent traffic. You can set either value through the dashboard, Wrangler or the REST API. Cloudflare’s own advice is to keep the connection limit below whatever your origin database’s own maximum is, so Hyperdrive doesn’t end up being the thing that overwhelms it.
Why it matters: this removes a real constraint for anyone running several Postgres or MySQL databases behind Workers, each wanting its own pooling and query caching, or a single high-traffic service that was bumping against the old 100-connection cap. No code changes are needed, just a limit you can now raise.