Tech stacks by project

Six kinds of project. Each stack lists the jobs it needs in setup order, an example tool per job, the $0 option, and what can wait.

Apps made with Lovable, Bolt, v0 or another AI builder

These tools host your app while you build it. Before other people use it, do these four things:

  1. Connect a GitHub repository. Your code then exists outside the builder, and any app host on this site can deploy it from there.
  2. Keep the database it set up, and learn its free-tier catches. If the builder created a Supabase project, that is an ordinary Postgres database you own. Free Supabase projects pause after a week with no activity and have no automatic backups.
  3. Move secret keys to the server. Keys for payments, AI APIs or your database's service role must never be in code that runs in the browser. Search your project for them before you share the link.
  4. Add what builders usually leave out: your own domain, an email service for sign-up and password-reset emails, and an error tracker. The SaaS stack covers each.

Why stacks are grouped by project

A blog and an AI chatbot need different things whatever the size of the team. Each stack names one tool per job, with a $0 option next to it where a good one exists. The category pages compare every option with its pricing.

Terms such as egress, MAU and cold start are defined in the glossary.