draw.io is a configurable, client-side JavaScript diagramming and whiteboarding application, jointly owned and developed by draw.io Ltd (previously JGraph) and draw.io AG, intended for anyone who needs to draw diagrams and whiteboards in a browser or on the desktop without a login.

What it is

draw.io is a JavaScript, client-side editor for general diagramming and whiteboarding. The source in this repository is licensed under Apache License 2.0, and the project runs a production deployment at https://app.diagrams.net in addition to being self-hostable. It lives in the web-application ecosystem: the editor runs in the browser, and the same codebase backs the Desktop build, the official Docker image, and packaged .war files. The README states the scope plainly — this is a diagramming and whiteboarding application, not an SVG editor, and SVG export is intended for embedding in web pages rather than for editing in other tools.

The concrete problem it solves is providing a diagramming and whiteboarding editor that a person or an organisation can run themselves and keep full control of their content. Because the editor is client-side, it works from a fork published to GitHub Pages, from a container, from a packaged archive, or as a desktop application. The project makes no copyright claim on the diagrams created with it, and the README notes that all third-party JavaScript libraries bundled in are licensed compatibly with Apache 2.0, with no GPL or AGPL among them.

Key capabilities

• Client-side JavaScript diagramming and whiteboarding editor, forkable and publishable to GitHub Pages as a fully functional editor without integrations.
• Tracked in this registry under the topics diagram, javascript, and whiteboard.
• Distributed through multiple channels: the official Docker image at https://github.com/jgraph/docker-drawio, draw.io Desktop from https://get.diagrams.net, and packaged .war files on the releases page.
• SVG export aimed at embedding diagrams in web pages.
• Apache-2.0 source licence, with no copyright claim made on diagrams created by users.
• Icon sets, stencil libraries, and diagram templates carry a separate restriction: they may not be used as software assets in, distributed for use with, or incorporated into Atlassian products or products distributed through the Atlassian marketplace or plugin ecosystem without explicit written permission. That restriction does not apply to end-user diagram output such as exported images or documents.
• Browser support spans Chrome 123+, Firefox 120+, Safari 17.5+, Opera 109+, Edge 123+, WebView Android 137+, and Safari iOS 18.5+.

Who uses it and how

• Individuals and teams who want a diagramming editor reachable without an account, including through the hosted instance at https://app.diagrams.net.
• Self-hosters who fork the repository and publish it to GitHub Pages to obtain a fully functional editor without integrations.
• Operators who prefer container deployment, using the official Docker image rather than a manual fork.
• Desktop users who install draw.io Desktop from https://get.diagrams.net instead of running a browser or server deployment.
• Organisations deploying the packaged .war files from the releases page onto their own application server infrastructure.

Getting started

Fork the repository and publish it to GitHub Pages, or use the official Docker image published at https://github.com/jgraph/docker-drawio. Alternatives are draw.io Desktop from https://get.diagrams.net and the packaged .war files on the releases page.

How it compares

The facts provide no list of paid products that this project replaces, and they name no comparable diagramming tools. On the evidence available, draw.io stands alone in this registry.

When to use it — and when not to

A self-hoster takes on running the editor themselves, whether through GitHub Pages, the Docker image, or a .war deployment; the README does not describe required database, storage, or SMTP dependencies, so those must be established from the chosen deployment route rather than from this documentation. The most significant limitation is stated by the project itself: draw.io does not support real-time collaborative editing in this version, so teams that need concurrent multi-user editing should look elsewhere. Additionally, the project does not accept pull requests and is developed entirely by its core team, and the icon sets, stencil libraries, and templates are subject to trademark and licence restrictions that govern their use inside Atlassian products.