Self-Hosting Overview

livediagram is built to be self-hosted, not just used at livediagram.app. Because the whole project is open source, you can clone the repository and run it on your own Cloudflare account. You get every feature in the codebase, no subscription, no licence check, and no required outside services. This page covers why you might do that and what you are signing up for.

Why self-host

There are two equally supported ways to use livediagram, and both have the same feature set.

• Hosted by livediagram at livediagram.app, free for everyone, a convenience and a public home for the project.
• Self-hosted, where you deploy and run it yourself.

You might self-host to keep diagram data on infrastructure you control, to meet an internal policy, to fork and customise the editor, or simply to run a private instance for your team. Since it is MIT-licensed, you are free to modify, embed, or build on it, commercially or not.

What it runs on

livediagram runs entirely on Cloudflare. The frontends are static (built with Next.js in export mode, so there is no server-side rendering and no Node runtime to operate), and all server-side logic lives in Cloudflare Workers.

• Cloudflare Workers serve the apps and host the API.
• Cloudflare D1 is the database where diagrams live, reached only through the API Worker.
• Cloudflare Durable Objects power the per-diagram real-time room.

This means there is no separate database server, no container fleet, and no always-on box to babysit. You deploy Workers and static assets to your Cloudflare account.

What you keep control of

A self-hosted instance has no required calls to any outside service.

• Sign-in is optional. Leave it unconfigured and the app runs in pure-guest mode, fully usable, with no account system at all.
• Telemetry is off by default. A self-host emits and serves nothing unless you explicitly enable it.
• No license gating. Nothing phones home to unlock features.