: Native AV1 ingest via SRT (Secure Reliable Transport) and RTMP was fully stabilized, allowing high-efficiency compression pipelines for web broadcasters.
The release notes highlight the deprecation of legacy configuration endpoints in favor of a declarative JSON schema. This allows DevOps teams to provision instances programmatically via tools like Ansible, Terraform, or Kubernetes operators.
Recent release notes are dominated by the embedding of computer vision features directly into the stream processing pipeline: flussonic release notes full
: Introduced native support for listener-side stream redundancy, allowing Flussonic to accept bonded SRT feeds over multiple network paths. DVR and Storage
Then came a release that changed how the notes read: 30.0, "Archive". It introduced long-term DVR with deduplication and legal hold. The story attached was different: not a frantic midnight fix but a long, patient conversation with archivists at a national library. The team learned to weigh fidelity against storage costs and legal constraints. : Native AV1 ingest via SRT (Secure Reliable
Flussonic avoids long, unpredictable update cycles by adhering to a strict monthly release cadence alongside a continuous .
Transition to Erlang-based core, robust RTMP to HLS packaging, basic DVR engine. Hardware Acceleration & Scale Recent release notes are dominated by the embedding
Enhanced CAS (Conditional Access System) support.
During this period, Flussonic focused heavily on expanding ingestion and playback protocols to bridge the gap between traditional broadcasting and modern web streaming.