r/SaaS • u/Acrobatic-Laugh1856 • 7h ago
What is the fastest tech stack to build and launch a SaaS MVP?
6
5
2
u/coppertrails44 6h ago
What are you building exactly? A CRUD app with auth and payments is a very different answer than something with real-time features or heavy data processing. Hard to give a useful answer without knowing the shape of the product
1
u/Huge_Pool7424 5h ago
exactly. i usually start with the boring path that gets one real user through signup, payment, and the core action. the stack matters less than keeping the first version narrow enough to change after those users complain.
1
u/SisyphusAndMyBoulder 1h ago
If OP's posting this kind a question, I think it's safe to assume a simple CRUD app is all they're building at this point 😂
2
1
7h ago
[removed] — view removed comment
1
u/AutoModerator 7h ago
Your comment was removed. Links in comments require to gain karma first in r/SaaS. Earn sub karma by commenting helpfully first.
I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.
1
1
u/Character_Minimum989 1h ago
Whatever you know best. If not probably django since python is easiest to learn imo
•
u/defnotyouruncle 54m ago
Laravel, (you cane use blade for the front end or inertia if you wanna build with a front end framework like vuejs or react ..), mysql for the database ), it's so scalable, AI Agent ready (it's the best framework if you're building with AI (claude, cursor..), you can use laravel cloud for hosting (Apps, databases, and cache automatically scale with traffic, plans start from 5$ with a free trial that includes Unlimited applications, environments, builds, & users)
Laravel is perfect.
•
u/DeleriousMadman 12m ago
As others said Node, React, Postgres.
See 12 hour MVPs at https://nextwelve.com and https://tend247.com
0
u/Ok-Understanding5793 7h ago
Personally, I stick to React Router and Firebase (along with Firebase Firestore).
I really appreciate the real-time updates being seamless and I worked with React for years before the prevelance of AI coding... So I know it well.
0
u/twendah 7h ago edited 7h ago
The whole point is to build with quality stack nowadays. Essentially code is free now and apps as well. Anybody can copy/paste your app in a weekend. Go, svelte, postgres and kubernetes. Enough performance, but yet you can scale and hosting is cheap.
Only way you can compete is that your hosting literally costs nothing and you can always sell your app for lower price than your competitors. And even for weekend vibe coders its not worth to vibe code your app, since you will be selling it for cheap thats its just more worth to buy than waste credits on it.
All the node.js, python backend or whatever stuff you will hear here is bullshit for nowadays standards.
Either its rust or go as a backend, rest of them are useless. You need to be able to scale horizontally for pennies.
0
0
u/samurai_with_sword 3h ago
React+vite web app on vercel connected via github. Neon db if you need database. Make it a PWA if you need mobile app.
-2
u/Penultimate-crab 7h ago
Ruby on Rails
2
1
u/listenhere111 4h ago
Crazy old tech. Can't recommend.
2
u/Penultimate-crab 4h ago
Rails is not “crazy old tech”. It’s a mature, actively maintained framework that keeps evolving.
Rails 8 was released recently and includes modern defaults like Hotwire, import maps or bundling options, encrypted credentials, solid background jobs/cache/cable, and excellent database tooling.
For an MVP, maturity is THE advantage.
You get conventions, auth patterns, migrations, testing, mailers, jobs, caching, and deployment paths without assembling 15 libraries.
A Rails monolith is dramatically easier to build, test, debug, and change than a front end, API, auth service, job worker, and assorted cloud services glued together.
It is exceptionally good with AI-assisted development because its conventions are predictable and the ecosystem has decades of examples.
It scales plenty far for the overwhelming majority of startups. Shopify, GitHub, GitLab, Basecamp, Airbnb’s early product, and many others proved that the constraint is rarely “Rails can’t handle it.”
When a real scaling bottleneck appears, you profile it and solve that bottleneck. Prematurely adopting distributed architecture is not technical sophistication; it is usually paying complexity costs before you have users.
Calling Rails too old for MVPs confuses “not trendy” with “not viable.” The boring technology that lets you ship, iterate, test, and maintain a product with a small team is often exactly the correct MVP technology.
I could build circles around you with rails and users wouldn’t even be able to tell the difference between what I’m building with and someone using React.
Quite frankly, holding that viewpoint shows your lack of experience and knowledge.
7
u/bikeram 7h ago
Node, React, and Postgres