For a while now I’ve been running an Excalidraw instance on my VPS (with Yunohost). Excalidraw is a virtual whiteboard, and a useful tool to me. Excalidraw is lightweight, and any drawings you make are stored in text format, which makes them highly portable. It integrates very well with Obsidian, with the Excalidraw plugin, by fellow PKM enthusiast Zsolt Viczián. My Excalidraw instance is also used by my company’s team.
I run my own Excalidraw instance for reasons of digital autonomy. For single person use it provides that. However, Excalidraw has a collaboration mode, reserved to Excalidraw.com only (as noted in the package description), which depends on two outside parties with control over it. For my company collaboration mode is the primary desired use form, but it must be digitally autonomous to be of actual value. It should also actually work, which it doesn’t on a self-hosted instance.
In Excalidraw’s collaboration mode multiple users can work on its canvas (dubbed a ‘room’), where you see each-others edits in real time. Drawings you’ve made collaboratively also have a unique URL so the room can be called back up later, to continue work.
The Excalidraw.com deployment’s open source package, included in the general excalidraw package (which the Yunohost install package uses directly) has two things hardcoded that are needed for collaboration and persistence:
- To make the realtime movement of cursors and edits visible, it calls the oss-collab.excalidraw.com subdomain for websocket connections but only answers requests with excalidraw.com as origin, and returns forbidden for my and other domains. In the browser,
wss://oss-collab.excalidraw.com/socket.io/?EIO=4&transport=websocketfails. So it refuses self-hosted Excalidraw instances. The live view of other users and their edits therefore does not work on self-hosted instances. - It stores drawn objects in Firebase for persistence of rooms, and does so encrypted. For self-hosted instances this does work, reloading a room from storage shows the objects others made. However Excalidraw.com controls that storage, and holds the keys to it, meaning they can delete your stored material or remove your access at will. An issue of digital autonomy. Firebase itself is provided by Google, and while the Excalidraw objects are encrypted, it introduces another party with a hold on the data.
In practice, it means that a self-hosted instance of Excalidraw has a half working collaboration capability (no live sync, but reloading the persistent Firebase version works). It of course wasn’t promised to work, but even if it did it would not actually be an autonomous install due to the hardcoded dependencies. To gain that digital autonomy, and have functioning collaborative functionality, both a necessity for my team, I’d need to ‘bring home’ those dependencies.
The live collaboration part is created with the open source excalidraw-room script, which is easy enough to install on my VPS. Local storage may be more difficult to figure out (but not too hard, I hope). The main thing is that to let the excalidraw package talk to that room script and the storage, I need to alter that package itself. If the dependencies had been configurable settings it would be a different thing.
Now it needs a fork from Excalidraw, to be able to change those hard coded settings to provide both excalidraw-room and storage on my VPS itself. I do not look forward to maintaining a fork in order to change 3 things or so for the live collaboration to work (more to swap out storage), and then needing to keep it aligned with the upstream version of Excalidraw, but it seems to be the only viable path.
Whether there are other open source packages out there where self-hosting also carries hard coded cloud dependencies is a question I need to also stay aware of, I think.


