NetCoreSaaS is a complete SaaS codebase built on .NET with multiple frontend options including Vue, React, and Svelte. It features a clean architecture design with multiple layers (Domain, Application, Infrastructure, WebApi) organized for maintainability and scalability.
Key Technical Features
Clean Architecture with properly separated concerns across multiple layers
Extensive Testing with over 130 integration tests covering core functionality
Multi-tenancy with options for single database or database-per-tenant
Multi-organization & workspace support with proper role-based permissions
Subscription Management with Stripe integration and dynamic pricing
Internationalization with support for multiple languages
Multiple database support including PostgreSQL and MySQL
Themable UI with TailwindCSS for customization
The solution provides everything needed to launch a professional SaaS application quickly with enterprise-grade architecture and features.
A clean architecture ASP.NET multi-tenant API with Vue, React and Razor Pages UI for building SaaS applications.
C#
JavaScript
TypeScript
Bootstrap
PostgreSQL
ASP.NET
Entity Framework
MVC Razor
React
Vue.js
Features:
Access Control
API
Auth
Clean Architecture
CRUD
Dark Mode
JWT
+4 more
Frequently Asked Questions
C#
What makes C# ideal for SaaS development?
C# excels in SaaS development due to its robust ecosystem, strong typing capabilities, and excellent library support. C# boilerplates leverage language-specific features to provide type-safe database queries, efficient API routing, and optimized runtime performance. The language's maturity means you get battle-tested packages for authentication, payment processing, and background jobs that integrate seamlessly.
.NET
What .NET-specific architecture patterns are implemented?
.NET boilerplates leverage the framework's native architecture patterns including its routing system, middleware pipeline, and controller/handler structure. They implement .NET's conventions for separating concerns, dependency injection, and service layer patterns. The codebase follows .NET's best practices for organizing models, views/components, and business logic to ensure maintainability as your application grows.
React
What React-specific architecture patterns are implemented?
React boilerplates leverage the framework's native architecture patterns including its routing system, middleware pipeline, and controller/handler structure. They implement React's conventions for separating concerns, dependency injection, and service layer patterns. The codebase follows React's best practices for organizing models, views/components, and business logic to ensure maintainability as your application grows.
Svelte
What Svelte-specific architecture patterns are implemented?
Svelte boilerplates leverage the framework's native architecture patterns including its routing system, middleware pipeline, and controller/handler structure. They implement Svelte's conventions for separating concerns, dependency injection, and service layer patterns. The codebase follows Svelte's best practices for organizing models, views/components, and business logic to ensure maintainability as your application grows.
SvelteKit
What SvelteKit-specific architecture patterns are implemented?
SvelteKit boilerplates leverage the framework's native architecture patterns including its routing system, middleware pipeline, and controller/handler structure. They implement SvelteKit's conventions for separating concerns, dependency injection, and service layer patterns. The codebase follows SvelteKit's best practices for organizing models, views/components, and business logic to ensure maintainability as your application grows.
Vue.js
What Vue.js-specific architecture patterns are implemented?
Vue.js boilerplates leverage the framework's native architecture patterns including its routing system, middleware pipeline, and controller/handler structure. They implement Vue.js's conventions for separating concerns, dependency injection, and service layer patterns. The codebase follows Vue.js's best practices for organizing models, views/components, and business logic to ensure maintainability as your application grows.
React
What React-specific component architecture is used?
React boilerplates follow the framework's component composition patterns with reusable, atomic design components. They implement React's best practices for component structure, props handling, event management, and lifecycle methods. The component library includes authentication flows, dashboards, data tables, forms with validation, and navigation—all built with React's native features like hooks (React), composition API (Vue), or directives (Angular).
Tailwind CSS
What Tailwind CSS-specific component architecture is used?
Tailwind CSS boilerplates follow the framework's component composition patterns with reusable, atomic design components. They implement Tailwind CSS's best practices for component structure, props handling, event management, and lifecycle methods. The component library includes authentication flows, dashboards, data tables, forms with validation, and navigation—all built with Tailwind CSS's native features like hooks (React), composition API (Vue), or directives (Angular).
MySQL
What MySQL-specific features are leveraged in these boilerplates?
MySQL boilerplates utilize the database's native capabilities including its transaction model (ACID for SQL, eventual consistency for NoSQL), indexing strategies (B-tree, GiST, full-text search), and advanced features like JSON columns, array types, window functions, or document queries. The schema design takes advantage of MySQL's strengths—whether that's PostgreSQL's JSONB, MySQL's full-text search, MongoDB's aggregation pipeline, or Redis's data structures.
PostgreSQL
What PostgreSQL-specific features are leveraged in these boilerplates?
PostgreSQL boilerplates utilize the database's native capabilities including its transaction model (ACID for SQL, eventual consistency for NoSQL), indexing strategies (B-tree, GiST, full-text search), and advanced features like JSON columns, array types, window functions, or document queries. The schema design takes advantage of PostgreSQL's strengths—whether that's PostgreSQL's JSONB, MySQL's full-text search, MongoDB's aggregation pipeline, or Redis's data structures.
Stripe
What Stripe API features are implemented?
Stripe boilerplates implement the provider's complete API suite including checkout sessions, subscription lifecycle management, customer portal, webhook event handling, and invoice generation. They use Stripe's latest API version with proper error handling, idempotency keys, and retry logic. The integration includes Stripe-specific features like payment intents, setup intents, subscription schedules, and tax calculation APIs.
C#
What C#-specific tools and libraries are included?
C# boilerplates include the language's most popular and production-proven tools. This typically includes testing frameworks, linters, formatters, build tools, and package managers specific to C#. You'll get pre-configured toolchains that enforce best practices, automated testing pipelines, and development environments optimized for C# development workflows.
.NET
How does .NET's ORM/database layer work in these boilerplates?
.NET boilerplates use the framework's native ORM or query builder (Prisma, Eloquent, Active Record, SQLAlchemy, etc.) with pre-configured models for users, subscriptions, teams, and common SaaS entities. They include optimized queries, relationships, migrations, seeders, and database connection pooling. The implementation leverages .NET's specific features like eager loading, query scopes, and transaction handling for performance.
React
How does React's ORM/database layer work in these boilerplates?
React boilerplates use the framework's native ORM or query builder (Prisma, Eloquent, Active Record, SQLAlchemy, etc.) with pre-configured models for users, subscriptions, teams, and common SaaS entities. They include optimized queries, relationships, migrations, seeders, and database connection pooling. The implementation leverages React's specific features like eager loading, query scopes, and transaction handling for performance.
Svelte
How does Svelte's ORM/database layer work in these boilerplates?
Svelte boilerplates use the framework's native ORM or query builder (Prisma, Eloquent, Active Record, SQLAlchemy, etc.) with pre-configured models for users, subscriptions, teams, and common SaaS entities. They include optimized queries, relationships, migrations, seeders, and database connection pooling. The implementation leverages Svelte's specific features like eager loading, query scopes, and transaction handling for performance.
