Neon
Security & compliance
Cost
Stability
Releases
Code quality
Performance
Cost & ops health
Live Neon consumption, retention, and access posture.
Overview
Reads the Neon control plane for what your project is actually consuming and how it is exposed: compute hours, storage growth, branch sprawl, failed operations, PITR retention, spend quotas, and IP access rules.
What it looks for
- Compute running continuously with no scale-to-zero
- Storage growth from orphaned or expired branches, and non-primary branches outgrowing primary
- PITR retention under a day, or under seven days in production
- No spend quota on a paid project
- Connections accepted from any IP, or an allow-list not scoped to protected branches
- Repeated migration failures, elevated failed-operation ratios, end-of-life Postgres versions
Why it matters
Branch sprawl is the quiet Neon cost — preview branches accumulate compute and storage long after the PR merged, and no single one looks expensive. Meanwhile PITR under a day and no spend quota are the two settings you find out about on the worst possible day.
Rules in this check
How the fixes arrive
GuideChanges only you can make safely arrive as a step-by-step guide you can follow yourself or hand to your coding agent.
Run them all on your app
Connect your repo and your live services with read-only scopes. The first scan is free, and nothing changes without your approval.