One living model.
Catio now builds one living model of your architecture and the business it supports, from what you already have, continuously evolved. Diagrams draw themselves from it, and every blueprint carries its own.
What this means for you
One model that every answer is checked against.
Instead of a pile of facts, Catio keeps a connected, living model: which business goals depend on which services, and which services run on what. Answers, diagrams and blueprints all read from the same model, so they agree with each other and with what is actually running. It is the foundation every decision runs on.
A diagram of the change, in every blueprint.
Every blueprint now shows the change it proposes as a diagram: green for what is new, amber for what changes, gray for what stays. Share it with a link you can switch off, or export a PDF, so a decision can travel to the people who need to make it.
The model stays current without anyone redrawing it.
When something changes in your cloud accounts or your code, the model changes with it, and the diagrams follow. Nothing is drawn by hand, so nothing goes stale in a drawer.
- One living model of your business, software and infrastructure, built from your cloud accounts, source code, documents and usage data.
- Diagrams draw themselves from the model, in two views: what the system does, and what it runs on.
- Every blueprint carries an interactive diagram of its change, color-coded, shareable by a revocable link, exportable as a PDF.
- Stacks render faster and, since late September, say in plain words what each component does.
One living model
Catio reads what you already have, your cloud accounts, your source code, your documents, your invoices and usage, your network logs, and turns it into one connected, living model: business goals at the top, the software that serves them, and the infrastructure it runs on. Stacks, Blueprints and Archie all read from that one model.
A list of facts cannot tell you what breaks when a database goes down, or which business goal a service serves. A connected model can, and because it is rebuilt from your sources, nobody keeps it up to date by hand.
Under the hood
The knowledge base moved from a store of loose facts to a connected, multi-layer model of business, software and infrastructure, which is what lets Archie reason about how things interconnect rather than retrieve facts one at a time.
Source code ingestion is in beta: Catio reads your repositories to ground what it knows about a service in what is actually built.
Read more: Docs: the Architecture Knowledge Base
Diagrams that draw themselves
Diagrams generate themselves from the living model. In Stacks, the Functional View shows what your system does, grouped by product; the Infrastructure View shows what it runs on. Archie can trace a business flow through the model on request; the views do not draw flows as diagram entities. Since September 22, pointing at a component in Stacks says in plain words what it does, not only what it is.
Hand-drawn diagrams are wrong the week after they are made. Generated ones cannot drift from the system, and the two views let an executive and an engineer look at the same thing and each see what they need.
How it works, in one lineThe Functional View is generated from what your live software and infrastructure do, as the model tracks it; the Infrastructure View from the runtime, code and cloud layers.
Read more: Docs: Stacks
A blueprint you can hand to someone
Every blueprint now carries an interactive diagram of the change it proposes, color-coded: green for new components, amber for changed ones, gray for what stays. A blueprint can be shared with a link limited to your workspace, to everyone in your organization, or to anyone with the link, and the link can be switched off at any time. It can also be exported as a PDF; since September 25 the PDF includes the diagram and its legend.
You told us text alone does not work for the people who sign off. The diagram shows the change at a glance, the link brings a reviewer straight to the live blueprint and its comments, and the PDF goes where links cannot.
Read more: Docs: Blueprints
What we measured, and what we did not
More ways to look at the model
- Hover descriptions and click-through on blueprint diagrams.
- Diagram export to Draw.io and Visio for editing off-platform.
- A diagram that overlays a proposed change on the existing architecture.
- Tags and naming conventions on components, so the model can be sliced the way your organization is.
Elsewhere in the console this month
- Sep 25The PDF export of a blueprint includes the diagram and its legend.
- Sep 24Blueprint diagrams read relationship subtypes from the component library and label grouped edges.
- Sep 22Stacks say what a component does, not only what it is.
- Sep 16Stacks render faster.
- Sep 02Blueprint export to PDF.
- Aug 25Diagram generation: every blueprint gets a diagram of its change, color-coded for new, changed and unchanged.
- Aug 23Conversations no longer scan the whole account first: the slowest opening steps went from minutes to seconds.
- Aug 14Blueprint sharing: links scoped to the workspace, the organization or anyone, revocable at any time.
- Aug 11Saved views: filters reload as saved.
- Aug 11Architecture Inventory: browse and search every component.
- Aug 05Integration runs no longer fail when Catio's own credentials rotate.
- Aug 04Attached diagrams and images are read by a stronger vision model.
- Jul 31A new onboarding flow.
Want to see it on your own system? Book a demo