The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Back to feedPost
After 10+ years of shipping client projects, my default stack is boring on purpose.
→ Go for APIs. Fast, one binary, easy to deploy
→ Vue 3 + TypeScript for UIs that stay maintainable
→ PostgreSQL for almost everything
→ Docker + GitHub Actions so every deploy is the same
I still reach for Laravel, Next.js, FastAPI or Flutter when the project calls for it. But a stack that's boring to run gives clients more time to grow the business.
What's your default, and why?
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Related posts
Web Based Admin Panel using framer to manage Plants Inventory
the glassy cards and framer animation makes it great. congrats..
The fastest SaaS products we've built didn't use the newest stack. They used the most boring one.
What we reach for when a founder needs a working product:
• Next.js App Router, React, TypeScript and Tailwind
• Supabase Auth and Postgres, Prisma for the schema
• Stripe subscriptions kept in sync with webhooks
• Transactional email for the moments that matter
• A marketing site in Webflow or Framer the team can edit
What we skip at MVP stage: microservices, Kubernetes and anything the first 100 users won't notice.
Every novel choice is one you'll debug at 2 a.m. Save the novelty for the part customers pay for.
Founders: what did you over-build in your first version?
Really agree with keeping the stack simple early on. Curious, how do you decide when a SaaS product has outgrown its MVP architecture? Would love to exchange thoughts on this in DMs.
Left one.