LinkMesh

Design partners

Install it with us, then tell us what's wrong with it.

LinkMesh is in early access. We're looking for a small number of teams who run collector fleets somewhere a vendor cloud can't reach — and who are willing to put the product in front of their real environment and be blunt about what it gets wrong.

In return you get the people who build it, sitting with you through the install.

Who we're looking for

One shape of team, specifically — because that's the case LinkMesh was built for and the case we most need to get right:

  • Your collectors can't reach a vendor cloud — either the network is genuinely isolated, or a policy names where control-plane metadata may live. Banks, insurers, public sector, healthcare, critical infrastructure, industrial networks.
  • You run enough collectors that managing them by hand hurts — roughly 25 and up, across more than one environment.
  • You have a real environment to point it at, not a slide about one. A lab or a staging fleet is fine; a hypothetical is not.
  • Someone on your side can spend an hour or two with us and say what they actually think.

Who this isn't for

If your collectors can reach a vendor cloud and you're content for your fleet inventory and configuration to live there, the established cloud-hosted tools are the lower-friction choice and you should take them. We wrote that out in full in our Grafana Fleet Management comparison, and we meant it.

This programme isn't a discount scheme or a way to get a demo. If you just want to try the product, don't apply — download it instead. The Community tier covers 25 collectors with the full feature set, no time limit and no credit card, and you never have to talk to us.

What you get

  • A hands-on install session. We work through the install on your infrastructure with you — not a scripted demo, your environment and its awkward parts.
  • An unlimited license for as long as we're working together, with no collector cap.
  • A direct line to an engineer. Your questions reach the people writing the code, not a ticket queue.
  • Real influence on what gets built next. We're early enough that this is true rather than flattering.

What we ask in return

Your honest assessment — particularly the unflattering half. What was confusing, what was missing, what you'd have to explain to a security reviewer, and what would stop you rolling it out. An install that goes badly and gets described accurately is worth more to us than a polite one that goes well.

We're not asking for money, a public case study, a logo on our homepage, or a reference call. If you later want to do any of those, that's a separate conversation and the answer can be no.

What LinkMesh actually is today

So you can judge whether it's worth your hour before you write to us:

  • It runs on your infrastructure. A single binary, a Docker image or a Kubernetes deployment, with embedded storage — no external database and no worker tier to stand up, and no calls out to a CDN at runtime. The control plane and every piece of fleet metadata stay inside your perimeter.
  • Collectors authenticate with a durable Bearer token over TLS you terminate at your own ingress. Enrollment is an explicit onboarding step, not an open registration endpoint.
  • Credentials live in a built-in vault and are rendered only at delivery, so secrets never land in stored configs and never get committed to Git.
  • Pricing is per collector, not per gigabyte — so the bill doesn't move when your telemetry volume does.
  • It's early access, and it has edges. The Trust page lists what we do and explicitly don't do, and the features page has the detail. Finding the edges is rather the point of this programme.

Apply

Tell us about your fleet and what makes it awkward. A few sentences is plenty — a real reply from a person comes back either way, including if we think you're better served by something else.

We use what you send here to answer you about this programme and nothing else. Details in our privacy notice. You can also just email [email protected].