Install
One command. It just works.
Install the LinkMesh Server on any Linux VM in a single command. The
.deb / .rpm postinstall bootstraps the internal CA,
the gRPC server certificate, the JWT secret, the GitOps config repo, and
the default admin user, then starts the systemd service. Open the web UI
and enroll your first Collector.
Full step-by-step guide including UI walkthrough and Kubernetes install: Quickstart on docs.linkmesh.io →
How it fits together
Server. Agent. Collector. mTLS in between.
LinkMesh ships in two pieces: the Server (the .deb / .rpm
you install below) and the Agent (installed once per host via the enrollment script).
The Agent connects to the Server over mTLS gRPC and manages the OpenTelemetry Collector on the same
machine — telemetry still flows directly from the Collector to your own backends, never through LinkMesh.
See Trust for the data-handling
specifics, and Architecture on docs
for the component topology in depth.
Quickstart — Linux
Install the Server
Pick the line that matches your distro and paste it on a fresh Linux VM. That's the whole install — the postinstall handles CA, certs, JWT, GitOps repo, and the admin user, then starts the systemd service.
Ubuntu / Debian
curl -fsSL https://artifacts.saas.opensight.ch/binaries/linkmesh-server/latest/linkmesh-server_latest_amd64.deb -o linkmesh-server.deb && sudo apt install -y ./linkmesh-server.debRHEL / Rocky / AlmaLinux
curl -fsSL https://artifacts.saas.opensight.ch/binaries/linkmesh-server/latest/linkmesh-server-latest.x86_64.rpm -o linkmesh-server.rpm && sudo dnf install -y ./linkmesh-server.rpmAfter install — sign in
Open the web UI at http://YOUR_HOST:8080 and sign in as user
admin. The one-time first-login password is printed to the
install journal — run this on the server to read it:
sudo journalctl -u linkmesh-server | grep "INITIAL ADMIN PASSWORD"Running on Kubernetes, or want auto-updates from APT/YUM?
The Kubernetes install guide on docs covers Helm + manifests with reverse-proxy preset. For auto-updates via your system package manager, see repository setup.
Managed hosts can run on Windows too
The Server itself is Linux-only, but the Agent (which runs alongside the OTel Collector on each managed host) ships a Windows AMD64 binary. After your Linux server is up, follow Add a Collector on docs for the platform-specific enrollment commands — Windows, Linux, and the OpAMP standards path all walk through there.
Next steps on docs.linkmesh.io
Everything beyond the one-liner — UI walkthrough, enrollment tokens, reverse-proxy setup, certificate lifecycle, the agent install one-liner, and troubleshooting — lives in the operator docs. Single source of truth, kept current with each release.
Quickstart
First Collector in 10 minutes
UI walkthrough from blank install to a live route with throughput. With inline screenshots. →
Kubernetes install
Helm chart + manifests
Production deployment with reverse-proxy preset, NetworkPolicy, and TLS termination. →
Enroll a Collector
Linux, Windows, or OpAMP
Three enrollment paths with the actual one-liner commands and token lifecycle. →
Reverse proxy
nginx / Caddy / HAProxy
HTTPS termination for the HTTP API + TCP pass-through for the mTLS gRPC channel. Annotated config. →
Reference
Configuration schema
All config.yaml keys, CLI flags, and the linkmesh-server cert lifecycle commands. →
Troubleshooting
Operational runbooks
Enrollment failures, cert renewal, server IP changes, common mistakes and how to recover. →
Stuck?
Open the app to start enrolling collectors, browse the full operator docs, or reach the OpenSight team directly.