Cratis Studio
Where your team designs the software together.
Most software gets designed in one room and built in another. Studio puts everyone in the same room — the people who know the business and the people who build it — around one picture of how the business works. Then it runs that picture, so what you agreed on and what your customers use are the same thing.
In beta Free trial, no card Your model exports
Why this now
Machines write a growing share of your software. They build what they are told.
An assistant is only as good as the description it works from. Give it a vague plan and it produces vague software, faster than anyone can review it. The bottleneck has moved: it is no longer how quickly you can write software, it is how precisely you can say what you want.
The plan lives in a document
Someone writes it down, someone else interprets it, and the distance between the two only shows up months later in something that shipped wrong.
The plan is the thing that runs
Your team designs how the business behaves, and that design is what executes. There is no gap between them to drift, because there is no second copy.
Speed stops costing you control
People and assistants work from the same explicit description instead of guessing at it — so going faster stops meaning accumulating things nobody can explain later.
How it works
From a conversation to something running.
You do not need to know how any of this is built to take part. That is the point.
Get it out of people's heads
Everyone who knows part of how the business works puts it on one canvas — what people do, what happens as a result, what everyone needs to see. In business language, not technical notation.
Shape it together, at the same time
Product people, domain experts, designers and engineers work on the same model at once — the way you would expect from any modern collaborative tool. Disagreements surface on the canvas, where they are cheap, instead of in production.
Press play
Studio turns the model into something that actually runs, so your team can use it and react to it rather than imagine it. Being wrong on a Tuesday afternoon is much cheaper than being wrong after a quarter of building.
Change it and go again
What you learn from using it goes straight back into the model. The loop is the work — not a phase that happens once at the start and never survives contact with reality.
What changes
What your organisation gets out of it.
More of your people can take part
Today the final say on what the software does is the code, which most of the people who understand the business cannot read. Studio moves that to something everyone can read, question and change — so the knowledge that shapes your software is not locked inside one department.
Design stops being engineering-onlyLess gets lost on the way
Every handoff between an idea and working software is a translation, and every translation loses something. Designing and running from one model removes most of the handoffs outright.
Fewer surprises at the endYou find out sooner
Because the model runs, the people who will live with a decision can try it before it is built for real — customers included. Feedback arrives while changing your mind is still cheap.
Cheaper mistakes, earlierDelivery gets more predictable
Studio knows what state each piece of work is in, because that falls out of the model rather than out of someone updating a board. Less ambiguity between what was intended and what arrives.
Status you don't have to maintainThe record keeps itself
Anything built this way records every business decision as it happened, permanently and in order. When someone asks how you got here — an auditor, a customer, a board — answering is a question you ask the system.
Audit becomes a query, not a projectThe honest part
Where Studio is today, and where it isn't.
We would rather you knew this before you spent an afternoon on it.
It is in beta, and that means something
Features arrive often and some of them move. Parts are labelled preview. We are still building toward the full loop, and we would rather say that than let you discover it. What is not in beta is how we treat your work: continuous backups, tested restores, and your organisation's content kept separate from everyone else's.
Pricing may still change
It is published rather than quoted, and it is per person. Prices during beta are current but not frozen — we commit to telling administrators at least thirty days before any increase, and we are actively asking early customers whether we have it right.
It will not cover everything
No tool covers a whole business, and the last stretch is usually the part that makes you different from everyone else. Studio is built to let your engineers drop into ordinary code exactly where that is needed, without leaving the model behind.
When it is the wrong fit
If your teams already design together well and nobody is asking questions the system cannot answer, you may not need this. It earns its keep where several people have to agree on how something works before it gets built — and where being wrong about that is expensive.
What it costs
Free to try. Then per person, published.
Start without talking to us
Create an organisation and the first administrator gets a trial seat with full access — no card, no call, no demo booked before you can look. After that, each person who needs access holds a seat, bought in the quantity and billing cycle you choose, at prices shown before you confirm.
Current prices are on cratis.studio.
What you keep
What your team designs stays yours and comes out in a format you can take elsewhere. If the last seat lapses, your organisation's content is held for thirty days so an administrator can export it or come back.
Why this one is paid
The software your business runs on is open source and always will be — you can read every line of it, and it keeps running whether you work with us or not. Studio is the hosted product around it, and it is what funds the rest staying free. How we draw that line →