Case studies·Tools

Nomad List

One founder, PHP, SQLite, and a Google Sheet MVP

Pieter Levels built Nomad List solo on deliberately boring tech — no React, no Kubernetes, no platform team. It started as a spreadsheet and grew into a profitable nomad directory still running on a cheap VPS.

2014

Ship the spreadsheet, not the platform

Side project · first paying members

Nomad List began as a Google Sheet ranking cities for remote workers — the fastest possible backend for validating whether anyone cared. Pieter Levels has written repeatedly that frameworks are a trap when you are still hunting product-market fit.

The MVP did not need auth, sharding, or a roadmap to microservices. It needed cities, scores, and a way to take money from people who found it useful.

Lesson

If your idea fits in a spreadsheet, start in a spreadsheet. You are testing demand, not auditioning for a SRE role.

2015–2018

Boring stack, real revenue

~$1M combined annual revenue (Nomad List + Remote OK, ~4 years in)

Once the idea stuck, Levels rewrote Nomad List in vanilla PHP with SQLite on a single VPS — the same stack he uses across Nomad List, Remote OK, and later products. No Laravel, no ORM ceremony, no container orchestration.

He has publicly described Remote OK as fitting in a single PHP file and documented CDN tweaks (SPDY, CloudFront, PageSpeed) when pages got slow — optimization, not re-architecture.

Lesson

PHP and SQLite are not punchlines. They are production defaults for a solo founder who owns every line of code.

2019–today

Still one person, still no platform team

Solo founder · portfolio past seven-figure annual revenue (public updates)

In interviews and on his blog, Levels reports Nomad List and sibling products on hundreds of thousands of monthly visitors and high six- to seven-figure annual revenue — still maintained largely alone on VPS hosting he describes as tens of dollars a month, not AWS-scale bills.

The stack did not graduate to Kubernetes. The business graduated to profitability. That is the point of the story for indie hackers: boring tech held because the product held.

Lesson

You do not need a staff engineer to review your Helm charts. You need a product people pay for on infrastructure you can reboot yourself.

Sources

Facts drawn from public engineering posts and interviews. Numbers are approximate where sources disagree — we're stack advisors, not historians.

Get the right stack for YOUR scale — not theirs

Nomad List's stack made sense for Nomad List. Yours won't — and copying theirs is how you end up with a $4k/month bill and three unused Kubernetes clusters.

Plan my stack — free