The latest articles on DEV Community by ARITRA SARKAR (@aritrasarkar). https://dev.to/aritrasarkar https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F1048198%2F8c8a1fb7-63e5-40b2-9f7c-21add3964b8d.png https://dev.to/aritrasarkar en ARITRA SARKAR Tue, 30 Jun 2026 03:35:49 +0000 https://dev.to/aritrasarkar/my-serverless-database-was-billing-me-like-it-never-slept-ffc https://dev.to/aritrasarkar/my-serverless-database-was-billing-me-like-it-never-slept-ffc <p>My "serverless" database was billing me like it never slept.</p> <p>Neon has this great feature called scale-to-zero. Your Postgres compute suspends when it's idle, so you only pay for the queries you actually run. For a pre-revenue product, that should cost a few cents a month.</p> <p>Mine ran 24/7. The compute never once scaled to zero.</p> <p>The culprit wasn't my app logic. It was my database driver.</p> <p>I was using postgres-js, which holds a persistent connection open to the database. From Neon's side, an open connection looks like activity, so it never suspended. It just stayed awake and kept quietly billing me.</p> <p>The fix was basically one conceptual change: switch to @neondatabase/serverless, the HTTP driver.</p> <p>Instead of a long-lived connection, every query becomes a stateless one-shot HTTP request. The query fires, the connection closes, and the compute is free to suspend.</p> <p>Scale-to-zero finally worked.</p> <p>The lesson I keep relearning as a solo founder: "serverless" is a property of your whole stack, not a checkbox on one service. One persistent connection upstream and the whole cost model breaks.</p> neondb postgres serverless infrastructure