Self-hosted Lucidchart alternative: own your diagrams with drawio
Every architecture diagram, network map, and onboarding flowchart your team draws is a real asset — the shared picture of how things actually work. So it's worth asking where those pictures live. Lucidchart keeps them on its servers, counts your documents on the free tier, and puts the shape libraries and Visio import you actually need behind a subscription. But a diagram is just structured XML. There's no reason the tool that edits it should hold it hostage. drawio is the full editor — flowcharts, network and architecture diagrams, the lot — running on hardware you control.
What drawio is
drawio (the open-source project behind diagrams.net) is a complete, professional diagram editor — the same one millions of people use inside Confluence, Jira, and Google Drive, packaged to run on your own server. It isn't a stripped-down demo. Flowcharts, network and cloud-architecture diagrams, UML and entity-relationship models, org charts, mind maps, BPMN, wireframes, and floor plans all live in one canvas with thousands of built-in shapes.
The contrast with Lucidchart is plain. Lucid's free tier caps you at three editable documents and keeps its richest shape libraries, most templates, and Visio import on paid plans. drawio has no document limit, no per-seat meter, and no upsell screen. It's open source under the Apache licence, genuinely free, and stores nothing on a server you don't control.
The features that actually matter
The feature list is long, but a handful of things are what make drawio a real replacement rather than a free-tier stopgap:
- Every diagram type in one editor. Flowcharts, network and architecture diagrams, UML, ER models, BPMN, org charts, mind maps, wireframes, and floor plans all share the same canvas — no separate apps, no premium unlock per category.
- Thousands of shapes, cloud stencils included. Official AWS, Azure, Google Cloud, Kubernetes, and Cisco network icon sets ship in the box. Lucid gates many of its shape packs behind paid tiers; here they're all just there.
- Your files, your storage. Save to your device, Google Drive, OneDrive, Dropbox, GitHub, or GitLab — or just download. The native format is open, human-readable, diffable XML, not a proprietary blob.
- Import from the tools you're leaving. drawio reads Visio (.vsdx), Gliffy, and Lucidchart files, so you don't abandon years of work. Visio import alone is a paid feature in Lucidchart. In fairness, the Lucidchart path is the least polished of the three — it runs through a copy-paste or a small converter tool rather than a clean file open — but it does get your diagrams across.
- Export where you need it. PNG, JPEG, SVG, PDF, and HTML. Exported PNG and SVG files can embed the editable diagram inside the image, so a picture someone shares reopens as a fully editable project.
- Diagrams from text and data. Generate a diagram straight from a CSV file, or paste Mermaid text and let drawio build and lay it out — handy for keeping diagrams under version control alongside the code they describe.
- Custom shapes and full styling. Edit any shape's style, build and save your own libraries, and apply themes — including a proper dark mode.
Why self-host it instead of the hosted version
Your diagrams stay yours. Self-hosted drawio runs client-side: the editing happens in your browser, and when you point it at your own storage, the sensitive stuff — your production network topology, your unreleased architecture — never touches a vendor's servers. That's a fundamentally different security posture than uploading all of it to a SaaS.
The cost doesn't scale per seat. Lucidchart bills per user, per month, forever, and the price climbs as your team grows. Self-hosted drawio costs the same whether five people use it or fifty. There's no editor tier, no document cap, no "contact sales."
You control the whole thing. Your instance, your domain, your update cadence, your branding. Nobody deprecates a feature you rely on, changes the pricing under you, or decides your free documents are now read-only.
Who it's for
Engineering and DevOps teams documenting infrastructure — network diagrams and cloud architecture that shouldn't be sitting on someone else's servers, and that live better kept next to the code in Git.
Consultants and agencies who produce diagrams for clients and want their own private, branded instance instead of paying per seat for a tool their clients never see.
Educators, students, and solo builders who need a serious diagramming tool without a subscription — flowcharts for a class, an ER model for a side project, a mind map for a plan that doesn't expire when a trial does.
The honest setup notes
drawio is refreshingly light to run — it's a stateless web app with no database to babysit — but self-hosting it raw still has chores. Because it's stateless, your diagrams don't live on the server; they live in the files and connected storage you point it at, so "backups" really means giving those files a sensible home and keeping a copy of it. You'll want it behind HTTPS with a real certificate, not served over plain HTTP. The cloud-storage connectors are their own small project too: pointing a self-hosted instance at Google Drive, OneDrive, or Dropbox means registering your own OAuth app with each provider and handing drawio the keys — worth it if you want the integration, but not something that just works the moment the container starts. You're also responsible for pulling new images when the project ships updates, and it ships often. And real-time, multi-person co-editing isn't part of the standalone editor; that's a genuine gap next to a live SaaS, and the closest drawio comes is the file-locking in its Confluence and Google Drive integrations.
None of it is hard. It's just yours to remember, on top of the actual work of drawing things. Or let us run it, and skip the list entirely.
Deploy it in one click
Rolling your own means installing Docker, wiring up a reverse proxy, terminating TLS, and owning updates and monitoring from then on. It's very doable, and it's a chore that never quite ends.
On Caliber Node it's one click. We stand up drawio on managed infrastructure with HTTPS already terminated, a real domain, and updates handled — you get the full editor at a URL, not a weekend project. You can deploy drawio in one click and be drawing in minutes, with the same ownership and export freedom you'd get from building it all by hand.
First run
- Open your drawio instance and choose where diagrams should be saved — your device, or a connected store like Google Drive or GitHub.
- Pick a template or start from a blank canvas, and give your first diagram a name.
- Drag shapes in from the left-hand panel, or search the shape library for exactly what you need — try "AWS EC2" or "database."
- Connect two shapes by hovering over one until directional arrows appear, then drag from its edge to link them; double-click any shape to add a label.
- Export to PNG, SVG, or PDF to share it — or just save the file and reopen it anytime to keep editing.
That's a real, finished diagram, stored somewhere you chose.
The bigger picture
Diagrams are how teams think out loud — the shared map of how a system, a process, or an org actually fits together. That's exactly the kind of tool worth owning outright, not renting by the seat and leaving on a vendor's servers. Self-hosting drawio turns your diagrams from someone else's hosted documents back into plain files you keep, version, and export forever. And because the format is open XML, that freedom outlives the tool: if you ever move off drawio, your work opens somewhere else instead of being trapped. The editor is genuinely first-class; the only thing you give up is the subscription.
Deploy drawio in a few minutes →
One-click self-hosted apps, managed for you — real logs, SFTP, and your data always exportable. Never a black box.