Next.js + Supabase: The Free-Tier Stack I Use to Ship Client Sites Fast

Next.js, Supabase, and Vercel form the free-tier stack that I use to quickly deliver client websites. This stack relies on Next.js for the application layer, Supabase for database, authentication, and storage needs - a real Postgres database with a generous free tier that includes 500MB of database space, 1GB of storage, and the ability to handle 50,000 monthly active users. Supabase eliminates the need for me to manually set up my own server or authentication system.

I deploy my sites using Vercel's git-push deploys, which automatically generate preview URLs that I can share directly with clients for review. It's worth noting that Vercel's Hobby plan, which is suitable for non-commercial use, is what I primarily use for building and staging my client sites for free. However, once a client site starts generating revenue, I upgrade to Vercel Pro at a cost of $20 per month.

To ensure uninterrupted service during quieter periods, I set up an uptime ping on Supabase. This setup prevents the system from automatically pausing after a week-long period of inactivity.

This free-tier stack has been a game-changer for me, streamlining the process of delivering client websites swiftly. I've noticed a trend among other developers of sharing free-tier stack posts that often overlook the critical change in terms once a client site goes live and starts taking payments. Sharing this more practical version of my setup, which accounts for the shift in terms when a site becomes live, would have been incredibly helpful for me in the past.