Software, built for the era after AI changed everything.
Large language models put software development at a genuine fork in the road. Cratis Studio is our answer to which way we chose to go — and why.
A fork in the road
Every LLM in existence was trained on source code written by humans, for humans, accumulated over decades, at an uneven level of quality. Ask a model to write code and it doesn't converge on the best version of the craft — it converges on the average of everything it has ever seen, good and bad alike.
If you want something better than the average, prompting harder won't get you there. You need a different foundation entirely — one designed for how software should be built, not one inferred from how it happened to be built.
Opinionated, on purpose
We believe in being opinionated, and we treat taking away choices as a bit of a blessing rather than a limitation. Every unnecessary decision a developer has to make along the way is a decision that can be made wrong, made inconsistently, or not made at all.
Event modeling and vertical slices are our foundation. Backed by a platform that is opinionated from top to bottom, they give us all the building blocks we need to create a genuinely new approach to software development — one that marries decades of hard-earned practice with the latest and greatest AI has to offer.
The human, elevated
Human in the loop matters more than ever — but the loop needs to change shape. Too much of a developer's attention today goes into wiring code together: the plumbing, not the thinking.
We believe that attention belongs higher up: designing the software itself, deciding how workflows fit together, defining what actually constitutes business value, and shaping how the whole thing looks and feels to the people who use it. That is the work only a human does well. That is the work Cratis Studio exists to protect and amplify.
Event sourcing at the core
Event sourcing sits at the core of the Cratis platform — not as an optional extra bolted on the side. Any solution built on top of Cratis is event sourced, full stop. Every state change is a fact, captured once, never overwritten, always there to explain exactly how a system arrived at where it is.
Room for the code only you can write
We know we won't ever cover everything — no platform can, and we don't pretend otherwise. When the model and the generators get you most of the way there, the last stretch is often the part that makes your business different from everyone else's. Cratis Studio is built to let you drop into custom code exactly where you need it, without stepping outside the model or fighting the framework to do it.
And what gets generated has to be code you'd be proud to maintain, not a black box you're afraid to open. Readable, idiomatic, following the same conventions your team already uses — if a developer can't understand it at a glance, we haven't done our job.
Quality that runs itself
Every slice ships with living specifications, written Given/When/Then style so anyone on the team can read them — and they're not just documentation. They're runnable. Each spec is an executable test that proves the system still behaves the way it was designed to, today and after every change that follows.
That matters more, not less, once AI agents are the ones making some of those changes. Regression isn't something you hope someone catches in review — it's something the specs catch automatically, every time.
A project manager built into the model
Because Cratis Studio is built around vertical slices, it always knows exactly what state each slice is in — not started, in progress, ready for review, done. That status isn't bookkeeping bolted on afterward; it falls directly out of the model itself.
Zoom out and that status rolls up into the health of the whole project. Cratis Studio doesn't just help you build the system — it takes on a good part of the job of managing the project around it, because the tracking is a byproduct of how the work is structured, not a separate tool you have to keep in sync.
Built for many hands, human and AI alike
None of this works as a single-player experience. Multiple people work on the same model, the same slice, at the same time — the way you'd expect from any modern collaborative tool, not a file you have to check out and lock.
And it's not only humans in that room. Full chat runs through the whole platform, built for cross-pollination between the humans and the agents working alongside them — ask a question, hand off a task, get a suggestion, all in the same conversation, whoever or whatever is on the other end.
From a prompt to "press play"
Part of the vision is deceptively simple to say: start from a prompt describing the software you're trying to build, arrive at a generated event model, and press "play" — all within a couple of minutes. Then iterate.
AI is infused all the way through that loop. You ask for changes in plain language. You talk to specialized agents the way you'd talk to teammates — agents that can be trained to know your domain, or brought in as partners for a specific job, the same way you'd bring in a specialist today.
Democratizing event sourcing
Zooming out, our fuller mission is to democratize event sourcing itself. We believe every information system should be built this way, so that no organization ever loses valuable data — data that can unlock capabilities nobody has imagined yet, and data that can train the machine learning models that help you reach your business goals, faster.
This is the vision we're building toward, one release at a time. We'd love for you to be part of it.
Einar Ingebrigtsen
Co-founder, CTO
Sindre Wilting
Co-founder, Chief Architect