Roadmap
The roadmap is directional, not a delivery contract. Cratis is open source, and priorities move when real adoption uncovers sharper needs. Treat this page as a map of intent: what you can rely on, what is being strengthened, what is experimental, and where feedback will shape the work.
Share roadmap feedback Tell us what would unblock adoption, production use, training, or contribution.
Watch what changed Read weekly release digests across the Cratis repositories.
Ask before depending on a future item Use Discord when a planned or exploratory item matters to your project.
Stable foundations
Section titled “Stable foundations”These are the core areas the documentation treats as the current Cratis foundation:
| Area | Direction |
|---|---|
| Chronicle | Event log, event types, projections, reducers, reactors, subscriptions, storage choices, hosting, CLI inspection, and testing helpers, with a first-class .NET SDK |
| Arc | Commands, queries, validation, generated TypeScript proxies, backend integrations, identity, tenancy, and CQRS without mandatory event sourcing |
| Components | Command forms, dialogs, data tables, styling, Storybook, and typed React screens over Arc proxies |
| Fundamentals | Concepts, serialization, type discovery, diagnostics helpers, and TypeScript utilities |
| Documentation | Product docs, full-stack guides, samples, API reference, Storybook, community routes, and AI-readable exports |
Being hardened
Section titled “Being hardened”These ship today and are in use, but their coverage, documentation, or guarantees are still being filled in:
- The TypeScript, Kotlin/Java, and Elixir Chronicle clients and their documentation. Not every documented workflow is available in every client yet; the client tabs on each page say which.
- Production guidance across the full stack.
- Compatibility documentation across .NET, Node, React, storage engines, and package versions, including a clearer statement of which client and kernel versions pair.
- Cratis AI rules, skills, and plugins, and the CLI’s AI command catalog.
- API reference and Storybook publishing.
- Documentation coverage for common adoption and migration paths.
- Testing guidance from unit-level specs to full workflow specs.
Model-first tools
Section titled “Model-first tools”- Screenplay is the declarative event-modeling language.
- Studio is a paid Preview product. Public sign-up is not open yet; contact Cratis through cratis.studio about access.
Experimental
Section titled “Experimental”- Model-first rendering and capture: Stage, Scene, and Prologue remain experimental and in early development; formats and behavior can change between releases.
- Developer tools in early releases: Lens, the browser extension for Arc apps.
Being explored
Section titled “Being explored”- A Python Chronicle client. It is pre-alpha and not published.
- Ensemble, deterministic expert workflows for AI agents building with the Cratis stack. It is pre-release, and free and MIT licensed like the rest of Cratis.
- Richer visual operations around a running system.
- More reference architectures and runnable sample applications.
- More workshop and training material around Cratis and event sourcing. Professional help is available today.
- A clearer RFC path for larger design proposals.
Feedback wanted
Section titled “Feedback wanted”The most useful roadmap feedback is concrete:
- Which adoption step felt risky or unclear?
- Which production question blocked a decision?
- Which tool or diagnostic would have saved time?
- Which docs page did you expect but could not find?
- Which integration would make Cratis easier to introduce in an existing system?