For frontend, I would go with either React or Vue, both with a huge community and already a lot of builtin solutions.
I would 100% start with a design system, maybe material UI.
Nothing fancy, low maintenance and painless onboarding/development experience.
It really depends on the use-case. Async Python is nice for IO-heavy APIs
If CPU-heavy workloads are likely, I'd probably look into using go.
In terms of FE, it really depends on the skill-set in the team. I went for Vue over React when we had to have a bunch of backenders whip up a FE simply because it's more opinionated and we didn't want to have to make as many choices when getting started. Also, just rendering HTML on the server side can still get you a long way
For the DB, again, it depends on your use case and what your data-model looks like, but I think a relational DB like postgres is a safe choice 99% of the time. You might need to couple it with something else on occasion (I've reached for elasticsearch more times than I can count)
Five options I’d consider depending on which language I am most familiar with:
Php Laravel with live wire/alpinejs
Ruby rails with Hotwire
Elixir Phoenix with live view
Python Django with htmx/alpinejs
Javascript nextjs or nuxtjs or redwooodjs
The onboarding for other developers is also painless. I've recently experiment with AWS Amplify and even if is not quite there yet, is pretty close.
Lambda, cloudfunctions, https://supabase.com/, https://hasura.io/, AWS Amplify, https://aws.amazon.com/serverless/.
For frontend, I would go with either React or Vue, both with a huge community and already a lot of builtin solutions. I would 100% start with a design system, maybe material UI.
Nothing fancy, low maintenance and painless onboarding/development experience.