Archyno

One model.
Every format.

UML and ArchiMate in the browser. Describe your system, get a diagram, ship it as PNG, Mermaid, XMI, or a Sparx .qea file.

Reduce settlement timeAccept paymentCheckout servicePayment orchestratorAuthorizeKubernetes cluster

Simplified ArchiMate layered view: a goal realized by a business process, served by an application service deployed on a Kubernetes cluster.

Drag any element - the connectors re-route as you move it.

Every view, one model

The same elements, drawn four ways. Rename one and it renames everywhere it appears.

methodamountPayment- id: UUID- amount: Money- status: Status+ authorize()+ capture()«interface»PaymentMethod+ token: string+ charge(amount)Card- last4: string- brand: Brand+ charge(amount)BankTransfer- iban: string+ charge(amount)«value object»Money+ amount: decimal+ currency: stringLedger- entries: Entry[]+ post(tx)

UML class diagram: Payment composes Money and associates a PaymentMethod interface, realized by Card and BankTransfer.

«deploy»Settle payments same day«business process»Capture payment«application service»Authorization service«application component»Payments engineeu-west-1 cluster
1..*Order- id: UUID- placedAt: InstantPayment- amount: Money- status: Status+ authorize(): AuthResultCardBankTransfer

How it works

01

Describe

Type a paragraph, drop a PDF spec, or paste a folder of code. You get a complete diagram, drawn element by element while you watch.

02

Refine

Drag, connect, rename. The tool knows which relationships your notation permits and will not let you draw the ones it forbids.

03

Export

PNG for the deck, Mermaid for the repo, .qea for whoever still lives in Sparx. Every export states what it drops before it runs.

Payment orchestratorAccept paymentServing

Suggested relationships

  • ServingThe component provides a service the process consumes.
  • RealizationThe component implements the behaviour the process defines.
  • AssociationA plain link, when neither direction is stronger.
  • CompositionNot permitted from an application component to a business process.

AI

AI that knows the notation

Suggestions are filtered by the rules engine before the model ever sees them, so it ranks legal relationships instead of inventing illegal ones. When only one is legal, we skip the model entirely.

  • Describe a system in prose and watch the diagram build itself
  • A whole-project review that finds orphans, cycles, and missing realizations
  • Documentation written into the model, not into a chat window
  • A monthly credit budget with a hard stop, never a surprise bill

The whole point

Architecture the whole team shares

One model, one project, everyone working on the same elements. Invite the team, see who is in the diagram, and hand the result to anyone outside it in whatever they actually open.

One model, many views

Elements exist once per project. Rename one in a layered view and it renames in the sequence diagram too, because they are the same element.

Invite by email, in one batch

Up to 20 addresses at a time with one role for the batch. Owner, admin, editor, commenter, viewer. Viewers and commenters never cost a seat.

See who is in the diagram

Live cursors, presence avatars, and a soft edit lock you can take over. Simultaneous co-editing lands after launch, and we say so plainly.

Honestly

Where we win, and where we do not

Sparx Enterprise Architect is twenty-five years old and does a great deal we do not. The last three rows are the ones where it beats us; a table without them would not be worth reading.

Where we win, and where we do not
ArchynoSparx EALucidchartdraw.ioArchi
UML 2.5.1, all fourteen diagram kindsYesYesPartlyPartlyNo
ArchiMate 4, all layers and viewpointsYesYesNoNoYes
One shared model behind every viewYesYesNoNoYes
Runs in the browser, nothing to installYesNoYesYesNo
Sparx .qea exportYesYesNoNoNo
XMI 2.5.1 exportYesYesNoNoNo
ArchiMate Exchange exportYesYesNoNoYes
Mermaid export for the repositoryYesNoNoNoNo
AI constrained by the notation rulesYesNoPartlyNoNo
Usable free tier, no watermarkYesNoPartlyYesYes
Code engineering across ten-plus languagesPartlyYesNoNoNo
BPMN, SysML and twenty more MDG notationsPartlyYesPartlyPartlyNo
Requirements, testing and project managementNoYesNoNoNo

Comparison reflects the shipping feature set at the time of writing. Sparx Enterprise Architect is a product of Sparx Systems; Lucidchart, draw.io and Archi are the products of their respective owners. We are not affiliated with any of them.

Pricing

Notation coverage is never the thing we charge for. Collaboration, Sparx interop, and AI usage are.

Free

One person, one project, real exports.

0EUR

Free forever. No credit card.

Start free
  • 1 project, unlimited diagrams
  • 300 elements
  • Full UML and ArchiMate notation
  • PNG and SVG export, no watermark
  • Undo 100 steps deep
  • 150 AI credits a month
  • AI constrained by the notation rules
Most popular

Individual

For a consultant or an engineer buying their own tools.

204EUR/ year

240 · 17 EUR a month

Billed once a year, excluding VAT

Coming soon

  • 5 projects
  • Unlimited elements
  • Share one project with 3 people
  • PDF, Mermaid, XMI, ArchiMate Exchange
  • Code generation and reverse engineering
  • 2,000 AI credits a month
  • 90 days of version history

Team

For an architecture team with a Sparx handoff.

1020EUR/ year

1200 · 85 EUR a month

Billed once a year, excluding VAT

Coming soon

  • 20 projects, extendable in packs
  • Every project collaborative
  • Full five-role model
  • Sparx .qea, .qeax, and draw.io export
  • Viewers and commenters are free, always
  • 4,000 AI credits per editor, pooled
  • Unlimited version history, API access

Paid plans are not open yet. The Free tier is live and needs no card.

Questions

Does it really export to Sparx Enterprise Architect?

Yes. A .qea file is a SQLite database carrying EA's repository schema, so we write real rows into real EA tables rather than generating XML. You get model and geometry fidelity, not repository fidelity: scripts, baselines, diagram themes, and MDG technologies beyond ArchiMate3 do not transfer, and the export dialog says so before it runs.

Is this just another diagramming tool?

No. Archyno is a model repository. Elements and relationships exist once per project and diagrams are views onto them, so renaming an element in one view renames it everywhere. That separation is what makes real XMI and .qea export possible instead of a reconstruction from pixels.

Will my layout survive an XMI export?

Model structure transfers reliably. Layout usually does not, because almost no two tools implement UML Diagram Interchange compatibly and most will re-lay out your diagram. If the geometry has to survive, use .qea.

Can I export ArchiMate to Mermaid?

You can, but Mermaid has no ArchiMate support at all. Your elements export as a flowchart and lose their layer and relationship semantics. The export dialog states that in those words before it runs.

Can the AI change my model without me?

No. Every AI result lands as a preview diff you accept, reject, or edit. No AI write reaches the model without an explicit accept, and every AI output is validated against the same schema a human edit is validated against.

Do I pay for people who only read diagrams?

No. On Team, only editors, admins, and the owner consume a seat. Viewers and commenters are free at any quantity, because architecture diagrams are read far more than they are written.

Can two people edit the same diagram at once?

At launch you see who else has a diagram open, with live cursors and a soft edit lock you can take over. Simultaneous co-editing of the same diagram comes after launch; we would rather ship a lock that tells the truth than a merge that does not.

What are the limits on the free tier?

One project and 300 elements. Notation coverage is not limited, and no export at any tier carries a watermark.

Does it work on a phone?

Reading does. Editing needs a larger screen, so under 1024px a diagram opens as a read-only pan and zoom viewer with export available. We would rather do that than ship a half-working mobile editor.