Full-Stack App Starter Kits

This is really useful! Having production-ready apps with auth and payments already wired up can save developers so much time. 🚀

The two interchangeable backend editions (Node/Express or Go) on one shared architecture is more valuable than it looks. Most starter kits quietly lock you into the author's stack, so 'buy once, own forever' often means inheriting someone else's framework decisions. The timezone-correct, DST-safe availability engine in the Booking kit is the detail I would weigh most - that is the part teams routinely underestimate and end up rebuilding. Real question though: when the base architecture ships an update, how do buyers who have already customised a kit pull it in? That handoff is where one-time-purchase kits usually get painful.

Hi Fazier, I'm Ken. For the past year and a half I've been building React frontends for a European fintech, and every new project started the same way: rebuild auth, rebuild payments, rebuild roles, and only then start on the actual product. I turned that work into kits. They are not boilerplates. Each kit is a finished application - UI, REST API, MongoDB, auth - and every kit sits on the same architecture, so you choose your stack instead of inheriting mine: Node/Express or Go on the backend, MUI or Tailwind on the frontend. The source comes in a private GitHub repo, you self-host it and you keep it forever. One-time price, no subscription. Three kits so far - Booking, Registration and Checkout - each with a live demo you can click through before buying. This is my first launch and I would rather have hard feedback than upvotes: tell me what is missing, what you would never pay for, and which kit you would want next.

Interesting to see how starter kits would survive the AI era :)