I would still choose Rails or Laravel. When we were building the MVP for Transistor.fm, we chose Rails because it's what my co-founder knew the best. These ol

I would still choose Rails or Laravel. When we were building the MVP for Transistor.fm, we chose Rails because it's what my co-founder knew the best. These old-school web frameworks are mature, and still have a big ecosystem (community, resources, etc). Beyond Rails, we used AWS with Postgres, Redis, nginx/puma, and sidekiq for background jobs. With any business (especially early stage), you only make progress when stuff gets built, deployed, and into the hands of customers. Remove anything that slows you down (like learning a new stack). When we were in the MVP stage we recorded this podcast and went into more depth: https://saas.transistor.fm/episodes/nerd-stuff-our-web-app-tech-stack https://saas.transistor.fm/episodes/nerd-stuff-our-web-app-t...