Deploy SigNoz
SigNoz v0.150.0: traces, metrics and logs on ClickHouse, OTLP ready
Collector
Just deployed
ClickHouse
Just deployed
/var/lib/clickhouse
Just deployed
/var/lib/signoz
Deploy and Host SigNoz on Railway
SigNoz is an open-source, OpenTelemetry-native observability platform. It collects traces, metrics and logs from your applications and shows them in one UI with service maps, dashboards, log search, exceptions and alerts. It stores telemetry in ClickHouse and is a self-hosted alternative to Datadog and New Relic.
About Hosting SigNoz
This template deploys SigNoz v0.150.0 as three services. SigNoz (UI, query service and alerts) is public. Its users, dashboards and alert rules live in SQLite on a volume. The Collector (SigNoz's OpenTelemetry Collector) applies the ClickHouse schema migrations when it starts, then accepts OTLP: gRPC on the private network, and HTTP on its own public domain behind a generated bearer token. ClickHouse with an embedded Keeper stores the telemetry on a volume, behind a generated password. After deploy, open the SigNoz URL and create the first account. It becomes the admin, and sign-up closes after that.
Common Use Cases
- Tracing requests across the services in your Railway project to find slow endpoints and errors
- Centralising application logs and searching them next to the traces they belong to
- Dashboards and alerts on application and infrastructure metrics sent over OpenTelemetry
Dependencies for SigNoz Hosting
- ClickHouse (included, with embedded ClickHouse Keeper)
- An OpenTelemetry SDK or agent in the apps you want to observe
Deployment Dependencies
Implementation Details
Send telemetry from another Railway service over the private network (no token needed):
OTEL_EXPORTER_OTLP_ENDPOINT=http://${{Collector.RAILWAY_PRIVATE_DOMAIN}}:4317
OTEL_EXPORTER_OTLP_PROTOCOL=grpc
From outside Railway, use the Collector's public domain and the token in its OTLP_INGEST_TOKEN variable:
OTEL_EXPORTER_OTLP_ENDPOINT=https://YOUR-COLLECTOR-DOMAIN
OTEL_EXPORTER_OTLP_PROTOCOL=http/protobuf
OTEL_EXPORTER_OTLP_HEADERS=Authorization=Bearer YOUR-OTLP-INGEST-TOKEN
The ingest pipelines start after the first account exists, because the Collector takes its configuration from SigNoz. Every service builds from the template's GitHub repository with pinned image versions and digests. When the repository is updated, Railway offers you the update, and the changelog lists any breaking changes first. SMTP for alert emails is optional: add the SIGNOZ_EMAILING_* variables from SigNoz's configuration reference to the SigNoz service.
Why Deploy SigNoz on Railway?
Railway is a singular platform to deploy your infrastructure stack. Railway will host your infrastructure so you don't have to deal with configuration, while allowing you to vertically and horizontally scale it.
By deploying SigNoz on Railway, you are one step closer to supporting a complete full-stack application with minimal burden. Host your servers, databases, AI agents, and more on Railway.
Template Content
Collector
aalfath/signoz-railway-templateClickHouse
aalfath/signoz-railway-template
