April 18, 2026 · 8 min read
The Zero-Fluff Stack I Actually Use in Production
A practical stack review: what I keep, what I avoid, and why standard tools usually outperform complexity theater.
Core Defaults
Framework choice is mostly an operations decision. I use Next.js and TypeScript because onboarding is fast and maintenance cost stays predictable.
Tailwind helps me keep UI consistency without switching mental context every ten minutes.
Backend and Data
PostgreSQL is my default because relational problems dominate real products. I do not optimize for edge cases on day one.
I avoid reinventing commodity infrastructure like auth and payments when mature providers already solve it.
- Auth: managed where possible
- Payments: Stripe
- Database: PostgreSQL/Supabase patterns
Ops and Growth Tooling
Deployment should be boring. The goal is confident release cycles, not infrastructure prestige.
Analytics and email tooling should stay lightweight so product teams can move without platform drag.
What I Skip on Purpose
Some tools are powerful but expensive in team cognition. I avoid them until they are undeniably necessary.
- Complex state machinery for simple apps
- Heavy local container workflows by default
- Platform-level orchestration too early in the lifecycle