Where MeshHold is going.
Built incrementally, in the open. The community shapes what comes next.
Shipped
- Distributed storage with replication factor
- Encrypted chat, audio + video calls
- Mesh VPN + multi-hop tunnels (TCP & UDP)
- Forward / reverse port forwards
- S3-compatible API (Garage-style)
- Vaults mounted as a drive (Windows, Linux, WebDAV)
- Documents, spreadsheets and a plain-text editor — OpenDocument, co-edited node to node
- Photo gallery, with the dates and cameras read out of the files
- Media library — audio + video, auto-enriched metadata
- Federated sharing with Nextcloud / ownCloud (OCM)
- AI agent integration (Claude Code, OpenCode, Gemini CLI)
- Inbound webhooks (Slack / Mattermost shape)
- Headless Pi cameras, auto-answer calls
- At-rest encryption, password-locked vaults and chats
- Linux (DEB / RPM), Windows (MSI), Android, Raspberry Pi
In progress
- Phone-as-admin pivot — web UI on
127.0.0.1only, managed exclusively via libp2p tunnel from a paired device. No public admin endpoint, no domain, no TLS cert. - More AI agent back-ends — Codex (OpenAI), Aider, Cursor and GitHub Copilot alongside the current Claude Code, OpenCode and Gemini CLI.
- Stability & quality — fewer rough edges, better error handling, more tests on every release.
Considering
- App store releases — Google Play and Apple's App Store, so install is one tap and updates land automatically.
- macOS & iOS apps — native clients (today we bundle a WebView2 wrapper on Windows). Apple's P2P restrictions make iOS hard; it'll ship when there's a clear path.
- Linux distro repositories — APT / RPM / AUR repos so
apt install meshholdjust works and stays updated. - Theme customization — light / dark and custom accent colours across the web UI.
- Public API for third-party apps — a documented, stable API surface so external tools and integrations can build on MeshHold.
- Better documentation — more guides, recipes and reference docs.
- Enterprise tier — OIDC / SAML / AD integration, tamper-evident audit log, RBAC per vault, fleet management across N nodes.
- Plugin marketplace — third-party extensions to the core daemon.
How this list gets decided
Mostly by what breaks. A feature usually exists because something did not work in an actual house, on an actual laptop, over an actual bad connection — which is why the shipped column is longer than the plan that preceded it.
After that: what people keep asking for on the forum, and what a partner is blocked on. Deployment partners get two blocking issues a year moved to the front, which is the most direct route onto this list that exists.
There are no dates, because a date from one person is a guess with a number attached. The one exception is the Business tier, which is aimed at 2026 because a commercial commitment without a year is not a commitment.