Gigapipe replaces Datadog and ELK with an open-source ClickHouse observability warehouse supporting logs, metrics, traces, and continuous profiling.
Gigapipe routes logs, metrics, traces, and continuous profiles into ClickHouse through a Go binary that implements the native ingestion and query protocols of Loki, Prometheus, Tempo, and Pyroscope. Originally developed under the project name qryn, the platform transpiles LogQL, PromQL, and TraceQL queries into vectorized ClickHouse SQL in real time. This architecture allows engineering teams to preserve existing Grafana dashboards while storing all telemetry in a shared analytical database.
Datadog charges per host, per metric series, and per gigabyte of logs, forcing teams to drop debug logs or sample traces to control spend. Gigapipe eliminates volume-based billing by directing all four telemetry signals into a self-hosted ClickHouse cluster. ClickHouse executes queries using columnar tables and SIMD vectorization, maintaining fast response times across billions of records. Columnar compression routinely reduces log storage five- to ten-fold, enabling long retention periods that would be cost-prohibitive on managed SaaS.
The trade-off is operational ownership. Datadog delivers a managed SaaS suite with automated anomaly detection, synthetic browser checks, and turnkey alerting across cloud providers. Gigapipe provides the storage and query translation engine, leaving dashboards to Grafana and alerts to Alertmanager. Teams migrating from Datadog can redirect Datadog agents or OpenTelemetry collectors to Gigapipe without re-instrumenting code, exchanging SaaS subscription costs for ClickHouse cluster maintenance.
Is Gigapipe free for commercial use? Yes. Gigapipe carries an AGPL-3.0 license that permits commercial self-hosting, provided modified server source code is made available to network users.
Gigapipe vs Datadog — which should an engineering team choose? Choose Datadog for a managed SaaS platform with turnkey synthetic monitoring and alerting; choose Gigapipe for high-throughput, un-sampled telemetry stored in your own ClickHouse cluster.
Can Gigapipe replace the full Grafana LGTM stack? Yes. Gigapipe serves as a single backend replacing Loki, Prometheus, and Tempo, allowing standard Grafana instances to query all three data types from one service.
Gigapipe provides an efficient open-source path for teams that want un-sampled observability on ClickHouse without replacing Grafana dashboards or re-instrumenting code. Its active development cycle and AGPL-3.0 license make it a viable on-premise foundation for engineering teams prepared to manage their own database storage. Organizations that rely on turnkey SaaS synthetic monitoring or lack dedicated ClickHouse database administrators should remain on managed platforms.
Free IDE for Java, Kotlin, Go, TypeScript and Python. Built on IntelliJ Community, fully open source, 300+ plugins.
Show that Gigapipe is listed as an open-source alternative. Paste into your README: