Deploy tracedown-core-template

Deploy and Host tracedown-core-template on Railway

Tracedown is a self-hosted API monitoring platform: probes written in the Lace scripting language run against your endpoints on schedules, with assertions, multi-step journeys, notifications, and a full dashboard. This template deploys the complete Tracedown Core stack — eight JVM services, PostgreSQL (TimescaleDB), Redis, and an edge proxy serving the UI.

Links

• Live demo: demo.tracedown.dev — this exact template running in production, browsable read-only
• Documentation: tracedown.dev — operator docs: deployment, agents, variables, notifications
• Lace language: lacelang.dev — the probe scripting language: spec, grammar, examples
• Template source: github.com/tracedown/tracedown-railway-template
• Tracedown Core: tracedown-core-backend · tracedown-core-frontend · tracedown-probe-agent — Apache 2.0

About Hosting tracedown-core-template

The template deploys eleven services in one click: the API gateway (which runs schema migrations and internal-CA init on startup), probe scheduler, result ingestor, notification dispatcher, email service, metrics service, aggregate worker, realtime WebSocket service, a Caddy edge proxy that serves the dashboard and routes /api, /ws, and /metrics, plus TimescaleDB and Redis. Nothing builds from source — every service fetches versioned release artifacts from GitHub, so deploys are fast and upgrades are a one-line version bump. Secrets are generated at deploy time and shared by reference; you enter only your admin email and password.

Common Use Cases

• Uptime and API monitoring for your own services, with email and webhook alerts on failure and recovery
• Multi-step API journey testing (auth flows, CRUD sequences) with assertions on status, latency, and response content
• Multi-region latency measurement by connecting self-hosted probe agents to one central dashboard

Dependencies for tracedown-core-template Hosting

• None to start — the database, cache, and all services are included in the template
• One or more Tracedown probe agents (deployed separately, anywhere) enrolled via one-time bootstrap tokens over mutual TLS

Implementation Details

Services talk over Railway's private network; only the proxy is public. Redis A/B/C are independently configurable environment variables that point at the single bundled Redis by default — deploy extra instances and repoint them if you want to split operational, cache, and resource-cache traffic. Probe agents are deliberately not part of the template: they hold long-lived mTLS identities and are bootstrapped against the running gateway with a one-time token, so add them after the stack is up. Sign in with the admin credentials you set at deploy; upgrading later is editing VERSION / FRONTEND_VERSION and redeploying.

Why Deploy tracedown-core-template 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 tracedown-core-template 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.