Cratis Assurance
Depend on it with the people behind it.
Cratis Build is open source. Assurance is not permission to use or repair it; it is direct access to the people and experience behind the stack. Use it for model decisions, adoption, production readiness, incident help and the changes that are expensive to reverse.
First, the question you were going to ask anyway.
What happens if you stop?
Cratis Build is developed in public and is intended to run in your infrastructure. It does not require a Studio subscription or a commercial feature key. Each repository states its own license, and component documentation describes interfaces and storage.
Cratis Studio is a separate hosted, paid Preview product. Build continues without it. Studio provides export for supported model content; formats, retention, and post-subscription access follow the hosted product and the terms that apply when you use it.
Public Build source and data in your infrastructure reduce vendor dependency. They do not eliminate transition work: your team would still need to plan maintenance, replacement services, and any migration appropriate to its deployment.
A support agreement can include a ninety-day wind-down with handover documentation. The signed agreement defines the applicable scope.
The practical claim is narrower: Build source is public, Studio is clearly separated, and leaving still requires an engineering plan.
Support
Ongoing support, agreed with you.
Ongoing support is available on request while Assurance is founder-led. We agree scope, advisory time, response targets and escalation with you in a signed agreement, sized to what we can actually deliver, rather than publishing tiers we would have to stretch to honour.
What support can cover
Advisory time for design reviews, second opinions before a decision gets expensive to reverse, migration planning, and help when something breaks in production and it is our software's fault.
How to start
Tell us what you run and what you need. We reply with a proposed scope and terms, or tell you plainly if we are not the right fit.
Ask about support →Assurance engagements
Get the consequential decisions right early.
The first slices set the pattern everything after them copies. Consistency boundaries are cheap to change now and expensive to change later.
Fit Review
90 minutes · remote
Free
- An honest yes or no
- If no — what we'd do instead
- No deck, no follow-up sequence
Architecture Review
1 week
€7,500
- How your system is designed, where it will strain, and what happens when something fails
- A written review with risks ranked and fixes named
Model Sprint
3 days · remote
€12,000
- A working session over how your business actually operates
- A design your whole team agrees on
- The first three pieces specified in detail
First Slice
2 weeks
Let's talk
- One real slice, built as a production-oriented pattern alongside your team
- The pattern everything after it copies
- Scope drives price — contact us and we'll figure it out together
Prologue Discovery
2 weeks
€22,000
- A map of what your existing system actually does today
- A sequenced adoption plan
AI-Ready Foundations
1 week
€9,000
- Guard rails set up so AI assistants build to your standards
- A system where people and AI follow the same rules
Workshops
The syntax is learnable in a week.
The modeling is the part
worth teaching.
Most teams don't struggle with Cratis. They struggle with deciding what an event is, where a consistency boundary belongs, and what everyone actually needs to see.
Designing Systems Together
2 days · up to 12 people
€8,500
- How to describe what your business does, in a way everyone understands
- Worked through your business, not a textbook example
Systems That Remember
2 days · up to 12 people
€8,500
- Building systems that keep a complete, trustworthy record
- What it costs, what it buys, and where it is the wrong choice
Building on Cratis
2 days · up to 12 people
€8,500
- Building a full product on the platform, end to end
- Taught by building something real together
A one-day Foundations format is available at €5,000 when two days is more than the calendar allows. On-site adds €3,500 plus travel.
When we're not the right fit.
Being direct about the limits saves everyone a meeting.
The question can be answered in public
The Discord is free, open, and usually faster.
You want a general software consultancy
We work on how systems are designed and the platform around them.
You want us to build your product
We'll build the first slice with your team and teach them the pattern. We won't be your development department.
You found a vulnerability
Use responsible disclosure instead — it's faster and it's the right channel.
Questions
You're two people. What happens if you stop?
Fair question, and the honest answer is better than the reassuring one.
Cratis Build is developed in public and intended to run in your infrastructure without a Studio subscription. Studio is a separate paid Preview product with export for supported model content. Continuing or replacing any deployed stack would still require engineering ownership and a transition plan.
A support agreement can additionally include a ninety-day wind-down with handover documentation; the signed agreement defines the applicable scope.
Assurance is founder-led today. The signed agreement defines availability, points of contact, and escalation.
Is this more than we need?
Sometimes, yes — and we will tell you when. It earns its keep wherever decisions have consequences later: payments, claims, contracts, anything an auditor or a customer might ask about. For a settings screen or a simple lookup table, it is more than you need, and the platform works perfectly well without it.
We already have something that works. Why change?
Then you may not need us, and we will say so. If what you have works, your team is productive, and nobody is asking questions the system cannot answer — stay where you are.
Organizations come to us when the design lives in a few people's heads, when the pieces have drifted apart, or when a question about the past takes a week to answer. That is the part we built.
What about lock-in?
Cratis Build source is public and the runtime is intended for your infrastructure. Studio is a separate paid Preview product with export for supported model content. Those choices reduce lock-in, but leaving still requires a maintenance or migration plan.
How does this actually help with AI?
Three specific things, not a slogan. Assistants are taught your conventions directly. Automated checks reject work that drifts off them, before a human ever reviews it. And an assistant can ask the running system what happened, in plain language.
Inspection can be read-only, but Chronicle MCP also exposes documented operational actions such as observer replay and recovery and job changes. Treat those as writes, authorize them for the environment they affect, and keep business changes on domain command and event paths.
How long is a version supported?
We are writing this down formally. Until it is published, ask us directly and you will get a straight answer about the version you are on.