OpenZipkin
zipkin.io
- Free plan
- Web
- Self-hosted
What OpenZipkin is
OpenZipkin is free, self-hosted tracing software for investigating latency in service architectures. Applications must be instrumented before they can send trace data. Users can open traces by ID or search by service, operation name, tags, and duration. The interface summarizes the proportion of time spent in each service and indicates whether operations failed. A dependency diagram shows how many traced requests passed through each application. Listed transports include HTTP, Kafka, ActiveMQ, gRPC, and RabbitMQ. Storage can be in memory or use MySQL, Cassandra, or Elasticsearch. Instrumentation libraries include supported and community-supported options for C#, Go, Java, JavaScript, Ruby, Scala, PHP, Python, and Lua. Zipkin supports OpenTelemetry and can run with Docker, Java, Homebrew, or from source. The self-contained executable JAR requires Java 17 or higher. The web UI has no built-in authentication.
Who it suits
It suits development and operations teams tracing distributed services that can instrument their applications. Teams should be comfortable running self-hosted infrastructure and handling web-UI authentication separately.
Good to know, and what to watch
- Free self-hosted tracing
- Trace search by multiple fields
- Service dependency diagram
- Several storage backends
- OpenTelemetry support
- Applications require instrumentation
- Web UI lacks authentication
- Self-contained JAR requires Java 17+
- No tail-based sampling
Plans
Every plan and priceZipkin (open-source software)
Free plan
The verdict
OpenZipkin offers trace search, service summaries, dependency visualization, and several collection and storage options. Its self-hosted setup and unauthenticated web interface make deployment and access control important considerations.
What the maker publishes
- Data collection
- Applications must be instrumented to report trace data; listed transports include HTTP, Kafka, ActiveMQ, gRPC, and RabbitMQ. source
- Dependency diagram
- The UI includes a dependency diagram showing how many traced requests went through each application. source
- Deployment
- The quickstart describes running Zipkin with Docker, Java, Homebrew, or from source. source
- Instrumentation
- The instrumentation list includes supported and community-supported libraries for languages including C#, Go, Java, JavaScript, Ruby, Scala, PHP, Python, and Lua. source
- Java requirement
- The quickstart says Java 17 or higher is required for its self-contained executable JAR option. source
- Maker
- OpenZipkin is the open-source organization that stewards Zipkin code, documentation, specifications, and support; Zipkin was originally created at Twitter. source
- Purpose
- Zipkin collects and looks up tracing data to help troubleshoot latency in service architectures. source
- Security limitation
- The architecture page says the web UI has no built-in authentication. source
- Storage
- The site lists in-memory storage and persistent backends including MySQL, Cassandra, and Elasticsearch. source
- Support
- The project directs users to its Gitter chat for questions and says the OpenZipkin organization is primarily volunteers. source
- Trace search
- Users can open a trace by ID or query by service, operation name, tags, and duration. source
- Trace summaries
- The UI summarizes the percentage of time spent in a service and whether operations failed. source
Checked against the maker's pages on 2 Oct 2026.