There are already very complete enterprise architecture suites, and one deep, venerable modelling tool. Between the two, most organisations in fact map their systems in a drawing tool, a spreadsheet and three slide exports. That works on review day. It lies three months later.

Cartano aims at the missing middle: the rigour of a repository without the cost or the sales cycle of an architecture suite, and data in the front row — the angle that neither the suites nor the drawing tools cover.

Three positions taken

The repository is the source of truth; diagrams are views. Never a piece of data that exists only in a drawing. It is demanding at data-entry time, and it is what keeps a map true.

A check that can say nothing about a case must not say "conforming". Our 89 issue codes are recomputed on every read, never stored — so never stale. That is what makes a modelling agent verifiable: it gets a mark, not an opinion.

The way out must be proven, not promised. The exchange format is documented, the export covers the whole workspace, and the round trip is verified by our tests. A vendor who makes your data hard to take back has a hold on you — we would rather keep you for other reasons.

What Cartano does not do

We say it on the pricing page, and we say it again here because it determines whether the tool suits you today:

• No connectors. The repository does not synchronise from ServiceNow, Azure or a CMDB. The way in is a file or data entry.
• No collection campaigns. Having hundreds of records confirmed by their owners, with reminders, is not tooled for.
• No business library. You start from your taxonomy, which the meta-model lets you extend without development.

If your first need is to synchronise an existing inventory, an architecture suite will serve you better. If your problem is that your models are neither consistent, nor verifiable, nor exportable — that is our subject.

Our first customer is us

We map our own system in Cartano: servers, domains, services, data models. That use flushed out two product gaps before a customer saw them. An architecture tool whose own vendor does not use it is a tool whose friction nobody has measured.

The publisher

Cartano is published by Ecobeez Consulting on the Centaur Cortex platform, which carries the authentication, hosting and billing shared across our products. Hosting is in France, at OVH.