Deploy Kafka UI
Web UI for Kafka and Redpanda: topics, messages, consumer groups, schemas
Just deployed
/etc/kafkaui
Deploy and Host Kafka UI on Railway
Kafka UI (kafbat/kafka-ui) is a free, open-source web console for Apache Kafka. It lets you browse brokers, topics, partitions and consumer groups, read and produce messages, and manage topic settings. It also works with Kafka-compatible brokers such as Redpanda, plus Schema Registry and Kafka Connect, from one browser tab.
About Hosting Kafka UI
This template runs Kafka UI 1.5.0 as one service, built from a small GitHub wrapper around the official kafbat image (pinned by version and digest). It is meant to be added to a Railway project that already runs Kafka or Redpanda. Set KAFKA_BOOTSTRAP_SERVERS to your broker's private address, for example kafka.railway.internal:9092 or ${{Kafka.KAFKA_PRIVATE_BOOTSTRAP}} with our Apache Kafka template, and the UI connects over Railway's private network. The login form is always on: the username defaults to admin and the password is generated. Clusters you add in the UI are saved on a volume, so they survive redeploys.
Common Use Cases
- Browse topics, partitions and consumer group lag of a Kafka or Redpanda broker running in the same Railway project
- Read, search and produce test messages while you build or debug an event-driven app
- Create, configure and delete topics, and inspect Schema Registry subjects and Kafka Connect connectors
Dependencies for Kafka UI Hosting
- A Kafka-compatible broker reachable from the service (Apache Kafka, Redpanda or a managed Kafka cluster)
- A Railway volume for the clusters saved from the UI (created by the template)
Deployment Dependencies
- Kafka UI source and docs: https://github.com/kafbat/kafka-ui and https://ui.docs.kafbat.io/
- Release used by this template: https://github.com/kafbat/kafka-ui/releases/tag/v1.5.0
- Template wrapper (Dockerfile, start script, changelog): https://github.com/aalfath/kafka-ui-railway-template
Implementation Details
Point the UI at a broker in the same project (replace Kafka with your service's name):
KAFKA_BOOTSTRAP_SERVERS=${{Kafka.RAILWAY_PRIVATE_DOMAIN}}:9092
Leave KAFKA_BOOTSTRAP_SERVERS empty to add clusters in the UI instead (Dashboard, then "Configure new cluster"). Brokers with SASL or TLS can be set up there, or with the upstream KAFKA_CLUSTERS_0_* variables. Your login password is in the service's SPRING_SECURITY_USER_PASSWORD variable. The start script refuses to run with a password shorter than 12 characters or with AUTH_TYPE=DISABLED. OAuth2 and LDAP are configured as in the kafbat docs. Updates to the pinned image arrive as "update available" notices from the GitHub repo.
Why Deploy Kafka UI 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 Kafka UI 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.
Template Content
