An aircraft feed can support several jobs at once: recording, analysis, a dashboard, and a downstream tool. beast-relay provides a central fan-out point for a Beast TCP stream, allowing each consumer to connect to the relay instead of building its own upstream handling.
Keep the stream moving
The relay preserves bytes by default. Bounded queues separate downstream consumers so that a slow client does not turn into an ever-growing memory backlog for everyone else. Reconnect backoff handles upstream interruptions without a tight retry loop. These are modest details, but they matter in a service expected to run continuously.
Filter only when you intend to
Optional ICAO and signal-strength filtering lets a deployment narrow the forwarded stream. Leaving filters off retains the default pass-through behavior. That distinction should be explicit in the configuration: consumers need to know whether they receive the upstream feed or a selected subset.
Make the relay observable
Health endpoints and Prometheus metrics provide a way to inspect the service alongside other receiver components. Consult the repository for supported options and deployment examples, then test with your actual downstream clients. A working socket alone does not tell the whole story about a data pipeline.
Explore beast-relay → · Source and documentation ↗