The Solo Founder Stack I Use to Ship at Scale

People ask me how I ship so many products as a solo founder. The answer isn't talent or hustle — it's the stack. I've spent years refining a toolkit that eliminates friction at every step.

The philosophy

Pick boring technology, automate everything you do twice, and never build what you can buy. Every tool in my stack earns its place by saving me hours, not minutes.

The stack, top to bottom

Deploys are one command

Every push to main is a deploy. No manual steps, no checklist, no room for human error. The entire pipeline looks like this:

name: Deploy
on:
  push:
    branches: [main]
jobs:
  ship:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - uses: oven-sh/setup-bun@v1
      - run: bun install --frozen-lockfile
      - run: bun test
      - run: bun run build
      - uses: superfly/flyctl-actions/setup-flyctl@master
      - run: flyctl deploy --remote-only
        env:
          FLY_API_TOKEN: ${{ secrets.FLY_API_TOKEN }}

Twelve lines. That's it. I stop thinking about deployment forever, and every commit gets shipped within a minute of hitting main.

Constraints breed creativity

By limiting myself to a small, proven set of tools, I spend zero time deliberating and all my time building. The best stack is the one you never think about. If you're solo, every minute spent choosing between two frameworks is a minute not spent talking to users.

Pick your eight tools. Stop shopping. Start shipping.