Missing rate limiting on branch creation enables runaway workloads

8/10 High

Neon lacked strong limits on the number of branches per project and per customer. Agentic AI systems creating thousands of branches as 'savepoints' overwhelmed the control plane metadata handling system. The absence of rate limiting at test boundaries allowed production workloads to diverge significantly from tested scenarios.

Neon
Category
config
Workaround
none
Stage
deploy
Freshness
persistent
Scope
single_lib
Upstream
open
Recurring
No
Buyer Type
enterprise
Maintainer
active

Sources

Collection History

Query: “What are the most common pain points with Neon for developers in 2025?”4/6/2026

It would have continued to function well if we had stronger limits on the number of branches both per project and per customer. One lesson here is that we need stronger limits on EVERY dimension of the workload. Rate limiting at or before our test boundaries would have saved the day.

Created: 4/6/2026Updated: 4/6/2026