I wrote one (very opinionated) in C# ASP.NET a long time ago (14 years or so and since ported to all versions of .net core besides 6) because I hated the plumbi

I wrote one (very opinionated) in C# ASP.NET a long time ago (14 years or so and since ported to all versions of .net core besides 6) because I hated the plumbing I had to do with most options in the space. 4 years ago, I started a large project and I was pushed to use vanilla asp.net with the promise that things were better now. Unfortunately I miss my own framework now all the time; it would let you focus on the logic and your core strengths. I had to create data models and logic and the framework would give me frontends (mobile, desktop and web) and api’s, with auth etc without me having to think about it. Then a frontend person had a working system they could fix the frontends for without touching the logic etc. I added, in 2017, micro services which, without having you to think too much about them, allowed you to point out which namespaces you want run seperately. And deployment (on aws, azure and alicloud) was all automated. If I find the time, I will clean it up and open source it. And for side projects I will use it again.