Really, whatever you know. But since that's a boring answer, so I'll assume you know exactly what I know. Anyway, as usual, "it depends," but there's probably

Really, whatever you know. But since that's a boring answer, so I'll assume you know exactly what I know. Anyway, as usual, "it depends," but there's probably a big split based on a specific question: "How rich is your frontend?" (and how rich will it need to get in the next few years)? If the answer is "rich enough" - ie you want a fair deal of dynamic content and a web-app feel, I'd do: - ReactJS via create-react-app with typescript and ReactQuery for talking to the API - Rails in api mode serving a rest api - Postgres for the db and Redis for caching/job storage. - Heroku If the answer is "not that rich," save yourself some complexity: - Normal Rails with server-rendered pages - Postgres/redis - Heroku Note: swap out Rails with whatever similar thing is in a language you know: Django, Phoenix, Laravel, etc. Now, all that said, I strongly suspect the dominant answer to this question is shifting. There seems to be a new wave of JS-based tools like Next.JS and RedwoodJS that seem batteries-included-enough to replace Rails as the getting-off-the-ground-quickly framework of choice. We'll see, though- it's still early.