EDITIONS

Community versus Pro

The Community broadcast foundation is autonomous. Pro is an optional, separately licensed extension—not a requirement for broadcasting.

Community

  • Authenticated station control
  • Media, playlists and scheduled programming
  • BPM-aware selection and configurable transitions
  • Audio analysis, Rust playout and Icecast delivery
  • History, diagnostics, backup, restore, updates and rollback
  • Best-effort community support without an SLA

No paid licence or mandatory remote licence-service request is required to start and broadcast.

Optional Pro

Pro uses a separate commercial licence. Repository documentation identifies Bliss-driven acoustic similarity, music-aware sequence optimisation and advanced transition/programming strategies as optional capabilities.

Other functions are included only when separately defined and documented. This site makes no roadmap promise.

Operational boundary

If an operator explicitly configures Pro, a licence request may transmit a licence identifier, FlowCast version, installation identifier, requested entitlement and coarse platform metadata. It does not transmit media, playlists, Icecast secrets or listener data.

A Pro licensing-service outage must not interrupt Community operation. Service images are separately licensed; the repository’s MIT licence must not be read as a claim that those OCI images’ source is open.

READY TO BROADCAST?

Build your station on infrastructure you control.

Review the Community Preview requirements, then install the current validated FlowCast Radio Automation release.