Repolode
Submit
metrico

metrico/gigapipe

Self-hosted observability backend that accepts logs, metrics, traces and profiles and serves them through Loki, Prometheus, Tempo and Pyroscope compatible APIs.

Open-source alternative to:Datadog

View on GitHubWebsite
Stars
1,714
Forks
103
Open issues
46
Last commit
18 hours ago

What is it?

Gigapipe is an open-source observability stack for logs, metrics, traces and profiling. It implements the Loki, Prometheus, Tempo and Pyroscope APIs, so existing clients, SDKs and the native Grafana datasources can point at it without plugins. Queries use LogQL, PromQL and TraceQL.

Data can be ingested through OpenTelemetry (including OTLP over HTTP and gRPC, and an OTLP profiles endpoint), or through native Loki, Prometheus, Tempo/Zipkin and Pyroscope APIs. The README also lists Influx, Datadog and Elastic formats. Storage is ClickHouse, DuckDB or GigAPI with S3 object storage. A built-in Explorer called View provides a browser UI for logs, metrics and traces without Grafana.

The project is licensed under AGPL-3.0 and was formerly named qryn.

Key features

  • 01Loki, Prometheus, Tempo and Pyroscope compatible APIs for existing clients and Grafana datasources
  • 02Queries with LogQL, PromQL and TraceQL, including TraceQL metrics endpoints
  • 03Ingestion via OpenTelemetry (OTLP metrics, traces, logs, profiles) and several vendor formats
  • 04Storage on ClickHouse, DuckDB or GigAPI, with S3 object storage support
  • 05Built-in View explorer for logs, metrics and traces without Grafana
  • 06DOT graph rendering for profiles with node limits and readable values

Use cases

  • Replacing a Grafana LGTM stack with a single self-hosted backend
  • Keeping observability data on-premises under your own control
  • Sending OpenTelemetry or existing Loki/Prometheus agents to one backend without changing instrumentation
  • Running continuous profiling with Pyroscope SDKs or OTLP profile exporters

Quick start

  1. 1

    Read the Configuration & Docker guide in docs/configuration.md to set up and deploy gigapipe

Things to know

  • Released under AGPL-3.0, a copyleft license that requires sharing modifications when offered as a network service.
  • Storage depends on a backend such as ClickHouse, DuckDB or GigAPI with S3, so you must set up and run that infrastructure yourself.

Topics

#observability#logs#metrics#tracing#opentelemetry#clickhouse#grafana#promql#gigapipe#lgtm

FAQ

What is gigapipe?
Self-hosted observability backend that accepts logs, metrics, traces and profiles and serves them through Loki, Prometheus, Tempo and Pyroscope compatible APIs. Gigapipe is an open-source observability stack for logs, metrics, traces and profiling. It implements the Loki, Prometheus, Tempo and Pyroscope APIs, so existing clients, SDKs and the native Grafana datasources can point at it without plugins. Queries use LogQL, PromQL and TraceQL.
Is gigapipe free to use? What license does it have?
gigapipe is open source under the AGPL-3.0 license. Check the license terms before using it in commercial products.
Is gigapipe still maintained?
Actively maintained. The last commit to gigapipe was on Oct 20, 2026.
What can I use gigapipe for?
Replacing a Grafana LGTM stack with a single self-hosted backend Keeping observability data on-premises under your own control Sending OpenTelemetry or existing Loki/Prometheus agents to one backend without changing instrumentation Running continuous profiling with Pyroscope SDKs or OTLP profile exporters
How do I install gigapipe?
Read the Configuration & Docker guide in docs/configuration.md to set up and deploy gigapipe
Where can I get gigapipe?
The source code and installation instructions are on GitHub: https://github.com/metrico/gigapipe

Summary generated by AI from the project's README. GitHub stats refresh daily.

Related projects