Surviving the JS Ecosystem: Auth, Netlify, and the New Rules of Next.js 16
How a harmless Next.js frontend forced us to battle hosting providers, outdated documentation, and implicit conventions.
How a harmless Next.js frontend forced us to battle hosting providers, outdated documentation, and implicit conventions.
How we built a Free-Tier, protected against Abuse loads, and why we chose Clerk over cheap Supabase Auth.
How a harmless configuration file almost became an RCE vector, and why we transitioned to a Zero-Trust architecture.
How we realized that binary distribution would kill our public business, and why we had to fork the product into two branches.