If you're starting a new SaaS project and wondering whether your tech stack choice matters — our data suggests it does. Not because certain frameworks are inherently better, but because the stack successful indie hackers converge on tells you something about what lets you ship fast enough to survive.
We analyzed the tech stacks of 800+ monetized websites in our database (sites with confirmed active payment infrastructure — Stripe, Paddle, LemonSqueezy integrations detected live). Here's what they're actually running.
The Dominant Stack
The pattern is remarkably consistent across categories:
| Technology | Monetized Sites Using It |
|---|---|
| Next.js | #1 framework by a wide margin |
| Tailwind CSS | 536 confirmed monetized sites |
| Vercel | 600+ monetized sites hosted |
| Cloudflare | Close second to Vercel |
| React | Underlying most of the above |
This isn't a "what's popular on Twitter" finding — it's what's actually running behind sites that are charging real customers right now.
What We Expected vs. What We Found
We expected Rails, Django, and Laravel to show up heavily. They barely appear in the top 15.
The shift toward Jamstack + serverless is real and measurable. Founders building subscription businesses in 2026 are not standing up Rails monoliths. They're pushing to Vercel with a git push and wiring in Supabase for the database layer.
The reasons hold up when you think about it:
Vercel + Next.js removes an entire layer of ops work. Serverless functions handle your API routes. Edge caching handles your performance. You don't hire a DevOps person at $0 MRR.
Tailwind kills the CSS bikeshedding problem. Solo founders can't afford to spend a week perfecting a design system. Tailwind + a component library (shadcn/ui appears frequently in our data) means shipping a usable UI in hours.
The ecosystem is dense. Choosing the same stack as thousands of other indie hackers means your specific problem has almost certainly been solved and documented.
The Backend Reality
One thing the data can't fully show: most of these Next.js sites are using a backend-as-a-service layer they didn't build themselves. The pattern we see in monetized sites:
- Auth: Clerk or NextAuth
- Database: Supabase or PlanetScale
- Payments: Stripe (detected most frequently despite being harder to detect client-side)
- Email: Resend or Loops
The entire stack can be assembled in a weekend. That's the point.
Real Examples From Our Database
Actual monetized products running this stack that we've detected:
- poteam.pro — productivity tool, Next.js + Tailwind, confirmed payment signals
- sidestackers.com — indie hacker platform, same stack
- Several AI tools in the 31–90 day post-launch window (our highest-monetization cohort) running identical infrastructure
The Boring Stack Wins
There are flashier options. Bun, Astro, SvelteKit — all legitimately good. But when you're looking at which stack appears most frequently in products that are actually charging money, the answer is not the most interesting one: it's Next.js, styled with Tailwind, deployed on Vercel, with Stripe handling money.
The insight isn't "use these tools." It's that the variance in tool choice for early-stage SaaS is much lower than the discourse would suggest. The founders who are monetizing aren't the ones with the most interesting tech stacks.
This data comes from MRRScout, which monitors 33,000+ newly launched websites and tracks which ones reach active monetization. If you want to see what's currently in the 31–90 day high-monetization window, the full database is at mrrscout.com/discover.
Top comments (0)