Why Cratis

Choose the part that solves your problem.

Cratis fits teams that need to explain business history, keep backend and frontend contracts in step, or make expected behavior explicit. Chronicle preserves events; Arc provides typed commands and queries with or without event sourcing. Each brings modeling or operational costs. Here's what changes, what doesn't, and when to choose less.

Is Cratis right for you?

Start in an existing system or compare the products and their limits.

What changes day to day

Instead of… you work with…

What changes when you adopt Cratis
Instead of You work with
Duplicating request and response shapes in C# and TypeScript One C# command or query model, generated into typed frontend proxies
Spreading one feature across controllers, handlers, clients and UI folders A vertical slice organized by behavior
Rebuilding screens by hand after a write Observable queries and components that follow the read model
Rebuilding authentication, tenancy and identity plumbing per service AuthProxy at the edge, Arc identity and tenancy inside, Chronicle namespaces underneath
Teaching every developer and assistant a project-specific architecture Strong conventions, analyzers and .ai guidance that make each feature look like the rest
Locking event history to one language or database engine An open, documented boundary, with language and database coverage stated by product and version
Debugging from logs alone Events, observers, and read models visible in current tools; replay is a deliberate operational action in supported CLI and Workbench versions

The four things we'd defend

What we actually claim.

01

One model, end to end

The point isn't that Cratis has many packages. It's that the packages agree about how an application is shaped. A command, an event, a read model, a tenant, an identity, a React form and an operating tool are parts of one model — not islands with separate conventions. That agreement is what takes the friction and repetitive work out of the day-to-day: one set of conventions to learn, and every feature shaped like the last one.

02

A history you can question

Event sourcing optimizes for understanding change, not storing the latest value. Events are facts: immutable, past-tense, single-purpose. Read models are disposable, because the events are the source of truth. That makes new views possible from recorded history, but requires deliberate event design and operational care.

03

Rails an agent can follow

Cratis AI provides framework guidance, analyzers catch supported convention violations, and Chronicle MCP exposes a running store to an assistant. Cratis Direct adds journeys, gates and recorded evidence to govern agent work. These checks support engineering review; they do not establish correctness on their own.

04

Public Build source and documented boundaries

Cratis Build is developed in public under the license stated by each repository. Chronicle has an open, documented boundary, while client and storage coverage varies by product and version. See the support matrix for storage, clients, hosting and maturity. Chronicle can be used without Arc, and Arc can be used without event sourcing.

When assembling parts

Choose the smallest boundary that solves the real problem.

A focused library can be the better answer. Cratis earns its keep when the expensive gaps are between design, backend, frontend, history and operations.

Choose focused parts

When the boundary is narrow

A backend-only service, one database, no shared design problem and no cross-language contract drift may not need the wider stack. Fewer moving pieces are a benefit when they solve the whole job.

Choose Cratis

When coherence is the requirement

Cratis Build joins Chronicle's event lifecycle with Arc's typed C# → TypeScript → React continuity. Workbench, CLI, and Chronicle MCP then expose documented operating workflows whose coverage varies by tool and version.

The commercial boundary

Four offers, with the line drawn plainly.

Cratis Build

Public runtime source and operating tools

Chronicle, Arc, Components, Workbench, CLI, and Chronicle MCP are developed in public under the license stated by each repository. Their documented Build capabilities do not require a Studio seat or production feature key.

Cratis Studio

Paid collaborative design

An optional paid workspace built on Chronicle for modeling together and exploring supported behavior. Sign-up is open with a 14-day free trial and per-seat pricing. Studio provides export for supported model content; available formats, retention, and later access follow the hosted product and applicable terms.

Cratis Direct

Keep agent work accountable

The control plane for agentic engineering connects intended work with delivery through journeys, gates and recorded evidence. Direct is GitHub-first and lets you bring your own model provider. It runs Cratis's own engineering; access opens in stages.

Cratis Assurance

Paid expertise and responsibility

Support, architecture review, model sprints, first slices, production readiness and founder-led workshops, subject to the signed agreement for the engagement.

Fit

When Cratis is the wrong choice.

Here is when we would point you somewhere else, and where.

You don't need an event-sourced model

Chronicle asks you to describe the system as things that happened. If that history is not useful to your feature, keep its current-state database. Arc can still provide typed commands and queries without event sourcing.

You only ever need current state

No audit trail, no “how did we get here”, no replay: storing every event may add cost without a useful return. A conventional database and an ORM may be enough. This is a limit on the case for event sourcing, not a requirement to adopt the whole Cratis stack.

You want a fully managed database

Chronicle is self-hosted. You run the Docker image and you operate it. If nobody on the team wants that job, use a managed database service from your cloud provider.

Your backend language has no Chronicle client

.NET has the first-class SDK. TypeScript/Node.js, Kotlin/Java and Elixir have clients. Go has a released client without observers or projections. Arc also documents Kotlin/Java and TypeScript backends. Check the support matrix for the features and version you need.

You need a published SLA before the first conversation

Paid support comes through Assurance, with scope and terms set in a signed agreement, not published tiers. If your buying process needs a published SLA before you talk to anyone, pick a vendor that publishes one.

On .NET and only need current state? Arc, the CQRS framework, also runs over MongoDB or EF Core without event sourcing.