SigNoz on Railway
Open-source, OpenTelemetry-native APM for traces, metrics and logs, self-hosted on Railway with ClickHouse.
SigNoz is an open-source observability platform built on OpenTelemetry. It collects traces, metrics and logs in one place, with dashboards, alerting and a query UI.
Teams use it to find slow or failing requests, correlate logs with traces, track error rate and latency per service, and replace a per-host SaaS APM bill. Datadog and New Relic are the commercial products it is usually compared with.
The core is MIT licensed; code under ee/ uses the SigNoz Enterprise License, and gated features stay off without a licence key.
What SigNoz can do
- Distributed tracing
- Logs and metrics in one UI
- Dashboards and alerts by email, Slack or webhook
- OpenTelemetry ingest over OTLP (HTTP and gRPC)
- ClickHouse as the telemetry store
- Bearer-token protection for public OTLP endpoints
What people use it for
- Tracing requests across APIs, workers and queues
- Centralising logs and linking them to traces
- Alerting on rate, errors and duration
- Monitoring LLM and agent workloads instrumented with OpenTelemetry
Videos
Running SigNoz on Railway
The Railway template deploys SigNoz, an OpenTelemetry Collector, a one-shot schema migrator, ClickHouse and ClickHouse Keeper with volumes. Services in the same project can send telemetry to the collector's private address without a token; public OTLP endpoints require a bearer token. The template's own estimate is about 0.95 GB of RAM when idle and roughly 2.5 to 3.8 GB typical, with ClickHouse as the largest part, so Hobby is the minimum plan.
SigNoz templates on Railway
Tracklayer templates are listed first. Other SigNoz templates follow, ordered by total deployments on Railway. How this works.
Deployment numbers as of 2026-11-20.
Questions about SigNoz
How do I sign in?
Enter your email in SIGNOZ_USER_ROOT_EMAIL when deploying and use the generated SIGNOZ_USER_ROOT_PASSWORD from the signoz service's Variables tab.
How do my Railway services send telemetry?
Set OTEL_EXPORTER_OTLP_ENDPOINT to the collector's private domain on port 4318 (HTTP) or 4317 (gRPC) and start the app with OpenTelemetry instrumentation.
What drives the cost?
ClickHouse memory and volume size, which grow with ingest and retention. The template documents estimates; set a short retention on small plans.
Can I send data from outside Railway?
Yes, using the collector's public endpoint and an Authorization Bearer token.
What does the licence cover?
The core is MIT. Enterprise features need a SigNoz licence key.
Guides
Similar apps
Tracklayer maintains the templates marked as such; SigNoz is a trademark of its owners and this site is not affiliated with them.