Published: Last updated:

WiseMapping

WiseMapping is open-source, web-based mind mapping. It runs in the browser and can be hosted on the organisation's own infrastructure, so the maps do not live in someone else's cloud service but stay under its own control.

Many collaborative, browser-based mind mapping tools are built as a foreign cloud service: the collection of ideas sits on the provider's server, and an account there is the precondition for using the tool at all. WiseMapping takes the other route. It is a web application that can be self-hosted, which turns mind mapping into a building block of sovereign infrastructure rather than another data leak. This page describes what WiseMapping does, how it is operated, and what state the project is in.

Mind mapping under the operator's own control

WiseMapping is an editor for mind maps, the tree-shaped idea diagrams that break a central topic down into branching sub-points. The application has existed since 2007. It comes in two parts: a back end in Java (Spring Boot 3) that manages maps, accounts and sharing, and a front end in React that draws the maps as SVG in the browser. PostgreSQL is the recommended database, and MySQL works too.

In terms of features, WiseMapping covers the usual mind mapping ground:

  • Visual maps. Nodes can carry colours, icons and notes and be structured freely.
  • Collaboration. Maps can be shared and edited as a team, with role-based access rights per map.
  • Import and export. WiseMapping imports from Freeplane, XMind and MindManager and exports to PDF, SVG and Freeplane among others. That keeps maps portable instead of locked into a closed format.
  • Embedding. A map can be embedded into web pages, blogs or documentation.
  • REST API. A programming interface connects WiseMapping into existing workflows.

Self-hosting

The real difference lies in the operating model. WiseMapping provides official Docker images, described as production-ready, that allow standing up a self-hosted instance on the organisation's own hardware or in its own data centre. The maps then never leave that environment, and there is no vendor lock-in to a hosted mind mapping service. Anyone who wants to work sovereignly has the choice between a self-run instance and the project's own online offering; only the self-run variant keeps the data entirely in house.

That choice is a make-or-buy decision in miniature: a self-run instance means control, but also operation, updates and backups as the operating organisation's own responsibility. The technical enforcement of data control ranges from tenant isolation to encryption and stays the operator's responsibility.

The licence, read closely

WiseMapping is open source, but not under one of the familiar standard licences. The code is released under the WiseMapping Public License Version 1.0 (WPL), which builds on the Apache License 2.0 and adds one extra condition: every user interface must carry a visible "powered by WiseMapping" notice linking to wisemapping.com, unless the project founders explicitly permit its removal. This is a so-called badgeware clause. It does not change the fact that the source is open and the implementation auditable, but it is worth knowing for anyone who wants to ship the interface unbranded.

Project activity

Mind mapping tools are plentiful; the honest question with a self-hosted service is whether the project is maintained. For WiseMapping, the releases point in the right direction: the official Docker image was last updated to version 6.0.9 in May 2026, with several predecessor versions in the preceding months. The project is therefore active, not a frozen archive. Checking the update cadence before adoption still makes sense, because a self-run service is only as secure as its last update.

Scope, honestly bounded

Not every feature advertised on the provider's site belongs to the self-hostable core. In particular, the AI feature that turns a text prompt into a mind map is a property of the hosted online offering and depends on an external language-model service; it is not a given part of a self-contained instance. Anyone taking the sovereignty idea seriously draws a clean line here: the open-source core application delivers mind mapping without an external dependency, while AI generation is an additional, differently sourced offering.

WiseMapping also has a clear boundary in substance. It is a tool for free thinking and structuring, not for formal diagrams. To draw software architecture in defined layers, the right tool is not a mind map but a method such as the C4 Model. And a durable, linked knowledge store is more the domain of a local flat-file tool like Obsidian; the mind map is the quick visual sketch before it, not the filing place after.

Where WiseMapping fits and where it does not

  • Fits. Quick, visual structuring of ideas, brainstorming and project planning, together as a team, and on the organisation's own infrastructure instead of in a foreign account.
  • Fits less. As a long-lived, searchable knowledge base with dense linking, a notes system like Obsidian is the better choice.
  • Does not fit. Formal, rule-bound architecture or process diagrams belong in a notation tool built for that, not in a free mind map.

References

Related topics

  • Digital Sovereignty, control over data and infrastructure without foreign servers.
  • Obsidian, the local flat-file knowledge store for durable filing.
  • C4 Model, the method for formal architecture diagrams instead of free maps.

Ask AI

These links open external AI services, the conversation and its content are sent to their providers.