Microsoft Visio has been the default diagramming tool in many companies for decades. If your organization runs on Microsoft 365, it is probably already licensed, people know it, and there is a stencil for almost anything.
Engineering teams still go looking for a Visio alternative, usually for architecture diagrams specifically. This post is an honest look at that decision: what Visio does well, where architecture diagrams outgrow it, what Archboard does instead, and how to move the diagrams that matter without a migration project.
The short version
- Visio is a general diagramming suite inside Microsoft 365. Org charts, floor plans, process maps, network diagrams and cloud architecture, with deep links into Teams, Excel, Power BI and the rest of the suite.
- Archboard is a hosted workspace for structured diagrams. Nodes have types from node packs, such as a Kubernetes Deployment, a C4 Container or a firewall, and people and AI agents edit the same canvas live.
- The choice depends on the job. For business diagrams that live inside Microsoft 365, Visio fits. For architecture diagrams an engineering team keeps current, a structured workspace usually fits better.
Where Visio shines
Be fair to it. Visio does several things very well:
- It is already there. Visio in Microsoft 365, a lightweight web app, is included with Microsoft 365 commercial subscriptions.
- Breadth of content. Templates and stencils for flowcharts, BPMN, network and rack diagrams, Azure and AWS architecture, UML and ER diagrams, floor plans and engineering drawings. Plan 2 adds access to more than 250,000 partner-created shapes.
- Data-linked diagrams. With Plan 2, diagrams can be linked to data sources and generated from data, which is how many organizations keep org charts and process maps up to date.
- The Microsoft ecosystem. Diagrams in Teams and Power BI, editing in Excel and PowerPoint, and process diagrams exported to Power Automate.
- Familiarity. Many people outside engineering already know it.
Why architecture diagrams outgrow it
The desktop app is Windows only
The full Visio desktop app comes with Plan 2 and runs on Windows. Microsoft does not offer a desktop version for macOS; Mac users work in Visio for the web, which creates fewer diagram types than the desktop app. In engineering teams where many people use Macs or Linux, the people who know the system best often have the weakest editor.
Diagrams are files
A Visio diagram is a .vsdx file stored in OneDrive, SharePoint or somewhere else. Co-authoring works when the file lives in OneDrive or SharePoint, but everyone has to use the same kind of app: one person in the web app and another in the desktop app cannot edit at the same time. Copies multiply as files get emailed, exported and pasted into wikis, and the screenshot in the design doc is out of date the day the system changes.
Shapes carry no architecture meaning
A box with an AWS icon is a shape with a label. Visio can validate some structured diagrams against rules and attach shape data, but nothing knows that a Service routes to a Deployment or that a database sits in a private subnet unless someone draws it consistently every time.
Licensing follows editors
Plan 1 is listed at $5 and Plan 2 at $15 per user per month, paid yearly, at the time of writing (October 2026). For a team that mostly needs a few architecture diagrams, paying for the suite's breadth can be more than the job needs, and for Mac users the web app is the only option anyway.
What Archboard does instead
- Typed node packs. 27 built-in packs, including Kubernetes, Cloud, C4 Model, Network, Data, Security, BPMN, UML, Sequence and Entity Relation, plus flowcharts, mind maps and sticky notes on the same canvas.
- Live editing in the browser. Everyone with edit access works on the same diagram with live cursors, on any operating system with a browser.
- AI agents on the canvas. Agents such as Claude or Cursor connect over MCP and edit diagrams live next to the team, labeled with the person they work for, and that person can undo an agent's change in one step. See AI agents.
- One live link. Share links update as the diagram changes; Pro adds embeds for docs sites.
- Diagrams from code. Free tools turn Terraform, CloudFormation, Kubernetes YAML, Docker Compose, SQL schemas and Mermaid flowcharts into editable diagrams.
- An open document format. Every diagram is versioned JSON with a published JSON Schema, so other tools can read what you export.
Visio vs Archboard at a glance
| Visio | Archboard | |
|---|---|---|
| Primary job | General business and technical diagramming in Microsoft 365 | Structured architecture and process diagrams that stay current |
| Apps | Web app; desktop app for Windows with Plan 2 | Web app in any modern browser |
| Building blocks | Large template and stencil libraries | 27 typed node packs with frames and ports |
| Live co-editing | In the web app, or in the desktop app with Plan 2, for files in OneDrive or SharePoint | Live cursors for people and AI agents on every diagram |
| From data or code | Plan 2 links shapes to data and creates diagrams from data | Free tools turn Terraform, Kubernetes YAML, Compose, SQL and Mermaid into diagrams |
| Format | .vsdx, XML parts in a ZIP package |
Versioned JSON with a public JSON Schema |
| Office integration | Deep: Teams, Excel, PowerPoint, Power BI, Power Automate | None; Archboard is not an office-suite add-in |
| Hosting | Microsoft 365 cloud, desktop files | Hosted SaaS only, no self-hosted edition |
| Price (October 2026) | Included in Microsoft 365 commercial plans (web); Plan 1 $5, Plan 2 $15 per user per month, paid yearly | Free for one seat; Pro $10 per seat per month or $96 per year |
Check each vendor's pricing page before you decide; plans and prices change.
A typical switch: the three-tier diagram
Many teams have one Visio diagram everyone knows: users, a load balancer, a web tier, an app tier and a database, drawn years ago and edited by whoever still has the file. Rebuilt once with typed nodes, it looks like this:
Diagram contents
- Users
- www.example.com
- VPC
- Public subnet
- Load balancer
- App subnet
- Web servers ×2
- App servers ×3
- Data subnet
- Database primary
- Read replica
- Object storage
- HTTPS 443
- alias record
- HTTP 80
- REST 8080
- writes, SQL 5432
- reads
- async replication
- HTTPS, files and backups
How to read it:
- Entry. Users reach the load balancer in the public subnet over HTTPS; DNS points the domain at it.
- Tiers. Web servers and app servers sit in a private subnet and scale separately. App servers write to the primary database and can read from the replica.
- Data. The database and its asynchronous replica have their own subnet; files and backups go to object storage.
- The note. Decisions and runbook names sit next to the picture, so the diagram explains itself without the email thread it came from.
How to move without a migration project
Archboard has no Visio (.vsdx) import, so plan on redrawing rather than converting:
- Pick the diagrams people still use. Search your wiki and design docs for embedded Visio exports, and keep the ones that are referenced. Leave the rest where they are.
- Redraw the important ones with typed nodes. A three-tier or service diagram takes minutes, and redrawing is a chance to fix what drifted. Export the old diagram from Visio as SVG or PNG and keep it beside the new one while you work.
- Start from code where you can. If the infrastructure is in Terraform or Kubernetes YAML, or the schema is in SQL, generate a first draft with the free tools instead of drawing.
- Let an agent draw the first version. With an AI agent connected over MCP, describe the diagram and let it place the typed nodes, then correct what it got wrong.
- Replace screenshots with links. Point every page to the live diagram so there is one copy to keep current.
If you need to convert hundreds of .vsdx files automatically, a tool with Visio import fits that job better. For a wider comparison, see Lucidchart alternatives for engineering teams and draw.io vs Archboard, or all comparisons.
Build it in Archboard
- Sign in with Google or GitHub and create a diagram.
- Add a Network pack Internet node for users and a DNS node, then a Network pack VPC frame with three Subnet frames: public, app and data.
- Put a Cloud pack Cloud LB in the public subnet, two Cloud pack Compute nodes for the web and app tiers in the app subnet, and two Managed DB nodes for the primary and the replica in the data subnet.
- Add a Cloud pack Object Storage node outside the VPC.
- Label the edges with protocols and ports, make replication dashed, and add a Core Markdown block with decisions and runbooks.
The example uses 13 diagram nodes, within the Free plan.
FAQ
Can Archboard open Visio files?
No. There is no .vsdx import. Redraw the diagrams you want to keep; for code-defined infrastructure, start from the free code-to-diagram tools.
Does Archboard work inside Microsoft 365? No. Archboard is a hosted web app, not an office-suite add-in. You can link or, on Pro, embed live diagrams in documentation sites.
Is there a desktop app? No. Archboard runs in the browser on any operating system.
Is Archboard cheaper than Visio? It depends on what you already pay for. Visio in Microsoft 365 is included with commercial Microsoft 365 plans, and Visio Plan 1 is listed at $5 per user per month. Archboard Free covers one seat, and Pro is $10 per seat per month. Compare what each plan includes for the diagrams you need.
Should we replace Visio everywhere? Usually not. Keep Visio for org charts, floor plans and Office-centric process diagrams, and move the architecture diagrams that engineering keeps current.