---
title: "Deploy Gigapipe observability"
description: "Protected Gigapipe logs, metrics, traces, and profiles."
category: "Observability"
url: https://railway.com/deploy/gigapipe-observability
---

# Deploy Gigapipe observability

Protected Gigapipe logs, metrics, traces, and profiles.

**[Deploy Gigapipe observability on Railway](https://railway.com/template/gigapipe-observability)**

- **Creator:** Anton Orel's Projects
- **Category:** Observability
- **Total deploys:** 1

## Template content

### ClickHouse

- **Image:** clickhouse/clickhouse-server:26.3.16.16-alpine@sha256:b45ab149f0d331b944b4aa2ccdd47d0242238fd39e68ec524ad63338e4b9d8f8
- **Health check:** /ping

### Gigapipe Gateway

- **Image:** caddy:2.11.4-alpine@sha256:5f5c8640aae01df9654968d946d8f1a56c497f1dd5c5cda4cf95ab7c14d58648
- **Start command:** `/bin/sh -ec 'password_hash="$(caddy hash-password --plaintext "$GATEWAY_PASSWORD")"; upstream_auth="$(printf "%s:%s" "$GATEWAY_USERNAME" "$GATEWAY_PASSWORD" | base64 | tr -d "\n")"; printf "%s\n" "$GATEWAY_CONFIG" | sed -e "s|__USERNAME__|$GATEWAY_USERNAME|g" -e "s|__PASSWORD_HASH__|$password_hash|g" -e "s|__UPSTREAM_AUTH__|$upstream_auth|g" -e "s|__UPSTREAM__|$UPSTREAM|g" >/tmp/Caddyfile; exec caddy run --config /tmp/Caddyfile --adapter caddyfile'`
- **Health check:** /healthz
- **Public domain:** Yes

### Gigapipe

- **Image:** ghcr.io/metrico/gigapipe:v5.1.1@sha256:2392ec7f1b1c4e6eecf5565ccf74a8eb3b8d46b7f0fb952e4d765e00e23626a7

## Documentation

# Deploy and Host Gigapipe on Railway

## About Hosting Gigapipe

Gigapipe is an open-source polyglot observability service, formerly qryn, that accepts and queries logs, metrics, traces, and profiles through familiar telemetry APIs. This template pairs its embedded explorer and API service with durable ClickHouse storage.

## Why Deploy Gigapipe on Railway

Railway creates private Gigapipe and ClickHouse services, generated storage and perimeter credentials, health checks, and a 5 GB volume. Only an authenticated HTTPS gateway is public, so agents and operators share one protected endpoint while ClickHouse remains private.

## Common Use Cases

- Collect and query Loki-compatible application logs.
- Centralize Prometheus metrics and OpenTelemetry traces.
- Explore correlated telemetry without operating separate backends.

## Dependencies for Gigapipe Hosting

The template uses Gigapipe, ClickHouse, Caddy, and one Railway volume. A compatible telemetry agent or SDK supplies the data.

### Deployment Dependencies

- [Gigapipe](https://gigapipe.com) provides telemetry ingestion, queries, and the embedded explorer.
- [ClickHouse](https://clickhouse.com) provides durable columnar storage.
- [Caddy](https://caddyserver.com) protects the public endpoint.
- [Railway](https://railway.com) provides private networking, generated credentials, and persistent storage.


## Similar templates

- [Pyroscope profiling](https://railway.com/deploy/pyroscope-profiling) — Protected continuous profiling with durable Pyroscope storage.
- [SigOnly](https://railway.com/deploy/sigonly) — Deploy SigNoz with a working demo app & config in one click
- [Unwrapped Spotify Music Stats](https://railway.com/deploy/wide-bold) — Unwrapped Spotify Music Stats, Estatísticas de músicas disponíveis

Open this page in a browser: https://railway.com/deploy/gigapipe-observability