DotForge.dev Reviews and Details

Questions & Answers

1. What's the story behind DotForge.dev?

   I kept rebuilding the same three months of plumbing. Every new SaaS project started with the same multi-tenant auth, the same tenant isolation, the same design system, the same wiring, before any actual product work could begin.

   DotForge is that layer, taken out of software that runs in production and generalized so it carries no domain of its own. What ships is the infrastructure, plus a demo application you can delete in ten minutes once you have seen it work.

2. How would you describe the primary audience of DotForge.dev?

   .NET developers building SaaS products, and the consultancies and freelancers who start client projects from scratch. People who are already productive in C# and Angular and would rather not learn a different stack just to ship a multi-tenant application.

3. What makes DotForge.dev unique?

   DotForge is the only SaaS starter kit built on .NET 10 with Angular 22, both current releases. The existing .NET kits are anchored on .NET 7 or 8 and, when they ship a frontend at all, on Angular 16 or React.

   It was extracted from production software rather than written for a demo: the infrastructure layer of a real multi-tenant application, generalized into a kit. That includes a 48-component design system of its own, with no Material, no PrimeNG and no UI library underneath.

4. Why should a person choose DotForge.dev over its competitors?

   Tenant isolation is proven, not claimed: cross-tenant access returns 404 rather than 403, so one tenant cannot even learn that another tenant's data exists, and integration tests assert it across every verb. The filters are generated from a marker interface instead of hand-copied per entity, and the write interceptor fails closed.

   One command gets you a running product. aspire run boots PostgreSQL, migrations, the API and the SPA; you sign in with printed credentials and land on a working dashboard with real data, not a skeleton.

   And the design system is yours: no UI library to fight, no theme to override, dark and light from the same components.

5. Which are the primary technologies used for building DotForge.dev?

   Backend: .NET 10, ASP.NET Core Minimal APIs, Entity Framework Core 10, PostgreSQL (SQLite for zero-Docker development), .NET Aspire, ErrorOr, FluentValidation, Mapster, xUnit.

   Frontend: Angular 22 standalone and zoneless, TypeScript 6, Tailwind CSS v4, Signal Forms, Vitest.

   CI: GitHub Actions.

6. Who are some of the biggest customers of DotForge.dev?

   None yet. DotForge goes on presale on September 22, 2026, and has not been sold to anyone. The code it is built from has been running in production for years, but the kit as a product has no customers to name.