Boring is a feature, not an insult
Look across enough build prompts on this register and the same handful of tools keep showing up, over and over, regardless of what the app actually does. That's not a lack of imagination — it's that a small set of well-documented, well-supported tools is exactly what makes an AI agent's output reliable. An agent that's seen a framework a million times in training data writes better code with it than one it's rarely encountered. Boring and proven beats new and clever, almost every time, for exactly this reason.
Frontend: Astro or Next.js
Astro for anything content-heavy and mostly static — a landing page, a directory, a blog. Next.js once you need real interactivity, user accounts, or a backend woven into the same codebase. Both are extremely well-documented and both are what most build prompts on this register default to for exactly that reason.
Database: Supabase, or self-hosted Postgres directly
This one has a genuinely honest asterisk on it: Postgres, the database underneath Supabase, is free and open-source. What Supabase actually sells is managed hosting, backups, and auth layered on top of something you could run yourself for the cost of a server. For a small personal project, that's worth knowing — self-hosting is a real option, not just a cop-out. For not wanting to be the person on call when the database has a problem, paying for the managed version is a legitimate, reasonable choice.
Payments, email, hosting: rent, don't build
Three things on this list are worth naming specifically as places this site says don't try to build it yourself, even though everything else here is about building things yourself. Payments (Stripe or a comparable processor) needs a licensed processor by law, not just by difficulty — this isn't a coding decision. Transactional email (Resend or similar) is trivial to send and genuinely hard to get reliably delivered, since deliverability is an ongoing reputation problem, not a one-time build. And hosting infrastructure — global edge networks, automatic scaling — is precisely the kind of thing worth renting rather than building, which is true of this site's own hosting choice too.
The pattern underneath all of it
Every recommendation here follows the same rule this whole register is built around: build the part that's genuinely yours — the specific feature, the specific workflow, the thing that makes your idea your idea — and rent the parts that are commodity infrastructure everyone needs the same version of. Nobody's idea is actually differentiated by which payment processor or which database host they used.