The right amount of "cutting edge" when starting a project

I've historically struggled to find starter kits/boilerplates compelling because:

1. They are either old-school and reliable but haven't kept up with the times like Django-based starter kits, or
2. They are too cutting-edge and built using Firebase or something similar - I just want to bring my SQL database

However, the state of web development has improved significantly over the past five years, and I believe we are starting to consolidate on some key technologies.

As an indie hacker, my goal is to move fast while ensuring safety. I can't rely on another team of on-call engineers. We should only adopt new technology if it enables us to move quickly and safely. A couple of relatively new technologies that I've found useful for this are:

tRPC and Prisma: These technologies provide backend <> frontend type safety. You only need to declare your types in the DB schema, and they are automatically available in the frontend. This is personally insane to me -- much better compared to having to declare types in multiple places or use GraphQL.

Vercel serverless with Next.js: With this technology, you can push your code to Git and have your serverless backend up in just two minutes.

Based on this philosophy, I built a starter kit with some friends called neorepo.com. I think it satisfies my personal requirements for "the right amount of boilerplate." It takes care of non-differentiated tasks like authentication, org management, and basic components, while still allowing me to have complete control over my brand and product logic.

Perhaps some of you will find it useful. You can find more information on the website to determine whether or not it could be a good fit for you.

How do you approach working with the right amount of "cutting-edge" technology? Honestly I personally need to work in a little bit of new tech all the time or I'll go insane from boredom haha