Stacks

Ship a SaaS this weekend

Editor, UI, Postgres, payments, a URL, and somewhere to see the crash.

A practical loadout for an indie SaaS you can demo on Monday. Stay in a real editor, generate the first screens if you want, and use hosted data, billing, and deploys so you are not assembling infrastructure from scratch.

Outcome A hosted web app with a database, a way to charge, and error reports.

1. 01

   Freemium

   Cursor

   Build

   Daily driver. The agent and the editor are the same place, which is what you want when the whole product is still one repo.

   Score 8.6 · Daily driving an AI editor on a real repo

2. 02

   Check site

   v0

   First UI

   Use it to get a React and Tailwind starting point, then bring the code into the repo. Do not keep the product inside the generator.

   Score 7.5 · Generating the first React screens

3. 03

   Freemium

   Supabase

   Data

   Postgres, auth, and file storage in one project so the weekend does not disappear into backend setup.

   Score 8.5 · Postgres plus auth for an indie app

4. 04

   Usage-based

   Stripe

   Payments

   The default when you want cards and subscriptions and you are willing to handle taxes yourself. Rates: check site.

   Score 8.0 · Taking cards and running subscriptions

5. 05

   Freemium

   Vercel

   Deploy

   Push the repo and get a URL. The shortest path if the app is Next.js or another frontend framework it already knows.

   Score 8.2 · Deploying a Next.js app with preview URLs

6. 06

   Freemium

   Sentry

   See failures

   You will ship a bug. Sentry tells you which one, with the stack, before a user has to email you.

   Score 7.7 · Knowing what broke in production