What's supported at v1.0
Concrete commitments per diagram type. No "we support UML" with asterisks hidden behind the marketing copy. If it's on the green list, it works as advertised; if it's amber, the page says exactly what's different; if it's deferred, you know it's not in the box yet.
UML 2.5.1
| Diagram type | Status | Notes |
|---|---|---|
| Class | Full | Nested classifiers, generalisation sets, ball-and-socket, association classes, qualified + n-ary associations. |
| Component | Full | Ports, provided/required interfaces, assembly connectors. |
| Package | Full | Package import / merge, profile applications, nested packages. |
| Use Case | Full | Actors, subjects, «include» and «extend» relationships. |
| Activity | Full | Swimlanes, structured activity nodes (sequence, conditional, loop, expansion, interruptible region), pins, clauses. |
| State Machine | Full | Composite states, all pseudostates, internal transitions. |
| Sequence | Full | Lifelines, combined fragments, state invariants, continuations, coregions, gates, duration / time constraints, local attributes. The deepest UML coverage in the tool. |
| Object | Partial | Works via the Class diagram with an «instance» stereotype. A dedicated name : Classifier slot syntax is post-launch. |
| Composite Structure | Partial | Component + Port + Connector cover most cases. Collaborations and Roles are user-composed via stereotypes, not first-class. |
| Deployment | Partial | Nodes and Artifacts render. The «device» / «execution environment» stereotype gallery is user-authored; the 3D-box modulation is not applied (flat rectangles instead). |
| Profile | Deferred | Not a diagram type. Profile authoring lives in the Stereotype editor on the Property Panel. |
| Communication | Deferred | Auto-sequence-numbering not implemented. Sequence diagrams cover most use cases at launch. |
| Timing | Deferred | No timeline renderer. |
| Interaction Overview | Deferred | Activity-flow embedding of Interaction frames not implemented. |
ArchiMate 3.1
Seven layers, all first-class. Spec-verified element coverage on 28 May 2026 against the ArchiMate 3.1 standard.
| Layer | Status | Elements |
|---|---|---|
| Business | Full | 13 elements: Actor, Role, Collaboration, Interface, Process, Function, Interaction, Event, Service, Object, Contract, Representation, Product. |
| Application | Full | 9 elements: Component, Collaboration, Interface, Function, Interaction, Process, Event, Service, Data Object. |
| Technology | Full | 13 elements: Node, Device, System Software, Collaboration, Interface, Path, Communication Network, Function, Process, Interaction, Event, Service, Artifact. |
| Motivation | Full | 10 elements: Stakeholder, Driver, Assessment, Goal, Outcome, Principle, Requirement, Constraint, Meaning, Value. |
| Strategy | Full | 4 elements: Resource, Capability, Course of Action, Value Stream. |
| Physical | Full | 4 elements: Equipment, Facility, Distribution Network, Material. |
| Implementation & Migration | Full | 5 elements: Work Package, Deliverable, Implementation Event, Plateau, Gap. |
All 11 ArchiMate relationship types render correctly: composition, aggregation, assignment, realisation, used-by, access, influence, triggering, flow, specialisation, association.
Cloud profiles
Cloud-deployment notations ship as stereotype profiles on top of UML Component + Package — the same machinery that future BPMN, C4, or domain-specific notations will use.
| Profile | Status | Notes |
|---|---|---|
| AWS | Full | Containment hierarchy (Region, VPC, Availability Zone, Subnet) with tagged-value slots. Service catalogue with official icons. |
| Azure | Full | Containment hierarchy (Subscription, Region, Availability Zone, Resource Group, VNet, Subnet) with tagged-value slots. Service catalogue with official icons. |
| GCP | Deferred | Post-launch as a profile pack. |
Deferred to post-launch
BPMN
Not shipped at v1.0. Use UML Activity diagrams for business-process modelling — swimlanes, structured activities, decisions, and parallel flows cover most BPMN use cases. A BPMN profile pack is planned post-launch.
C4 (Context / Container / Component / Code)
Not shipped as a dedicated notation. UML Component diagrams with stereotypes serve as a C4-alike substitute today. Architects who want strict C4 conventions are well served by Structurizr; architects who want a richer modelling environment use UML+stereotypes in EOModeller. A C4 profile pack is planned post-launch.
SysML, NIEM, TOGAF Content Framework, others
No commitments at v1.0. The stereotype + profile system is the path — any of these can ship later as profile packs on the same metamodel substrate, without schema changes.
Why this list exists
Most modelling tools claim "UML 2.5.1" or "ArchiMate 3.1" support and leave the gaps for the architect to discover during evaluation. We publish this page so the gaps are visible up front. If something you need is in the "deferred" column, tell us — your input shapes what we ship next.