Cratis Templates

The Cratis Stack

Start your Cratis app with the conventions already in place

Every Cratis application follows the same conventions: vertical slices, model-bound commands and queries, events as facts, read models projected from the log. The Cratis templates give you a working application with those conventions already in place — a real project you can run in minutes, not a blank folder you fill in from documentation.

Install the .NET templates once:

dotnet new install Cratis.Templates

The Kotlin and Java templates ship as separate packages — Cratis.Templates.Kotlin and Cratis.Templates.Java — so they do not show up in dotnet new unless you want them; the Cratis CLI installs and invokes them directly when you create a JVM project.

The templates

Cratis Web Application

The full-stack starting point: ASP.NET Core with Arc commands and queries, Chronicle event sourcing, and a React frontend with generated TypeScript proxies — wired together in vertical slices.

Cratis Kotlin Application

The same full-stack application on Spring Boot, authored in Kotlin — Arc commands and queries, Chronicle event sourcing, TypeScript proxy generation through the Arc Gradle plugin, and a React frontend.

Cratis Java Application

The same full-stack application on Spring Boot, authored in Java — records as commands and read models, Chronicle event sourcing, TypeScript proxy generation through the Arc Gradle plugin, and a React frontend.

Chronicle Web

A minimal ASP.NET Core application connected to Chronicle — events in, projections out, no frontend. The smallest possible server-side starting point.

Chronicle Console

A console application that appends an event and observes it through a projection and a reactor. The shortest path to seeing Chronicle move.

Cratis Aspire

The full-stack web application, composed with .NET Aspire — the same vertical slices with an orchestrated development topology.

Note

The .NET templates reference the Cratis packages with a floating version (*), so dotnet new always scaffolds against the latest released Cratis stack. Run dotnet restore right after scaffolding to pick up the current versions, and update them later the same way you would any other package. The Kotlin and Java templates pin their verified Maven versions — Arc 7.2.0 with Chronicle 4.0.0, Kotlin 2.4.20, and Spring Boot 4.1.1 — since Gradle has no floating-version equivalent; bump them deliberately when you upgrade.

What the templates have in common

• Vertical slices — everything for a behavior lives in one folder: the C# command or query, the events it produces, the React component that calls it, and the generated TypeScript proxy.
• Model-bound by default — commands and queries are plain records the framework maps to HTTP routes; no controllers to write.
• Infrastructure included — a docker-compose.yml that starts a local Chronicle development container (with its bundled MongoDB) and an Aspire dashboard for telemetry.
• AI-ready — every template ships a .cratis/ai.json with the Cratis AI profiles, languages, and coding agent harnesses for that template. Install the Cratis CLI and run cratis ai update to get the AI rules, skills, and harness integration in place — dotnet new prints this reminder after scaffolding.
• Builds clean — the sample code compiles with zero warnings under the Cratis analyzers, so the first warning you see is your own.

Learn more

• Chronicle documentation — the event-sourcing database at the center of the stack.
• Arc documentation — the CQRS application framework the web templates build on.
• The Cratis AI skills teach coding agents these same conventions.