coArchi gives a team version-controlled collaboration on a shared Archi model, backed by Git: commit, push, pull, and a merge step when two people have touched the model since the last shared commit. CelinQ takes a different path — the same local-first, semantic sync architecture that already serves Sparx Enterprise Architect, now extended to Archi. The full narrative account is here. This page is the short, structured version.
Dimension by dimension
| Collaboration architecture | coArchi: Git-backed — commit, push, pull, merge, the same model a code team already uses. CelinQ: local-first — a background service exchanges changes continuously; no commit step. |
|---|---|
| Reconciliation level | coArchi: file-level — Git's merge machinery reconciles the serialised .archimate XML. CelinQ: model-level — Fusion reconciles by what an element or relationship means, not by comparing file text. |
| Workflow required | coArchi: commit-and-pull discipline, a Git remote to maintain, conflict resolution inside Archi's own merge UI. CelinQ: none of the above — sync happens in the background without an explicit step. |
| Conflict handling | coArchi: Git merge, with Archi's own UI for resolving what Git flags as conflicting. CelinQ: CelinQ Fusion's deterministic three-way merge at model-fact granularity, with tombstones for deletions. |
| Offline operation | coArchi: works offline between commits, same as any Git workflow. CelinQ: works offline as normal editing; changes synchronise when a connection returns. |
| Revision history | coArchi: full Git commit history. CelinQ: an ordered revision history per workspace, with a Control Plane view of open Fusion decisions. |
| Infrastructure required | coArchi: a Git remote (GitHub, GitLab, self-hosted, or similar) the team already has or can stand up cheaply. CelinQ: a CelinQ Server your organisation runs. |
| Tool interoperability | coArchi: Archi only. CelinQ: the same server and Fusion engine also serve Sparx Enterprise Architect — one shared workspace for both tools. |
| Governance & RBAC | coArchi: whatever the Git hosting platform provides (branch protection, PR review, etc.). CelinQ: workspace roles (Viewer/Editor/Administrator/Owner) enforced server-side on every call, plus an audit log. |
| Documentation | coArchi: none built in. CelinQ: a built-in generator produces a searchable static documentation portal from the workspace. |
| Maturity | coArchi: an established, widely used part of the Archi ecosystem. CelinQ's Archi client: real and independently verified against a live server, but newer than CelinQ's EA integration — Smart Sync's background cadence is not yet ported to Archi (sync is manual-trigger today). |
| Best fit | coArchi: teams already fluent in Git, comfortable with a commit-and-pull workflow, working in Archi only. CelinQ: teams who want collaboration to feel invisible, teams mixing Archi with Enterprise Architect, or teams who want the same governance and merge engine across both tools. |
When coArchi may be the better choice. If your team already lives in Git for everything else, has Git-fluent architects, and is comfortable with a commit-and-pull rhythm, coArchi is a legitimate, low-friction, purpose-built answer — introducing a second server and a different sync model is a real cost that has to earn its place. coArchi is also the simpler choice for an Archi-only team with no Enterprise Architect side to reconcile with.
Go deeper
Archi Was Built for One Editor at a Time
What Archi's core actually is, what coArchi solves, and what's left.
CelinQ for Archi: One Server, Two Modelling Tools
The real, verified cross-tool proof — and the honest limits of where it stands today.