I agree with that too comments that you should avoid having a backend at all for your MVP if you can avoid it (just make a static hosted website with HTML, CSS,

I agree with that too comments that you should avoid having a backend at all for your MVP if you can avoid it (just make a static hosted website with HTML, CSS, and minimal JS). But since you asked about backends specifically, this is what I would use. I would use clerk.dev for authentication, Hasura for the CRUD API, neon.tech for the database, S3 for static files (images), and AWS Lambda for any extra functionality you can’t accomplish with Hasura natively (but call them through Hasura). Personally, I like using GraphQL because I can just focus on my data model and not think about what endpoints I need to make. But there’s definitely a learning curve, so sticking with a REST API is probably better for most people. As an alternative, I would also consider Supabase like you mentioned. It sounds cool, but I’m already comfortable with Hasura so that’s what I go to first. Update: For a website, I would actually use Remix with Clerk for auth and Prisma/SQLite for data stuff. That’s one of their premade starter stacks. I made one prototype with Remix and had a lot of fun using it. It’s easy to learn and will give you a high performance full stack app. My original answer is what I would use if you’re making a mobile app.