Our Stack, 2 Years Later
We switched to this stack in 2023. We haven't changed.
Here's why.
The Stack
Frontend: Next.js + TypeScript
- Server-side rendering for SEO
- TypeScript prevents bugs
- Great developer experience
- Huge ecosystem
Backend: Supabase
- PostgreSQL for data
- Built-in auth
- Real-time subscriptions
- Edge functions
Payments: Stripe
- The standard
- Great docs
- Trusted by users
Deployment: Vercel
- Zero config
- Edge network
- Great DX
Why We Chose This
1. Fast to Build
Next.js + Supabase = prototypes in days.
We've shipped MVPs in 6 weeks that used to take 12.
2. Scales Automatically
We don't think about infrastructure. Vercel handles it.
Supabase scales without config.
3. Great Developer Experience
We enjoy building with this. That matters.
Happy developers = better code.
What We'd Change
Maybe: Turso instead of Supabase
Edge SQLite is interesting. But Supabase is proven.
Maybe: Railway instead of Vercel
Better pricing. Still evaluating.
The Alternative Stacks
Traditional LAMP
PHP + MySQL + Apache
Works. Boring. No modern features.
Enterprise: AWS + React + Node
Powerful. Complex. Expensive.
JAMstack: Astro + Headless CMS
Great for content sites. Less for SaaS.
The Honest Answer
This stack isn't revolutionary.
It's proven. It's stable. It works.
We optimize for outcomes, not novelty.
When to Choose Something Else
- Building a game: Unity
- Real-time chat: Elixir/Phoenix
- Heavy ML: Python stack
This stack is for typical SaaS products.
Not every product is typical.
