ArchiMate® modelling,
inside Confluence
Arkidor for Confluence lets your team author and embed ArchiMate architecture diagrams directly inside Confluence Cloud. Models live as page attachments in your tenant — no external storage, no separate account.
Atlassian Confluence is a widely used team workspace where organisations write documentation, plan projects, and keep their shared knowledge — a natural home for the architecture models themselves. Arkidor brings full ArchiMate modelling into that workspace, so diagrams sit alongside the documentation that explains them. And because ArchiMate is a proper model, the same elements, relationships, documentation, and links can be reused across many views instead of redrawn — describe something once, show it wherever it's relevant.
ArchiMate 3.2 & 4.0
Full notation support — elements and relationships — powered by the same Arkidor editor.
Runs on Atlassian, data in your tenant
Built on the Forge platform — no separate server to manage. Each model is stored as page attachments inside your own Confluence space: your data, your permissions, and it survives uninstall.
Embed views anywhere
Place view embeds on any Confluence page from any model in your site. Extra element detail is shown in a table or on hover — configurable per embed — with the full model just one click away.
See where it's used
For each model you get a list of referencing pages, so you can see exactly where the model is used across your site.
Version history
Every published version appears in the model's History tab, with who published it and when. Draft saves aren't listed — only published versions are.
Open format, no lock-in
Models are always stored as standard ArchiMate Open Exchange Format (OEF) XML — the same file can be opened directly in any ArchiMate-compatible tool, such as Archi, Sparx EA, BiZZdesign, or ADOIT.
Your models stay in your tenant
We don't operate a separate database for your model content. Here's what actually happens:
- Models are stored as page attachments inside your Confluence tenant, always as standard ArchiMate Open Exchange Format (OEF) XML — an open standard you can open directly in any ArchiMate-compatible tool.
- Saves happen as you, using your own Confluence session — version history shows your name.
- Attachments survive uninstall — they're yours, not ours, and remain readable without Arkidor.
- The only external egress is error telemetry to Sentry (EU region), cleaned on your device before sending. It is designed to exclude model content and page titles (client-side, best-effort scrubbing) and contains no names or email addresses; technical identifiers such as page, space or model IDs may appear in diagnostic messages. See the Security Policy for exactly what is sent.
Why this matters for governance: because your models live inside your own tenant and never move to a separate Arkidor system, they already fall under the Confluence data-governance, access controls, and residency policies you have in place — there's no new data store to assess. And because the data is an open, standard format rather than a proprietary one, it stays portable, auditable, and readable independently of any single vendor.