← Templates · Databases
RE
Redpanda
CommunityKafka-API-compatible streaming platform — a single binary, no ZooKeeper or JVM, for high-throughput pub/sub and event logs.
| Runs | redpandadata/redpanda:v26.2.5 |
|---|---|
| Stack | database |
| Provisioned for it | Nothing, it's self-contained |
| Verified | Not yet |
Why deploy on Railyard
Railyard runs it standalone on a server you already pay for — no addons to provision, with zero-downtime deploys and scaling still included.
Deploying Redpanda is one piece of a bigger stack you can keep building — add a database, a worker, a cache, or another app, all on the same servers you already pay for.
Good for
- A drop-in Kafka-API replacement for event streaming without running ZooKeeper or the JVM
- High-throughput pub/sub between your own apps on Railyard's private network
- Event sourcing and log-based architectures that need the Kafka wire protocol
Good to know
- The command must start with `rpk`, not `redpanda` — the image's own entrypoint script is bypassed when a custom process command is set, so the `rpk redpanda start` wrapper has to be spelled out in full or the server fails to parse its flags
- Single-node, single-broker mode (`dev-container`) — this is a standalone deployment separate from the Redpanda service bundled inside the PostHog stack template, not a shared instance
- Kafka clients connecting from other Railyard apps on the same team should use this app's private domain on port 9092; the public URL isn't a meaningful Kafka endpoint