Solved: If not Next.js, then what frontend for a self-hosted?

🚀 Executive Summary TL;DR: Self-hosting Next.js introduces significant operational complexity due to its Vercel-centric design, leading to issues like OOM-killing and convoluted build pipelines. The solution involves adopting battle-tested alternatives: Astro for content-focused static sites, classic SPAs for internal tools, or SvelteKit for deliberate self-hosted SSR, prioritizing simplicity and operational sanity. 🎯 Key Takeaways Self-hosting Next.js incurs a ‘complexity tax’ because it requires replicating Vercel’s serverless ecosystem, leading to issues like long-running Node.js servers, complex caching for ISR, and convoluted build pipelines. Astro is the recommended modern powerhouse for content-focused sites, delivering pure HTML/CSS at build time with optional client-side JavaScript ‘islands,’ offering simple deployment and performance. Classic Single Page Applications (SPAs) built with tools like Vite are ideal for internal dashboards or admin panels where SEO isn’t a concern,