Self-host HyperDX with Levelrail
An observability platform that brings logs, traces, metrics and session replays together in one search UI. MIT licensed. Runs the all-in-one image with its bundled ClickHouse, MongoDB and OpenTelemetry collector, so it needs about 2 GB of memory. On first open, the setup page asks you to create the admin login.
- Authorhyperdxio
- LicenceMIT
- Memory2 GiB
- Archarm64
- Services1
How to self-host HyperDX
-
Pull the images
One image is pulled on your server.
Show images
hyperdx/hyperdx-all-in-one:2.43.1
-
Create the app
One service starts in a single Compose app, with 3 named volume mounts for your data, on port 8080.
-
Fill in the secrets
1 setting is preset, you do not have to fill in anything.
-
Open it
Without a domain the app gets an sslip.io address; add --domain SERVICE=HOST to use your own.
After the first start
- Open the app and register the first user on the sign-up page.
HyperDX requirements
- Memory
- About 2 GiB
- Architectures
- amd64 image published, arm64 image published
- Ports
- 8080
- Domain
- Optional, an sslip.io address is used without one
- Settings
- none to fill in
- License
- MIT, permissive license
- Listed. It is in the catalog but not verified. Back up the data volume before changing an image tag.
Install Levelrail first
On a server with Levelrail running, run the command above, or open the dashboard: Apps, New app, Browse templates, then HyperDX. New to Levelrail? Install it on a fresh VPS first.
docker pull ghcr.io/glincker/levelrail:latest Then levelrail-cli login --device. See Getting started and the HyperDX docs page.
Deploy HyperDX your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy HyperDX from the CLI
levelrail-cli templates deploy hyperdx --name my-hyperdx Deploy HyperDX with the API
curl -X POST -H "Authorization: Bearer $TOKEN" \
https://levelrail.example.com/api/v1/service-templates/hyperdx/deploy HyperDX configuration
HyperDX services
| Service | Image | Ports | Volumes |
|---|---|---|---|
| hyperdx | hyperdx/hyperdx-all-in-one:2.43.1 | 8080 | mongo -> /data/dbch_data -> /var/lib/clickhousech_logs -> /var/log/clickhouse-server |
HyperDX environment variables
| Variable | Service | Value |
|---|---|---|
| FRONTEND_URL | hyperdx | Preset by the template |
Ports and volumes
- Ports
- 8080
- Volumes
- 3 named mounts: mongo -> /data/db, ch_data -> /var/lib/clickhouse, ch_logs -> /var/log/clickhouse-server
HyperDX FAQ
How much memory does HyperDX need?
The catalog lists about 2 GiB of memory for HyperDX.
Does HyperDX run on arm64?
For HyperDX, an arm64 image is published; amd64 is image published.
What licence is HyperDX under?
HyperDX is licensed under MIT, which is permissive, with few conditions on reuse.
Does HyperDX need configuration before it starts?
No. The template fills in its own defaults.
Which ports does HyperDX use?
HyperDX listens on port 8080 inside the stack.
Where does HyperDX keep its data?
In named volumes: mongo mounted at /data/db, ch_data mounted at /var/lib/clickhouse and ch_logs mounted at /var/log/clickhouse-server.
Can I deploy HyperDX on Dokploy or Dokku?
The services and pinned images on this page can be run on any Docker host. The public Dokploy templates list has an entry with the id hyperdx for this app, so check that entry as well. Dokku deploys container images with its own commands, so the pinned image hyperdx/hyperdx-all-in-one:2.43.1 is what you deploy there.