Give architecture, change and operations the same working model — with the roles, reviews and evidence a regulated organisation needs to stand behind it.
Meridian is built around the model, not the picture. That means the same structure can be reviewed, traced and exported — and it stays true when the next person opens it.
Capabilities in a spreadsheet, applications in a CMDB, standards in a wiki and the argument in a slide deck. None of them agree.
A diagram is circulated, comments arrive in three formats, and the decision is made in a meeting nobody can reconstruct later.
When audit or procurement asks why a system exists, the answer is rebuilt by hand from whoever still remembers.
A single capability, application and data library that every map draws from. Change it once, see it everywhere.
Editors propose, reviewers comment, admins publish. The state of every model is visible without a meeting.
SAML and OIDC on Business and Enterprise, with SCIM provisioning and group-based access.
Every node, edit and export is attributable. Trace a brief back to the model it came from.
Export the map, the PlantUML source, the brief and the revision history as one decision record.
Set how long workspaces, comments and exports are kept. Regional tenancy available on Enterprise.
For a delivery team finding its shape.
Minimum three seats.
For an architecture or change function.
Minimum five seats. Annual billing available.
For regulated organisations at scale.
Priced with your platform and support requirements. AI-training exclusion is written into the contract.
Per-seat pricing. Annual rates shown as an effective monthly rate. Team requires three seats; Business requires five.
“The value is not the diagram. It is that the diagram, the brief and the audit evidence all come from the same place.”
Start with a team workspace. Add governance when you need it.