A modern .NET 10 full-stack project template for building multi-tenant SaaS applications with Vertical Slice Architecture (VSA), Hybrid Blazor, and AI-friendly structure.

Krafter is used via dotnet new.

You do not clone this repository to start an application. Clone it only if you want to contribute to the template itself.

# 1. Install the template pack (one-time)
dotnet new install AditiKraft.Krafter.Templates

# 2. Create a new app
dotnet new krafter -n MyApp            # Split Host (separate API + UI)
dotnet new krafter-single -n MyApp     # Single Host (combined)

# 3. Run it
cd MyApp
dotnet run --project aspire/MyApp.Aspire.AppHost/MyApp.Aspire.AppHost.csproj

Krafter ships as a dotnet new template pack with two hosting models:

Always use -n to set your project name — it replaces namespaces, folders, and project files throughout the generated solution.

dotnet new install AditiKraft.Krafter.Templates   # Install
dotnet new update                                  # Update to latest
dotnet new uninstall AditiKraft.Krafter.Templates  # Uninstall

Try the live demo at https://krafter.getkrafter.dev/

Default Credentials:

• Email: [email protected]
• Password: 123Pa$$word!

Alternatively, log in with Google to create a new account.

Krafter is a production-ready .NET 10 application template, not a starter toy project. It gives you a structured foundation for full-stack business apps with modern defaults already wired together.

• Template-first workflow with dotnet new
• Feature-oriented backend structure that is easier to extend with AI assistance
• Modern full-stack .NET setup without spending days on wiring
• Two hosting models so you can optimize for simplicity or separation
• Built-in patterns for auth, tenants, jobs, realtime, and observability

The diagrams below reflect the template structure and are useful before you generate or contribute to a project.

This section applies to a generated project created with dotnet new krafter or dotnet new krafter-single.

If you want to work on the template repository itself, jump to Contributing & Template Development.

• .NET 10 SDK
• Docker Desktop (for Aspire/PostgreSQL)
• Visual Studio 2022 17.11+ or VS Code

1. Create a project from the template

   dotnet new krafter -n MyApp
   cd MyApp

2. Start the AppHost

   dotnet run --project aspire/MyApp.Aspire.AppHost/MyApp.Aspire.AppHost.csproj

3. Let myapp-migrator finish before judging startup health

   • The AppHost starts the short-lived migrator before the main app resources
   • For normal startup, you do not need to run dotnet ef database update manually

4. Open the generated app

   • Aspire Dashboard: https://localhost:17285
   • Backend API (split host only): https://localhost:5199
   • Scalar API Reference (split host only): https://localhost:5199/scalar/v1
   • Blazor UI: https://localhost:7291

5. Sign in with the seeded admin account

   • Email: [email protected]
   • Password: 123Pa$$word!

   Alternatively, log in with Google, which will create a new account.

⚠️ Change the default password immediately in production.

dotnet tool install --global dotnet-ef

cd src/AditiKraft.Krafter.Backend

dotnet ef migrations add <MigrationName> --context KrafterContext
dotnet ef migrations add <MigrationName> --context TenantDbContext
dotnet ef migrations add <MigrationName> --context BackgroundJobsContext

dotnet run --project aspire/AditiKraft.Krafter.Aspire.AppHost/AditiKraft.Krafter.Aspire.AppHost.csproj

The structure below is what you get after running dotnet new krafter -n MyApp (split host). Single host is identical except Backend has no Program.cs.

MyApp/
├── Agents.md                            # AI agent instructions (entry point)
├── aspire/                              # Aspire orchestration
│   ├── MyApp.Aspire.AppHost/
│   └── MyApp.Aspire.ServiceDefaults/
├── src/
│   ├── MyApp.Contracts/                 # Shared contracts library
│   │   ├── Contracts/                   # Auth, Users, Roles, Tenants DTOs
│   │   ├── Common/                      # Routes, permissions, shared models
│   │   └── Realtime/                    # SignalR method contracts
│   ├── MyApp.Backend/                   # ASP.NET Core API (VSA)
│   │   ├── Web/                         # HTTP pipeline, middleware, auth config
│   │   ├── Features/                    # Vertical slices
│   │   ├── Infrastructure/              # Jobs, notifications, persistence, realtime
│   │   ├── Common/                      # Context, entities, interfaces, extensions
│   │   ├── Errors/                      # Exception types
│   │   ├── Migrations/                  # EF Core migrations
│   │   └── Program.cs                   # (split host only)
│   ├── MyApp.Backend.Migrator/          # Short-lived EF migration runner
│   └── UI/
│       ├── MyApp.UI.Web.Client/         # Blazor WebAssembly
│       │   ├── Features/
│       │   ├── Infrastructure/          # AuthApi, Refit, SignalR, Storage, Http
│       │   └── Common/                  # Shared components, models
│       └── MyApp.UI.Web/               # Blazor Server host (or combined host in single mode)
├── build/                               # NUKE build automation
├── docs/                                # Documentation assets
├── .github/                             # GitHub Actions workflows
└── README.md

