Hey HN, maker here – happy to answer detailed questions about the stack, trade-offs, and whether Brick Starter is a good fit for your use case. What it include

Hey HN, maker here – happy to answer detailed questions about the stack, trade-offs, and whether Brick Starter is a good fit for your use case. What it includes today? Backend: .NET Core 8 with a layered architecture (API, application services, domain, infrastructure) and patterns for dependency injection, validation, and background processing Frontends: templates for Angular, React + Next.js, Vue, Blazor, and ASP.NET Core, all wired to the same backend API SaaS essentials: multi-tenant support, authentication/authorization, user and org management, roles/permissions, and payments using stripe Infrastructure concerns: caching (e.g., Redis), configuration, logging, and some “starter” patterns for deployment and CI/CD that you can adapt to your own cloud setup Who it’s for? Teams or solo devs who are comfortable with .NET but don’t want to keep rebuilding the same SaaS plumbing for every new product Agencies/consultants who repeatedly deliver SaaS-style projects and want a consistent, battle-tested baseline What it is not? A no-code tool. A magic “click once and you have a SaaS” product; you still write plenty of custom code, but start from something opinionated and production-aware If you’re using .NET and have strong opinions about architecture, multi-tenancy, or frontend stacks, would love to hear where this matches (or clashes with) how you like to structure projects.