OpenTelemetry-native · OpAMP-first · On-premises
The product is evolving quickly — some features may change.
Observability Data Collection Management
Centralized orchestration and configuration management for your OpenTelemetry Collectors — from one control plane. Collect, refine, protect, and route telemetry from any source to any destination, with predictable per-collector pricing.
Self-hosted, free to start. No credit card.
Prefer to be guided in, or want product updates? Get early access:
You're on the list — we'll be in touch by email.
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.
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) |
First time? Walk through the full setup with screenshots on docs.linkmesh.io/quickstart.
Built for the platform team
LinkMesh is the control plane for your telemetry pipelines. Four principles shape every design decision.
Composable
Open standards (OpenTelemetry), no lock-in. Your data stays yours, on your infrastructure.
Predictable
Collector-based pricing — capacity you can plan. No bills exploding when telemetry volume grows.
Trustworthy
On-prem, PII-aware, audit-friendly. Sensitive fields can be masked before telemetry leaves the host.
Connected
Mesh sources to destinations through a single fabric. Route by labels, environments, tenants.
The pipeline narrative
Collect
Onboard logs, metrics, and traces from any source using standard OpenTelemetry Collectors.
Refine
Filter, enrich, sample, and reduce noisy telemetry before it reaches expensive backends.
Protect
Mask credit cards, emails, phone numbers, and arbitrary fields inside customer infrastructure.
Route
Send telemetry to the right destination based on labels, services, environments, or tenants.
For the technical model behind these capabilities — Collectors, Sources, Pipelines, Routes, Destinations — see Concepts on docs.linkmesh.io.
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.
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.
Thanks — message sent.
We'll get back to you by email shortly.