Fork Excalidraw

The seed

Excalidraw is an excellent open-source whiteboard: fast, hand-drawn in feel, a natural place to think with shapes and arrows. But using the hosted version means your sketches live on someone else’s servers, bound to their roadmap and their terms. The tool is open; the deployment most people use is not theirs.

This quest takes the open code and makes it sovereign: a fork that runs on infrastructure you own, holds its data where you decide, and can be shaped to fit the EvoBioSys way of working. Visual thinking is core infrastructure — and core infrastructure should not be rented.

Why it matters

A whiteboard is where ideas take their first visible form. If that surface is owned by a third party, so is a piece of your thinking process. Forking it follows the EvoBioSys pattern of taking strong open foundations and re-hosting them under your own control rather than building from zero or depending on a vendor.

• Ownership — the canvas and its data live on infrastructure you control.
• Continuity — no roadmap or terms-of-service change can take the tool away.
• Fit — a fork can be adapted to connect with the rest of the EvoBioSys stack.

What building it out looks like

• Fork the upstream Excalidraw project and stand it up as a self-hosted deployment.
• Decide where drawings are stored, keeping the data local-first and under the user’s control.
• Establish a clean way to track upstream changes so security and feature updates can still flow in.
• Adapt the fork to integrate with the wider EvoBioSys toolset where it makes sense.

Status

Dormant. The intent is captured but no fork has been started. It waits on a self-hosting target and a decision on how drawings should be stored.