If you are using Krafter to build an app, the main workflow is:

1. Generate a project with dotnet new krafter or dotnet new krafter-single
2. Run the AppHost
3. Add features in the existing Contracts / Backend / UI structure
4. Create migrations when your model changes
5. Let the migrator apply them on the next AppHost start

For detailed feature-by-feature instructions, naming conventions, and backend/UI implementation rules, use Agents.md and the related files in:

• src/AditiKraft.Krafter.Backend/
• src/UI/
• src/AditiKraft.Krafter.Contracts/

# Build all projects (template development)
dotnet build AditiKraft.Krafter.Dev.slnx

# Run tests
dotnet test

# Create migrations
dotnet ef migrations add <Name> --project src/AditiKraft.Krafter.Backend --context KrafterContext
dotnet ef migrations add <Name> --project src/AditiKraft.Krafter.Backend --context BackgroundJobsContext
dotnet ef migrations add <Name> --project src/AditiKraft.Krafter.Backend --context TenantDbContext

# Apply migrations through the dedicated migrator
dotnet run --project aspire/AditiKraft.Krafter.Aspire.AppHost/AditiKraft.Krafter.Aspire.AppHost.csproj

Build container images with:

dotnet publish src/AditiKraft.Krafter.Backend/AditiKraft.Krafter.Backend.csproj -c Release -p:PublishProfile=DefaultContainer
dotnet publish src/UI/AditiKraft.Krafter.UI.Web/AditiKraft.Krafter.UI.Web.csproj -c Release -p:PublishProfile=DefaultContainer

The project includes GitHub Actions workflows for:

• Building and testing on every push
• Creating Docker images for main and dev branches
• Pushing images to GitHub Container Registry
• Triggering deployment webhooks

See .github/workflows for configuration.

Clone this repository only if you want to work on the Krafter template itself.

If you want to create an application, use dotnet new krafter or dotnet new krafter-single.

git clone https://github.com/AditiKraft/Krafter.git
cd Krafter
dotnet restore

AditiKraft.Krafter/                         # Template repo root
├── .template.config/                       # Split-host template definition
├── .template.config-single/                # Single-host template definition
├── src-single/                             # Single-host overrides (Program.cs, csproj, appsettings)
│   └── UI/AditiKraft.Krafter.UI.Web/       #   Overlaid into src/UI/ during template generation
├── aspire-single/                          # Single-host Aspire AppHost override
│   └── AditiKraft.Krafter.Aspire.AppHost/  #   Overlaid into aspire/ during template generation
├── Agents.md                               # Template developer instructions
├── Agents.split.md                         # Renamed to Agents.md in split-host output
├── Agents.single.md                        # Renamed to Agents.md in single-host output
├── AditiKraft.Krafter.Dev.slnx             # All projects (template development)
├── AditiKraft.Krafter.slnx                 # Split-host solution (template output)
├── AditiKraft.Krafter.Single.slnx          # Single-host solution (template output)
├── AditiKraft.Krafter.Templates.csproj     # NuGet template packaging
└── pack-and-install.cmd                    # Local pack + install helper

# Split-host solution (default)
dotnet run --project aspire/AditiKraft.Krafter.Aspire.AppHost/AditiKraft.Krafter.Aspire.AppHost.csproj

# Single-host solution
dotnet run --project aspire-single/AditiKraft.Krafter.Aspire.AppHost/AditiKraft.Krafter.Aspire.AppHost.csproj

# Pack the template
dotnet pack AditiKraft.Krafter.Templates.csproj -o ./nupkg

# Install from local pack
dotnet new install ./nupkg/AditiKraft.Krafter.Templates.*.nupkg

# Create test projects
dotnet new krafter -n TestApp -o ../TestApp
dotnet new krafter-single -n TestSingle -o ../TestSingle

• Follow the coding conventions in Agents.md and the relevant sub-project Agents.md files
• Open changes through a Pull Request
• Use Conventional Commits

feat(scope): add new feature
fix(scope): fix bug
docs(scope): update documentation
refactor(scope): refactor code
test(scope): add tests

• License: MIT — see LICENSE
• Documentation: Agents.md
• Issues: GitHub Issues
• Discussions: GitHub Discussions

Acknowledgments

• .NET Team - For the amazing .NET platform
• Radzen - For the excellent Blazor components
• Refit - For the type-safe REST client
• NUKE Build - For the build automation framework