Deploy HyperDX
Open-source logs, traces, metrics and session replays on ClickHouse
Just deployed
/data/db
Just deployed
OTel Collector
Just deployed
ClickHouse
Just deployed
/var/lib/clickhouse
Deploy and Host HyperDX on Railway
HyperDX is an open-source observability platform, now also shipped by ClickHouse as ClickStack. It brings logs, traces, metrics, session replays and alerts into one searchable UI, stores everything in ClickHouse, and takes data from any OpenTelemetry SDK or collector. It is MIT licensed and self-hostable.
About Hosting HyperDX
This template deploys HyperDX 2.45.0 as four services: the HyperDX app (UI, API and alerts), its OpenTelemetry collector, ClickHouse 26.10 for telemetry and MongoDB 7.0 for users, dashboards and alerts. All four build from a public GitHub repo that pins the official images by version and digest, so Railway shows you an update notice when we release a new version. ClickHouse and MongoDB keep their data on volumes and stay on the private network with generated passwords. The app waits for MongoDB and the collector waits for ClickHouse, so a full restart comes back cleanly. Ingestion requires your team's API key.
Common Use Cases
- Search and graph logs, traces and metrics from your apps in one place, with SQL or Lucene-style queries
- Debug production issues by following a request from a browser session replay to backend traces and logs
- Set alerts and dashboards on error rates, latency and log patterns, without a paid observability vendor
Dependencies for HyperDX Hosting
- ClickHouse (26.10, included, on a volume)
- MongoDB (7.0, included, on a volume)
Deployment Dependencies
- HyperDX release notes: https://github.com/hyperdxio/hyperdx/releases
- ClickStack documentation: https://clickhouse.com/docs/use-cases/observability/clickstack/overview
- Template repo (Dockerfiles, start scripts, changelog): https://github.com/aalfath/hyperdx-railway-template
Implementation Details
After deploy:
- Open the HyperDX service's public URL right away and register. The first account creates the team, and HyperDX then closes registration. The team starts with a ClickHouse connection and Logs, Traces, Metrics and Sessions sources.
- Copy the ingestion API key from Team Settings.
- Point your OpenTelemetry SDK or collector at the OTel Collector service's public domain:
OTEL_EXPORTER_OTLP_ENDPOINT=https://YOUR-COLLECTOR-DOMAIN
OTEL_EXPORTER_OTLP_PROTOCOL=http/protobuf
OTEL_EXPORTER_OTLP_HEADERS=authorization=YOUR-INGESTION-API-KEY
Requests without the key get 401. Services in the same Railway project can send to http://${{OTel Collector.RAILWAY_PRIVATE_DOMAIN}}:4318 instead. Telemetry is kept for 30 days by default.
Nothing needs filling in at deploy time: passwords, the session secret and the token encryption key are generated. Optional features (SMTP for alerts, OAuth, AI assistant) are set as variables on the HyperDX service, as the ClickStack docs describe. If you add a custom domain, update FRONTEND_URL.
Updates: when we bump the pinned version, Railway shows an update notice on your project. Read the repo's CHANGELOG.md first; breaking changes are listed at the top of each entry.
Why Deploy HyperDX 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 HyperDX 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
OTel Collector
aalfath/hyperdx-railway-templateClickHouse
aalfath/hyperdx-railway-template
