LinkMesh
Early Access

Work directly with the builders and lock in launch pricing.Join the program →

The control plane for your OpenTelemetry Collector fleet

The observability Swiss Army knife

OpenTelemetry-native and OpAMP-first — one tool tocollect, refine, protect & routeyour telemetry, self-hosted and actually built in Switzerland.

Start free →View pricing

Self-hosted, free to start. No credit card · 25 Collectors free.

Install on any Linux VM — 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.deb

RHEL / Rocky / AlmaLinux, Kubernetes and the full walkthrough:Install guide →

LinkMeshOPENTELEMETRY COLLECTOR FLEET MANAGEMENTTelemetry sprawls.Cost explodes.LinkMesh isOpenTelemetry-nativeOpAMP-firstOn-premisesGitOps-drivenPer-collector billedPII-awareOpen standardsNo lock-inSelf-hostedNo volume-based licensing· pay per collector, not per GBCollectAny source, any signal.OTLP (gRPC + HTTP)Syslog (RFC 3164 / 5424)Filelog, journald, KafkaPrometheus + host metricsRefineCut noise before it costs you.Drop, sample, aggregateRate-limit by service or tagOTTL transforms with previewsPer-component throughputProtectMask PII on the host.Cards, emails, phone numbersCustom regex / OTTL rulesRuns client-side, before egressStays inside your networkRouteRight data to the right backend.By label, env, tenant, serviceFan-out to multiple backendsPer-route processing chainsGitOps audit-trail every changeHow it all connectsOne control plane orchestrating every Collector in your pipelineSOURCESBACKENDSLogsMetricsTracesGrafanaSplunkElasticAzureMANAGEMENTLinkMesh ServerOPAMP CONTROL PLANEOPENTELEMETRYCollectors

Prefer to be guided in, or want product updates? Get early access:

Already running a collector? Connect it in ~10 lines

otelcol-contrib · OpAMP

Running otelcol-contrib?

Add the OpAMP extension and a token. ~10 lines of YAML. →

Grafana Alloy · remotecfg

Running Grafana Alloy?

Add a remotecfg block and a token. Upstream Alloy, no fork. →

Either way, your telemetry stays on your infrastructure. Optionally add the LinkMesh agent for guided onboarding — it auto-discovers services and log sources.

Explainer · 1:33

LinkMesh in ninety seconds

What a collector is, where the control plane runs, and why you pay per collector instead of per gigabyte.

Already sold and want to see it installed?Watch the full install walkthrough →

Optional

Add the onboarding agent for a faster start

A plainly-enrolled collector works on its own. The optional LinkMesh agent is an edge connector that auto-discovers what's running on a host or cluster and turns it into ready-to-approve pipelines — so onboarding is minutes, not manual YAML. It carries no telemetry and never sits in the data path.

OnboardingCollector onlyOpAMP or remotecfg+ LinkMesh agentoptional edge connector
Service auto-detectionAuthor receiver config by handDetects running services + suggests receivers
Log-source discoveryFind log paths yourselfGuided picker + template library
Kubernetes workload rollup—Discovers pods / workloads for onboarding
Reachability preflight—Flags connectivity + unreadable sources up front
Host footprintYour collector only+ a small agent (package or DaemonSet)
Install guide →

First time? Walk through the full setup with screenshots ondocs.linkmesh.io/quickstart.

One tool for the whole pipeline

Open standards and no lock-in, per-collector pricing, on-prem and PII-aware — one control plane for the four jobs every telemetry pipeline needs.

Collect

Logs, metrics, and traces from any source, over standard OpenTelemetry Collectors — no proprietary agent, no fork.

Refine

Drop, sample, and aggregate noisy telemetry at the source — often 10–30% less log volume before it hits a billed backend.

Protect

Mask credit cards, emails, and custom fields on the host, before anything leaves your network.

Route

Fan out to the right backend by label, environment, or tenant — Grafana, Splunk, Elastic, Azure, any OTel destination.

For the technical model behind these — Collectors, Sources, Pipelines, Routes, Destinations — seeConcepts on docs.linkmesh.io.

From the blog

Telemetry pipelines, OpenTelemetry, and observability cost control — from the team building LinkMesh.

All posts →

25 Collectors free for evaluation.

Test enrollment, pipeline configuration, PII masking, and multi-destination routing in your own environment — no volume-based cost risk during the trial. Pricing scales by managed Collector after that.

Install LinkMesh →See pricing →

Get in touch

Questions about pricing, running a bigger fleet, or self-hosting? Tell us what you need and we'll get back to you.