Support, advisory and workshops
Depend on it with someone behind you.
The software your business runs on is open source and always will be. A support plan isn't access to the software — it's an ongoing relationship with the people who build it, and a written answer to the questions your architecture review will ask.
First, the question you were going to ask anyway.
What happens if you stop?
The software your business runs on is open source and public. It sits on your own infrastructure, works with the systems you already have, and there is no licence to renew, nothing phoning home, and no proprietary format holding your data.
Cratis Studio is the one exception, and we would rather tell you here than have you find out later: it is a product you pay for, so it is the part that would go. What your team designed in it comes out with you, and the software it produced keeps running — so what you would lose is the shared design surface, not your systems.
If Cratis ceased to operate tomorrow, you would keep the rest — the software, the data, and the right to continue it yourself. Nothing to renew, nothing to migrate off.
Every support plan additionally guarantees a ninety-day wind-down with handover documentation.
We think that makes us a lower-lock-in choice than most vendors ten times our size. It's certainly a more honest one.
Support plans
Three tiers, priced in public.
You should be able to tell whether you can afford us without booking a call. Annual, invoiced, cancellable.
| Community | Essential | Professional | Enterprise | |
|---|---|---|---|---|
| Price | Free | €4,500/yr | €14,000/yr | from €34,000/yr |
| For | Anyone | A team putting Cratis into production | A product depending on it | Mission-critical or regulated |
| Advisory hours | — | 10 | 30 | 70 |
| Response, critical | — | 2 business days | 1 business day | 4 business hours |
| Critical incidents | — | 2 | Unlimited | Unlimited |
| Design questions | Discord | 5 / yr | Unlimited | Unlimited |
| Private channel | — | ✓ | ✓ | ✓ |
| Private issue board | — | — | ✓ | ✓ |
| Named architect | — | — | — | ✓ |
| Onboarding session | — | 1 hour | 2 hours | Half day |
| Workshop day included | — | — | 1 | 2 |
| Quarterly model review | — | — | — | ✓ |
| Roadmap input | Public | Public | Prioritised | Prioritised + briefing |
| Continuity clause | — | ✓ | ✓ | ✓ |
What "advisory hours" means
Not just fixing things when they break. Design reviews, second opinions before a decision gets expensive to reverse, migration planning, and the architectural questions that keep people awake.
What a critical incident means
Something is broken in production and it is our software's fault. Response times are measured to a real human answer — not an automated acknowledgement.
Advisory
Get the model right the first time.
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
€25,000
- One real, production-grade piece of your system, built alongside your team
- The pattern everything after it copies
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 modelling 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.
The software your business runs on is open source and developed in public. It sits on your own infrastructure and works with the systems you already have. There is no licence to renew and no proprietary format holding your data. If we stopped tomorrow, you would keep everything you are running and the right to continue it yourself — Cratis Studio, where your team designs, is the one part that would go, and what you designed in it comes out with you.
That is a stronger position than most teams have with most vendors, and it is deliberate. Support plans additionally include a ninety-day wind-down with handover documentation.
We are small, and we intend to stay small enough that you can always reach the person who wrote the code.
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.
Organisations 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?
Concretely: the software your business runs on is open source and public, it sits on your infrastructure, and it works with the systems you already have. The one thing we charge for is Cratis Studio — where your team designs, not what keeps your business running — and what you design in it comes out with you. You can leave whenever you want. We would rather you did not want to.
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.
That last one is read-only by design. An assistant can look, but changing anything still goes through the same path as everything else. The record stays honest.
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.