Deploy and Host Zipkin on Railway

Zipkin is a distributed tracing system: it collects timing data from the services in your architecture and shows which calls were slow and where requests spent their time.

About Hosting Zipkin

This template runs the official openzipkin/zipkin:3 image with the default in-memory storage on port 9411. Traces are kept in memory and are lost when the service restarts; the UI and the span API are served from the same public URL. Zipkin has no built-in authentication, so anyone who knows the URL can view traces and post spans.

Common Use Cases

Trace requests across microservices and find slow calls
Inspect service dependency graphs
Receive spans from instrumented apps at /api/v2/spans

Dependencies for Zipkin Hosting

One service; nothing else (in-memory storage, no volume)

Deployment Dependencies

Why Deploy Zipkin on Railway?

Railway gives you a public HTTPS URL and automatic restarts with no server to maintain. Open the URL after the deploy to see the Zipkin UI, and point your tracers at https:///api/v2/spans. Restrict access before sending sensitive traces.