Self Host
Traceway is fully self-hosted. You run the entire platform on your own infrastructure. This section covers how to get Traceway up and running.
⚠️
Upgrading an instance that sits behind a reverse proxy, ingress, or CDN? Read the request limits upgrade notes first. The server now trusts X-Forwarded-For from loopback only, and until TRUSTED_PROXIES lists every hop, all of your users share one rate-limit bucket.
Deployment Options
All-in-One ContainerRecommended
ClickHouse + PostgreSQL + Backend + FrontendEverything in a single Docker container managed by supervisord. No external dependencies needed.Docker Compose
Backend + Frontend + ClickHouse + PostgreSQLEach component runs as its own container, orchestrated with a single command.Minimal Container
Backend + Frontend onlyLightweight Alpine image (~20-30MB). Connect to your own external ClickHouse and PostgreSQL.SQLite
Backend + Frontend + SQLiteSingle Alpine container with embedded SQLite. No external databases needed. Optional S3 for source maps and recordings.DuckDB
Backend + Frontend + SQLite + DuckDBSingle Debian container with a columnar telemetry store. Same zero-dependency setup as SQLite with far more dashboard headroom.Browser (Monitors)
DuckDB + Playwright + ChromiumThe DuckDB container plus headless Chromium, so Playwright browser monitors run in-process. HTTP/TCP monitors work in every image.Local Setup
Backend + Frontend from sourceDevelopment setup with Go and Node.js. Requires local ClickHouse and PostgreSQL.Haloy
ClickHouse + PostgreSQL + Backend + FrontendDeploy to your own server with automatic SSL and a single YAML config using the Haloy CLI.