SigNoz APM for Railway Apps

SigNoz v0.145.0 is an open-source, OpenTelemetry-native platform for traces, metrics and logs. This template deploys the full stack on Railway: UI, OTel Collector, ClickHouse and ClickHouse Keeper, so other services in your project can send telemetry over the private network.

What you get

  • SigNoz server with UI, query API and alerting, with metadata on a volume
  • OTel Collector for ingest, with OTLP/HTTP on a public domain and OTLP/gRPC on a TCP proxy, both requiring a bearer token
  • ClickHouse as the telemetry store and ClickHouse Keeper for coordination, each with a volume
  • A one-shot schema migrator that creates and upgrades the schema
  • Admin account created from variables; services in the same project can send to the collector's private address without a token

Good for

  • Tracing requests across APIs, workers and queues to find slow or failing spans
  • Centralising logs and correlating them with traces and metrics
  • Tracking rate, errors and duration per service with alerts by email, Slack or webhook
  • Monitoring LLM and agent workloads instrumented with OpenTelemetry

Services in this template

  • otel-collector · from baranberkay96/signoz-railway
  • schema-migrator · image signoz/signoz-otel-collector:v0.144.13
  • signoz · image signoz/signoz:v0.145.0
  • clickhouse-keeper · from baranberkay96/signoz-railway
  • clickhouse · from baranberkay96/signoz-railway

Questions people ask

How do I log in?

Enter your email in SIGNOZ_USER_ROOT_EMAIL when deploying. Once the stack is healthy, open the signoz domain and sign in with that email and the generated SIGNOZ_USER_ROOT_PASSWORD from the service's Variables tab. First boot takes a few minutes while the schema is created.

How do I send telemetry from my services?

In the same Railway project, set OTEL_EXPORTER_OTLP_ENDPOINT to the collector's private domain on port 4318 (4317 for gRPC), set the protocol and a service name, and start the app with your language's OpenTelemetry auto-instrumentation. From outside Railway use the collector's public domain with the Authorization Bearer token.

What drives the cost?

ClickHouse is the main factor: its memory use grows with query load and its volume with retained telemetry. Set retention in Settings > General to fit the volume. The source recommends the Hobby plan as a minimum and Pro for larger telemetry volumes.

How do I scale or upgrade?

The collector is stateless, so raise its replica count as ingest grows. To upgrade, change the signoz and schema-migrator image tags and the collector's FROM tag together, and redeploy the migrator before the other services. Read the release notes first.

Full template README

Deploy and Host SigNoz with Railway

SigNoz is an open-source, OpenTelemetry-native observability platform for application traces, metrics and logs. This community template runs the complete self-hosted stack on Railway — UI, OTel Collector, ClickHouse and ClickHouse Keeper — so the other services in your project can send telemetry over the private network within minutes.

About Hosting SigNoz

A working SigNoz installation is more than one container. Telemetry arrives at the SigNoz OpenTelemetry Collector, which writes it into ClickHouse; ClickHouse needs ClickHouse Keeper for its replicated tables and cluster DDL; a one-shot migrator creates and upgrades the schema; and the SigNoz server provides the query API, dashboards, alerting and the web UI. This template wires all of that together with pinned versions, generated credentials, persistent volumes and health checks. The admin account is created from variables, public OTLP endpoints are protected by a bearer token, and services inside your Railway project can send data to the collector's private address without any token.

Common Use Cases

  • Trace requests across the APIs, workers and queues you run on Railway and find slow or failing spans.
  • Centralise application logs and correlate them with traces and metrics.
  • Track RED metrics (rate, errors, duration) per service and alert on them by email, Slack or webhook.
  • Replace a per-host SaaS APM bill with a self-hosted stack you control.
  • Monitor LLM and agent workloads instrumented with OpenTelemetry.

Dependencies for SigNoz Hosting

  • SigNoz server (signoz/signoz) with a SQLite metadata store on a volume
  • SigNoz OpenTelemetry Collector (signoz/signoz-otel-collector) for ingest and schema migrations
  • ClickHouse (clickhouse/clickhouse-server) as the telemetry store
  • ClickHouse Keeper (clickhouse/clickhouse-keeper) for coordination

Deployment Dependencies

Implementation Details

Service Image / build Role Public
signoz signoz/signoz:v0.145.0 UI, query API, alerts HTTPS domain
otel-collector signoz/signoz-otel-collector:v0.144.13 + config OTLP ingest HTTPS domain (OTLP/HTTP) and TCP proxy (OTLP/gRPC), token required
schema-migrator signoz/signoz-otel-collector:v0.144.13 One-shot ClickHouse schema job, exits when done —
clickhouse clickhouse/clickhouse-server:25.12.5 + config Telemetry store (volume) —
clickhouse-keeper clickhouse/clickhouse-keeper:25.12.5 + config Coordination (volume) —

First login. Enter your email in SIGNOZ_USER_ROOT_EMAIL when deploying. After the stack is healthy (first boot takes a few minutes while the schema is created), open the signoz domain and sign in with that email and the generated SIGNOZ_USER_ROOT_PASSWORD from the service's Variables tab.

Send telemetry from your Railway services. Add to any service in the same project:

OTEL_EXPORTER_OTLP_ENDPOINT=http://${{otel-collector.RAILWAY_PRIVATE_DOMAIN}}:4318
OTEL_EXPORTER_OTLP_PROTOCOL=http/protobuf
OTEL_SERVICE_NAME=${{RAILWAY_SERVICE_NAME}}

and start the app with your language's OpenTelemetry auto-instrumentation. For gRPC use port 4317. From outside Railway, use https://{otel-collector domain} and the header Authorization=Bearer {OTLP_PUBLIC_TOKEN}.

Scaling. The collector is stateless: raise its replica count when ingest grows. Give ClickHouse more memory/CPU for heavier queries, and set data retention in Settings → General to fit the ClickHouse volume.

Pinning and upgrades. All images are pinned. To upgrade, change the signoz and schema-migrator image tags and the collector's FROM tag together, then redeploy the migrator before the other services. Read the SigNoz release notes first.

Why Deploy SigNoz on Railway?

Railway runs the whole observability stack next to the services it watches. Telemetry stays on the private network, volumes keep your data across deploys, and you pay for the resources the stack actually uses instead of per-host or per-seat APM pricing.

Guides for this template

View SigNoz APM for Railway Apps on railway.com

Similar templates

TemplateCategoryDeploymentsDeploys
Uptime Kuma
A fancy self-hosted monitoring tool
Observability1,456
Ubuntu
Ubuntu in your network for debugging
Observability181
Grafana 13 LGTM Observability StackTracklayer
Logs, metrics and traces with Grafana, Loki, Tempo and Prometheus.
Observability10