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.
I'm one of the founders of Flexy. Happy to answer questions.
The insight that led to this: I watched a friend's startup spend 3 weeks
hiring a contractor for a 2-day task. The friction—interviews, contracts,
onboarding—wasn't worth it. But they couldn't just ask their engineers to
drop everything, and they couldn't wait 3 weeks.
Productized services work great for other verticals (design, marketing,
copywriting). We thought: why not development?
The hard part wasn't the development—it's the matching. Getting the right
developer for each task's tech stack. We've built our vetting and matching
process around that.
Feel free to ask about pricing, use cases, tech stack limitations, or why
we think this is better than Toptal/Upwork/agencies. Happy to engage.
We are IT Service company with so many developers in-house. For the skill gap, we have vetted the most efficient partner companies in local area making us the most efficient to handle any tech stack.
We have scope of work in the quote. If client wants to change anything, depending on status of the task and the impact of change, we charge additional amount and record a scope of work change or additions.
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.