Partners and ecosystem

Vendor neutrality is a property of the protocols, not a slogan. Gigapipe speaks the same APIs that agents, dashboards and instrumentation already target, so the tools below reach it without a plugin, a fork or a proprietary SDK. Each one states which direction the integration runs and links to the page that documents it.
The ecosystem
Tools that write into Gigapipe, and projects Gigapipe is read with. The tag on each card says which direction the integration runs.
Apache-2.0

Ships telemetry into Gigapipe

Odigos instruments Kubernetes workloads with eBPF and OpenTelemetry, without touching application code. Gigapipe is a supported destination in Odigos OSS: pick it in the Odigos UI or apply the manifest, give it an endpoint and an API key and secret, and traces, metrics and logs land in Gigapipe.

Traces Metrics Logs Profiles
Gigapipe in the Odigos backend docs
CNCF Sandbox

Dashboards Gigapipe is read with

Perses is a CNCF Sandbox project and an open specification for dashboards, with datasources for Prometheus, Loki, Tempo and Pyroscope and a dashboard-as-code workflow. Gigapipe answers those same APIs, and is listed among the projects adopting Perses. It is the dashboard front end for teams who would rather not run Grafana.

Gigapipe in the Perses adopters list

Where Gigapipe is listed

CNCF LandscapeObservability and Analysis › Observability OpenTelemetry vendor registrylisted as qryn, our former name, with native OTLP support

Want your integration listed here?

If your tool writes into Gigapipe or reads from it, the APIs are open and the backend is AGPL-3.0. Send us a link to your docs and we will add it.

Send your telemetry somewhere neutral.