Articles and updates from Next.js SaaS Templates.
Why a Rails or Go API can't hand a Google OAuth session to a separate-origin Next.js frontend by redirect, and the single-use handoff code that replaces it.
The Stripe constraints that aren't on the getting-started page: the 120-day wait for two-day ACH settlement, unpublished bank debit volume limits, mandate wording you can't broaden later, and why test clocks can't fast-forward a bank debit.
My hosting stack costs roughly $7-8/month all-in, and most of the individual pieces are free. Here's what I'm actually using, and why.
Rails vs Go compared for building a SaaS backend: real tradeoffs in auth, admin panels, background jobs, and database tooling, from building the same registration flow in both.
What 'add user registration' really costs: password hashing, email verification in dev and production, background sending, and a POST-only confirm link.
I kept stalling at deployment, never at the idea. So I built starter templates for Rails and Go that handle hosting, auth, and the infrastructure for me.