meshr / Platform / Self-hosted
Self-hosted Coming soon

Your infrastructure, your rules.

We're building a self-hosted meshr you can run on your own servers — for full data sovereignty, air-gapped networks, and teams that can't send traffic to a SaaS. It isn't available yet; here's the plan and how to get on the list.

  • Docker Compose bundle for single-server deploys
  • Kubernetes Helm chart for production scale
  • Designed for air-gapped / offline networks
  • Full data sovereignty — your data, your servers
docker-compose.yml — planned
# Planned shape — not yet published
services:
  meshr-control:
    image: reg.meshr.to/meshr/control:latest
    ports:
      - "443:443"
    environment:
      - MESHR_DOMAIN=mesh.company.com
      - MESHR_DB_URL=postgres://...
    volumes:
      - meshr-data:/data
  postgres:
    image: postgres:16-alpine
Roadmap · Enterprise

Self-hosting is in design — not yet available

Today meshr runs as a managed cloud. Self-hosted deployment (Docker Compose, then Kubernetes) is planned as an Enterprise offering. If running meshr on your own infrastructure is a requirement, tell us about your environment — early design partners help shape what ships first.

Planned deployment models

Two targets, when it lands.

The intended path: start on a single server, move to a cluster when you need scale. Both are on the roadmap — neither ships today.

Coming soon

Docker Compose

A single-server bundle for small teams and evaluation. Planned as the first self-host target — bring Docker and a Postgres, point a domain, and run the control plane on your own box.

StatusComing soon
Planned forSmall teams, evaluation
RequirementsDocker, Postgres
AvailabilityEnterprise roadmap
Coming soon

Kubernetes

A Helm chart for production-grade, horizontally-scaled deployments is on the roadmap. It is not available yet — there is no published chart today.

StatusComing soon
Planned forProduction, larger orgs
RequirementsK8s cluster, Helm
AvailabilityEnterprise roadmap
Planned architecture

Modular by design.

The self-hosted build reuses the components that already run the meshr cloud — each with a single responsibility.

Control plane

The core API, authentication, policy engine, certificate authority, and dashboard — the same control plane that runs the meshr cloud today, packaged to run on your infrastructure.

PostgreSQL

Primary data store for devices, policies, users, organizations, and audit events. The control plane already targets Postgres 16, so the data layer carries straight over.

Relay / data plane

WireGuard relay for connectivity where a direct peer-to-peer path is not available. Designed to sit alongside the control plane in the same deployment.

Why self-host

Built on open source, run on your terms.

The reasons teams ask for it — the same reasons we're building it.

Data sovereignty

Keep every device record, policy, and audit event inside your own perimeter — nothing leaves your infrastructure.

Air-gapped networks

Designed to run with no outbound dependency on the meshr cloud, for offline and isolated environments.

Built on WireGuard

The same open-source WireGuard data plane you already trust — no proprietary protocol lock-in underneath.

Want to run meshr yourself?

Self-hosting is coming as an Enterprise option. Start free on the cloud today, and tell us if on-prem is a must-have — design partners get first access.