Studio

Studio · Preview

Model your domain before you build it

Studio is a shared place to design, visualize, and edit Screenplay event models: the commands people issue, the events they produce, and the read models people look at. Studio is a paid Preview product at app.cratis.studio. Public sign-up is not open yet. Contact Cratis through cratis.studio with questions about access.

Experimental application generation

Stage, Scene, and Prologue remain experimental and in early development. The stable path for building applications today is Arc and Chronicle directly.

Design before you build

Teams often write the code first and discover the domain afterwards. By the time everyone agrees on what “an order” is, half of it has been built around a different idea. Event modeling turns that around: you map out what happens in the system as a shared picture before anyone commits to an implementation.

Studio is meant to be the canvas for that conversation, where developers, domain experts, and product owners work on the same model instead of trading diagrams.

What Studio works with

Event brainstorming

Boards for a digital Event Storming session: collect ideas and find the events that drive your domain.

Event models

Commands, events, and read models organized into modules, features, and slices, stored as a Screenplay model.

Projections

Which events feed which read model, visible in the model itself.

Agents over MCP

An organization’s agents can read and change its event models through Studio’s own MCP server.

Rendering a model into a running application is Stage’s job. Stage remains experimental, so treat generated output as something to review, not as finished production code.

Where it fits

Studio is an independent top layer. You can use it to model an event-driven system without adopting the rest of the stack. With the Cratis Stack, the model describes the commands, events, and projections you build with Arc and Chronicle.

🎛️ Studio Preview Design and edit Screenplay event models → 🧩 Components React UI toolkit wired to your typed backend → 🏛️ Arc Full-stack CQRS framework — backend to React, typed → 📜 Chronicle The event sourcing engine at the core → 🧱 Fundamentals Shared building blocks for .NET and TypeScript →

Studio sits at the front of development: design and agree on the model there, then build. To inspect and operate a system that is already running, use the CLI and the Chronicle Workbench.

What you can use today

• Studio is a paid Preview product at app.cratis.studio. Public sign-up is not open yet; contact Cratis through cratis.studio about access.
• Write a model as text with Screenplay, which Studio edits.
• New to event modeling? Read Event modeling and work through the Chronicle tutorial.
• Model the Cratis way by hand with vertical slices and modeling events.