Skip to main content
The fastest way to try Alginte is the Docker image. You need a reachable Kafka broker.
Start in the playground if you are new here, or have no cluster to point at yet: Alginte with a bundled broker and sample data, one command, isolated on your machine. A stream designed there comes to your cluster as a file (from the playground to your cluster).

​
Requirements

  • A Kafka cluster — Alginte connects as a client; nothing is installed on your brokers.
  • Docker, or Java 25 for the standalone JAR.

​
Tested against

Every release is smoke-tested against a matrix of brokers: the app is started cold from the published image and driven through cluster management and a deployed Kafka Streams topology. Kafka 3.7 and newer is the tested range — including deploying and running stream topologies, and including Redpanda. Older brokers are untested rather than known-broken: Alginte uses Kafka 4.x client libraries, which negotiate down, so a 3.x broker below 3.7 may well work. If you run one, we would like to hear about it.
1

Run the image

Point Alginte at your broker and expose the UI on port 8888:
2

Open the UI

Browse to http://localhost:8888.
Alginte fails fast on startup if the broker is unreachable — this is by design (see Troubleshooting for the common causes). Inside a container, localhost is the container itself, so SPRING_KAFKA_BOOTSTRAPSERVERS=localhost:9092 will not find a broker on your host. Use a hostname/IP reachable from the container, or join the broker’s Docker network — see Run with Docker.

​
Prefer no container?

Download the standalone fat JAR from the community repo’s GitHub Releases and run it with Java 25 — Run with the JAR has the download, the checksum and the bind-address boundary. The Docker image stays the recommended channel.

​
Next steps

Configuration

Wire up Schema Registry, Connect, and ksqlDB.

Authentication

Turn on login before exposing Alginte on a network.