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 to collect, refine, protect & route your telemetry, self-hosted and actually built in Switzerland.

Start free → View pricing

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

LinkMesh OPENTELEMETRY COLLECTOR FLEET MANAGEMENT Telemetry sprawls. Cost explodes. LinkMesh is OpenTelemetry-native OpAMP-first On-premises GitOps-driven Per-collector billed PII-aware Open standards No lock-in Self-hosted No volume-based licensing· pay per collector, not per GB Collect Any source, any signal. OTLP (gRPC + HTTP) Syslog (RFC 3164 / 5424) Filelog, journald, Kafka Prometheus + host metrics Refine Cut noise before it costs you. Drop, sample, aggregate Rate-limit by service or tag OTTL transforms with previews Per-component throughput Protect Mask PII on the host. Cards, emails, phone numbers Custom regex / OTTL rules Runs client-side, before egress Stays inside your network Route Right data to the right backend. By label, env, tenant, service Fan-out to multiple backends Per-route processing chains GitOps audit-trail every change How it all connects One control plane orchestrating every Collector in your pipeline SOURCES BACKENDS Logs Metrics Traces Grafana Splunk Elastic Azure MANAGEMENT LinkMesh Server OPAMP CONTROL PLANE OPENTELEMETRY Collectors

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.

Onboarding Collector only OpAMP or remotecfg + LinkMesh agent optional edge connector
Service auto-detection Author receiver config by hand Detects running services + suggests receivers
Log-source discovery Find log paths yourself Guided picker + template library
Kubernetes workload rollup — Discovers pods / workloads for onboarding
Reachability preflight — Flags connectivity + unreadable sources up front
Host footprint Your collector only + a small agent (package or DaemonSet)
Install guide →

First time? Walk through the full setup with screenshots on docs.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 — see Concepts 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.