About
One model, every view
Archyno is a browser-based modelling tool for UML, ArchiMate, BPMN and ER. It is built around a single metamodel rather than a drawing canvas, which is the difference between a diagram that is checked and a picture that is merely drawn.
The metamodel is the product
Most diagram tools store shapes and lines. Archyno stores elements and relationships, and draws the shapes from them - so the same component appears in a class diagram, a deployment diagram and an ArchiMate layered view as one element with one name, not three copies that drift apart the first time somebody renames it.
The rules engine refuses illegal diagrams
UML 2.5.1, ArchiMate 4 and BPMN 2.0 each define which relationships may join which elements. Those constraints are loaded from the specifications rather than approximated, so an ArchiMate access relationship cannot target an active element and a BPMN sequence flow cannot cross a pool boundary. The palette offers what is legal; it does not offer everything and hope.
AI that proposes rather than invents
Generation is constrained by the same rules engine. The model ranks candidate relationships the engine has already filtered to the legal ones, so what comes back is a diagram the specification permits. An assistant that produces plausible-looking invalid notation costs more time than it saves.
Exports architects are actually asked for
PNG, SVG and Mermaid for the pull request; XMI and the ArchiMate Exchange format for the tools that expect a standard; Sparx .qea for the repository somebody else already maintains. Interoperability is a feature rather than an afterthought, because a model locked inside one vendor's file format is not an asset.
Open a template and change it
Nothing to install and no account for the first diagram.
Browse templates