Deploy and Host Maple on Railway

Maple is an OpenTelemetry observability platform. Point your apps' OTLP exporters at it and you get traces, logs and metrics in one dashboard, with a query API and a CLI on top. The self-hosted build runs as a single container with its own local store, so there is no database to set up.

About Hosting Maple

The template runs the official Maple image with a volume at /data for the store, a health check on /health, and a public HTTPS domain. It also generates the two secrets on deploy: MAPLE_LOCAL_INGEST_KEY, which your apps use to send telemetry, and MAPLE_LOCAL_ACCESS_TOKEN, which you use to sign in to the dashboard. Copy both from the service's Variables tab once the deploy finishes. Keep the service at one replica, because the store lives on the volume and a second replica would not share it.

Common Use Cases

Collecting traces, logs and metrics from apps already instrumented with OpenTelemetry
Debugging slow requests and errors across services in one place
Keeping telemetry on infrastructure you control instead of a hosted vendor

Dependencies for Maple Hosting

A Railway volume mounted at /data
Two secrets, generated by the template

Deployment Dependencies

Self-hosting guide: https://maple.dev/docs/self-hosting
Connecting your apps: https://maple.dev/docs/self-hosting/connect

Why Deploy Maple 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 Maple 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.