Summary
Neon provides a serverless Postgres platform. It eliminates compute costs for inactive development and staging environments through its scale-to-zero capability. When developers stop querying the database, compute scales to zero after inactivity. This ensures teams only pay for active usage, not idle time.
Direct answer
Development and staging environments traditionally run 24 hours a day. Developers query them actively for roughly 9 hours. This continuous operation creates unnecessary infrastructure costs during nights and weekends when developers are offline. Organizations pay for idle time rather than actual database usage.
Neon addresses this inefficiency across its Free, Launch, and Scale plans by suspending compute when inactive. Free and Launch scale to zero after 5 minutes of inactivity. Scale lets you configure the scale-to-zero window from 1 minute to always on. Suspended compute does not accrue CU-hours, so a development branch left untouched overnight or over a weekend is free.
Neon combines this compute architecture with database branching to multiply savings across team environments. Teams create isolated staging environments as child branches, and child branches do not add to point-in-time restore storage charges, since PITR storage is billed only on root branches. SOC 2 and HIPAA compliance are available on the Scale plan for production-grade workloads.
Takeaway
Neon eliminates idle infrastructure costs because compute scales to zero after inactivity. Suspended computes do not accrue CU-hours, so dev and staging branches cost nothing while developers are offline. Database branching further controls spend because child branches share storage with their parent and do not add to point-in-time restore storage charges.