About
Built for the messy middle of thinking
The stage after you have had an idea but before you can write it down in order. That stage deserves a proper tool.
Every team has the same failure mode. A good conversation happens, someone photographs a whiteboard, and the photograph is never opened again. The thinking was real; the artefact was not.
Untangling exists to make the artefact real. A map you build during the conversation, that everyone can edit while you talk, that keeps changing afterwards, and that you can present from without rebuilding it as slides.
It is deliberately not a general-purpose whiteboard. Mind maps have a structure, and committing to that structure is what makes automatic layout, outline mode, presentation sequencing and AI generation possible at all.
How we build it
The canvas comes first
Most of the engineering effort goes into the editor, because that is where the time is spent. A beautiful settings page cannot rescue a laggy canvas.
No fake buttons
If a control is visible, it works. Where something genuinely is not available on your plan or in this deployment, we say so in plain words rather than hiding it or letting you click into a dead end.
Merge, never overwrite
Collaborative editing built on last-write-wins loses people’s work quietly. We use conflict-free replicated data types so simultaneous edits combine, including inside the same topic.
Permissions are a server concern
Hiding a button is a courtesy, not a control. Every capability is resolved server-side through one module, and unauthorised reads look like "not found" rather than confirming what exists.
Your data is portable
Export works on every plan that includes it, and continues to work after you downgrade. Lock-in is not a retention strategy we are interested in.