Self-host MeshCentral with Levelrail

A remote device management server with web-based desktop, terminal and file access, plus agents for Windows, Linux and macOS. Apache-2.0 licensed. The first account you register becomes the server admin, so register it before sharing the address. Set the host name to your public domain so agents can find the server.

  • AuthorYlianst
  • LicenceApache-2.0
  • Memory384 MiB
  • Archarm64
  • Services1

How to self-host MeshCentral

  1. Pull the images

    One image is pulled on your server.

    Show images
    • ghcr.io/ylianst/meshcentral:1.3.1
  2. Create the app

    One service starts in a single Compose app, with 4 named volume mounts for your data, on port 4430.

  3. Fill in the secrets

    7 settings are preset, you do not have to fill in anything.

  4. Open it

    Without a domain the app gets an sslip.io address; add --domain SERVICE=HOST to use your own.

MeshCentral requirements

Memory
About 384 MiB
Architectures
amd64 image published, arm64 image published
Ports
4430
Domain
Optional, an sslip.io address is used without one
Settings
none to fill in
License
Apache-2.0, permissive license
  • Listed. It is in the catalog but not verified. Back up the data volume before changing an image tag.

Install Levelrail first

On a server with Levelrail running, run the command above, or open the dashboard: Apps, New app, Browse templates, then MeshCentral. New to Levelrail? Install it on a fresh VPS first.

docker pull ghcr.io/glincker/levelrail:latest

Then levelrail-cli login --device. See Getting started and the MeshCentral docs page.

Deploy MeshCentral your way

Every format below deploys the same pinned images. Pick the one that fits how you work.

Deploy MeshCentral from the CLI

Add --domain SERVICE=HOST to serve a service on your own domain, for example --domain meshcentral=app.example.com.

levelrail-cli templates install meshcentral --name my-meshcentral

Deploy MeshCentral with the API

Create a token in the dashboard first. Name, env and domains are the request fields.

curl -X POST -H "Authorization: Bearer $TOKEN" -H "Content-Type: application/json" \
  https://levelrail.example.com/api/v1/service-templates/meshcentral/install \
  -d '{
    "name": "my-meshcentral"
  }'

MeshCentral configuration

MeshCentral services

ServiceImagePortsVolumes
meshcentral ghcr.io/ylianst/meshcentral:1.3.1 4430 data -> /opt/meshcentral/meshcentral-datafiles -> /opt/meshcentral/meshcentral-filesweb -> /opt/meshcentral/meshcentral-webbackups -> /opt/meshcentral/meshcentral-backups

MeshCentral environment variables

VariableServiceValue
ALLOW_NEW_ACCOUNTS meshcentral Preset by the template
DYNAMIC_CONFIG meshcentral Preset by the template
HOSTNAME meshcentral Preset by the template
PORT meshcentral Preset by the template
REVERSE_PROXY meshcentral Preset by the template
REVERSE_PROXY_TLS_PORT meshcentral Preset by the template
TLS_OFFLOAD meshcentral Preset by the template

Ports and volumes

Ports
4430
Volumes
4 named mounts: data -> /opt/meshcentral/meshcentral-data, files -> /opt/meshcentral/meshcentral-files, web -> /opt/meshcentral/meshcentral-web, backups -> /opt/meshcentral/meshcentral-backups

MeshCentral FAQ

How much memory does MeshCentral need?

The catalog lists about 384 MiB of memory for MeshCentral.

Does MeshCentral run on arm64?

For MeshCentral, an arm64 image is published; amd64 is image published.

What licence is MeshCentral under?

MeshCentral is licensed under Apache-2.0, which is permissive, with few conditions on reuse.

Does MeshCentral need configuration before it starts?

No. The template fills in its own defaults.

Which ports does MeshCentral use?

MeshCentral listens on port 4430 inside the stack.

Where does MeshCentral keep its data?

In named volumes: data mounted at /opt/meshcentral/meshcentral-data, files mounted at /opt/meshcentral/meshcentral-files, web mounted at /opt/meshcentral/meshcentral-web and backups mounted at /opt/meshcentral/meshcentral-backups.

Can I deploy MeshCentral on Dokploy or Dokku?

The services and pinned images on this page can be run on any Docker host. The public Dokploy templates list we compared does not have an entry with the same id for MeshCentral, so on Dokploy you would use a Docker Compose application with the file from this page. Dokku deploys container images with its own commands, so the pinned image ghcr.io/ylianst/meshcentral:1.3.1 is what you deploy there.

levelrail-cli templates install meshcentral --name my-meshcentral