Skip to content
Cratis Cratis Cratis

Studio

Studio · Coming soon

Model your domain. Ship with confidence.

Design before you build

Section titled “Design before you build”

Most teams write the code first and discover the domain later — by the time everyone finally agrees on what “an order” really is, half of it is already built the wrong way. Event modeling flips that around: you map out what happens in the system — the commands people issue, the events those produce, the read models people look at — as a shared picture, before committing anyone to an implementation.

Studio is the canvas for that conversation. Developers, domain experts, and product owners shape the same living model together, in real time — no merge conflicts, no stale diagrams rotting in a wiki.

What Studio will do

Section titled “What Studio will do”
Event Brainstorming

Run a digital Event Storming session — drop sticky notes on an infinite canvas, cluster ideas, and discover the events that really drive your domain.

 Event Modeling

Lay out commands, events, and read models on a collaborative timeline, and visualize every state change in your system before you write a line of code.

 Read model projections

Connect events to read models on the canvas, so everyone can see exactly which events feed every projection — by design, not by archaeology.

 Team collaboration

Invite developers, domain experts, and product owners to edit the same model in real time. One shared source of truth, always current.

 Code generation

Generate type-safe C# commands, events, and projections directly from your model — so your design and your Cratis codebase stay perfectly in step.

 Spec-driven development

The model is the spec. Start from a shared design, generate the slices, and build on a foundation the whole team already agreed on.

Where it fits

Section titled “Where it fits”

Studio is an independent top layer — a design surface you can use on its own to model any event-driven system. Used with the Cratis Stack, it closes the loop: the commands, events, and projections you model become the type-safe C# you build on with Arc and Chronicle.

Studio Coming soon Visual control room for your event-sourced system Components React UI toolkit wired to your typed backend Arc Full-stack CQRS framework — C# to React, typed Chronicle The event sourcing engine at the core Fundamentals Shared building blocks for .NET and TypeScript

It’s the front of the development funnel — design and align in Studio, generate the slices, then build them out. To inspect and operate a system that’s already running, you reach for the CLI and Workbench instead.

Until then

Section titled “Until then”