Free Self-Hosted Mind Mapping for Home Lab Users: Why We Put MindMapVault on GitHub

If you are building a privacy-first product, trust cannot be a slogan.

It has to be visible in code, architecture, release history, and deployment paths people can verify.

That is one of the biggest reasons we put a significant part of MindMapVault in public GitHub repositories and continued building in the open.

This is not only a technical decision. It is also a values decision.

During my university years, I learned from free and open-source software every single week. I could read source code, learn from maintainers, fork projects, and build my own understanding on top of public knowledge. This project is, in many ways, a return of that respect.

Why open source matters for a privacy-first project

If we ask people to trust a private thinking tool, we need to accept scrutiny.

Open repositories do not magically make software secure, but they make meaningful verification possible:

• people can inspect architecture decisions instead of reading only marketing pages
• developers can review whether sensitive boundaries are documented and implemented
• users can track release cadence, issues, and changes over time
• teams can self-host and own infrastructure where that matters

For privacy products, this matters even more than in typical apps.

People now can run a self-hosted mind mapping app for free in their home lab and inspect how it works.

What we intentionally keep public for a free self-hosted mind mapping app

We publish major product surfaces and technical paths so people can evaluate how MindMapVault is built.

Public repositories

• MindMapVault FOSS (desktop app): https://github.com/mindmapvault/mindmapvault-foss
• MindMapVault Server (self-hosted backend and web surfaces): https://github.com/mindmapvault/mindmapvault-server

Self-hosted mind mapping app for free: what home lab users get

• open code you can review before running anything
• container image access for fast deployment in a home lab
• freedom to fork and adapt to your own infrastructure

Public container image links

• GitHub Container Registry package (server image): https://github.com/mindmapvault/mindmapvault-server/pkgs/container/mindmapvault-server
• Docker Hub image page: https://hub.docker.com/r/kornelko2/mindmapvault-server

Can you run a self-hosted mind mapping app for free in a home lab?

Yes. That is exactly one of the goals.

If you have a small home lab with Docker, you can run a free self-hosted mind mapping app and keep your deployment under your own control.

Typical home lab reasons include:

• you want private visual thinking on your own hardware
• you want to test upgrades before using them in team environments
• you want to learn from real architecture, not toy examples

Open repositories plus public container images make this practical instead of theoretical.

Why a free home lab mind mapping app benefits from open development

Building in public improves engineering discipline because decisions leave traces:

• route changes are visible in commits and changelogs
• compatibility fixes become testable history, not private patch notes
• deployment and packaging docs can be reviewed by operators before incidents happen

In practice, open development pushes us to be explicit and honest, especially around security boundaries.

For home lab users, this also means fewer hidden assumptions. You can inspect environment variables, compose patterns, and deployment docs before trusting a stack.

Transparency does not mean exposing secrets

Open source does not mean publishing private data.

We keep a strict line between:

• open implementation details and workflows
• secret material, keys, tokens, or sensitive user content

That line is critical. We can be transparent about architecture while still protecting operational security and user privacy.

Why this matters to users and developers looking for a free self-hosted mind mapping app

For users:

• you can see what is public and what is not
• you can compare trust models before adopting
• you are less dependent on marketing claims only

For developers:

• you can learn from a real privacy-first product in motion
• you can suggest improvements through issues and PRs
• you can fork and adapt workflows for your own projects

For home lab operators:

• you can run a self-hosted mind mapping app for free as a realistic privacy stack
• you can audit updates before pulling new images
• you can keep your own backup and restore workflow

Final note

I deeply respect the open-source community because it taught me how software is really built: through shared knowledge, visible mistakes, and continuous improvement.

Publishing significant parts of MindMapVault on GitHub is our way of honoring that tradition while building a product where trust is not hidden.

If you want to inspect what we build, start with the repos above and the container links.

If your goal is a free self-hosted mind mapping app in a home lab, this is the most direct way to evaluate whether the trust model matches your requirements.

That is the point: no hidden story, no closed narrative, just code you can evaluate.