If you're running a side project on Vercel's free tier with Neon as your database backend, watch those compute quotas carefully—or you might wake up to unexpected billing alerts. That's exactly what happened to developer zaerohell, who recently shared their experience removing a nightly cron job from their vercel.json configuration to avoid exceeding Neon's free-tier limits.

The Problem: A Nightly Sync Pushing Against Compute Ceilings

The setup was straightforward: an automated /api/cron/sync endpoint configured in vercel.json that ran on a nightly schedule. While cron jobs are technically supported on Vercel's hobby tier, the real trouble came from Neon's side—the database's free-tier compute allocation has strict limits on execution time and connection hours. Each cron invocation meant another hit against that quota, and over time, the math stopped working in zaerohell's favor.

The Fix: Stripping Out vercel.json Configuration

The solution was surgical but effective: remove the cron definition from vercel.json entirely. This eliminated the scheduled execution without touching application code or requiring a full deployment freeze. Zaerohell documented that this single change kept the project lightweight and prevented what could have been a service interruption or surprise invoice when Neon cut off compute access.

Why Free-Tier Compute Quotas Matter More Than You Think

Neon's free tier offers 0.5 ACU (Aurora Computing Unit) of serverless compute, which sounds generous until you factor in connection pooling overhead and regular cron triggers. For hobby projects with inconsistent traffic patterns, these quotas can fill up fast—especially if you're syncing data from external APIs or running background jobs that hold connections open longer than expected.

Key Takeaways

  • Audit your vercel.json for any scheduled functions before deploying to production
  • Monitor Neon's console for compute usage warnings—don't wait for the cutoff email
  • If you need cron functionality, consider offloading it to a separate service like GitHub Actions or a lightweight worker
  • Database connection pooling (Neon supports PgBouncer) can help reduce compute overhead per request

The Bottom Line

Free tiers aren't truly free when you're not paying attention. Zaerohell's quick fix underscores something we all know but often forget: infrastructure boundaries exist, and side projects that seem harmless can quickly become billing landmines. Read your quotas, set alerts, and for God's sake, document your cron jobs before they document themselves in your next invoice.