Sanity
Studio stops being a plugin host and starts being an SDK host.
Comparison · DevOps
Liquidsoap vs OSSEC
A side-by-side editorial comparison of Liquidsoap and OSSEC — release velocity, themes, recent moves, and the top alternatives to consider.
Liquidsoap vs OSSEC: at a glance
What is Liquidsoap?
Liquidsoap opens its 2.5 line with subtitles as a first-class content type and a streaming server of its own
The 2.5.x rolling release carries the accumulated 2.5.0 changelog, and it is the largest body of work Liquidsoap has staged in over a year. Subtitles become a dedicated content type alongside audio and video, with native SRT decoding, FFmpeg subtitle encode and decode, bitmap passthrough, callbacks, transformations and dynamic insertion. An Icecast-compatible server ships as icecast.server, with source authentication, mount points, relay and per-listener encoding. Underneath, the source composition model was rewritten: switch, fallback, rotate and random drop their parallel list parameters for per-source methods, and switching now fades by default.
What is OSSEC?
A 20-year-old HIDS is being re-engineered for scale and modern crypto.
OSSEC has moved through three substantial releases in six months under Atomicorp maintainership. The 4.0.0 release broke backwards compatibility by making AES the default agent transport and modernized file integrity monitoring to SHA-256; 4.2.0 followed with a multi-threaded analysisd pipeline and a self-contained Windows agent installer. The work is concentrated in a small number of hands — most PRs in these releases carry a single contributor tag.
Liquidsoap vs OSSEC: editorial side-by-side
Liquidsoap
6.3DEVOPS
Liquidsoap opens its 2.5 line with subtitles as a first-class content type and a streaming server of its own
◆ Current state
The 2.5.x rolling release carries the accumulated 2.5.0 changelog, and it is the largest body of work Liquidsoap has staged in over a year. Subtitles become a dedicated content type alongside audio and video, with native SRT decoding, FFmpeg subtitle encode and decode, bitmap passthrough, callbacks, transformations and dynamic insertion. An Icecast-compatible server ships as icecast.server, with source authentication, mount points, relay and per-listener encoding. Underneath, the source composition model was rewritten: switch, fallback, rotate and random drop their parallel list parameters for per-source methods, and switching now fades by default.
◆ Where it's heading
Liquidsoap is expanding on two axes at once. It is broadening what a stream can carry - subtitles are a third content modality in a system that has understood two - and it is moving up the stack from a source that feeds Icecast into something that can be the Icecast. The language work points the same way: a source(_) type for unknown content, callback release semantics, and effect-scoped clocks are the kind of changes made when scripts are getting large enough that lifetime and typing errors cost real production time.
◆ Prediction
The 2.5.0 final should follow the rolling branch within a release cycle, and the migration guide already shipped for the composition parameter changes suggests the breaking surface is considered settled. Watch whether subtitle support reaches the harbor and Icecast server paths, which the current notes do not say.
OSSEC
3.8DEVOPS
A 20-year-old HIDS is being re-engineered for scale and modern crypto.
◆ Current state
OSSEC has moved through three substantial releases in six months under Atomicorp maintainership. The 4.0.0 release broke backwards compatibility by making AES the default agent transport and modernized file integrity monitoring to SHA-256; 4.2.0 followed with a multi-threaded analysisd pipeline and a self-contained Windows agent installer. The work is concentrated in a small number of hands — most PRs in these releases carry a single contributor tag.
◆ Where it's heading
This is a modernization program, not feature expansion. The pattern across releases is removing decade-old constraints: single-threaded analysis, Blowfish crypto, MD5/SHA-1 integrity hashes, 2GB file limits, dependency-hunting Windows installs. Each release trades compatibility for correctness, and the project has been willing to force server-before-agent upgrade ordering to get there.
◆ Prediction
Expect the threading work started in 4.2.0 to extend further into the manager daemons, and continued removal of legacy crypto paths. Whether the Blowfish fallback survives another major version is the open question the entries don't answer.
Alternatives to Liquidsoap and OSSEC
Other DevOps products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either Liquidsoap or OSSEC.
Dapr
Three branches, one backport queue: Dapr is paying down workflow durability bugs
GitHub
Security and governance controls catch up to the Copilot build-out
Manticore Search
The 29.0 line is stabilizing in public; 29.1 opens with load-tool work rather than engine work.
Tigris
Tigris keeps publishing its architecture, and the newest post opens up the storage engine itself.
WeWeb
WeWeb is turning the apps it builds into AI products, and metering the AI as it goes.
See all Liquidsoap alternatives → · See all OSSEC alternatives →
Recent activity from Liquidsoap and OSSEC
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1d agoLiquidsoapSubtitles become a content type and Liquidsoap ships its own Icecast server ⚡
- 10d agoLiquidsoapLiquidsoap Rolling Release 2.4.x
- 17d agoOSSECMulti-threaded analysisd and a self-contained Windows agent land in 4.2.0 ⚡
- 2mo agoLiquidsoapQueue removal commands and O(1) clock propagation in Liquidsoap 2.4.5
- 4mo agoLiquidsoapLiquidsoap 2.4.4 supersedes 2.4.3 days after release
- 4mo agoLiquidsoapRaw string literals arrive in Liquidsoap 2.4.3
- 4mo agoOSSECRC1 adds SMTP auth, IPv6 whitelisting, and files over 2GB
- 6mo agoOSSECAES becomes the default agent transport in 4.0.0 ⚡
- 7mo agoLiquidsoapLiquidsoap 2.4.1 opens the stabilization phase
Frequently asked questions
What is the difference between Liquidsoap and OSSEC?
They serve adjacent needs but don't currently overlap on shipped themes. Liquidsoap is currently shipping more aggressively (velocity 6.3 vs 3.8), with 1 editorial sparks in the last 30 days against 1. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Is Liquidsoap better than OSSEC?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Liquidsoap is currently shipping more aggressively (velocity 6.3 vs 3.8), with 1 editorial sparks in the last 30 days against 1. For your specific use case, the alternatives sections above list other DevOps products to evaluate alongside.
What are the best alternatives to Liquidsoap?
Top Liquidsoap alternatives in DevOps are ranked by recent ship velocity. Browse the "Liquidsoap alternatives" section above for the current picks, or visit /alternatives/liquidsoap for the full list with editorial commentary on each.
What are the best alternatives to OSSEC?
Top OSSEC alternatives in DevOps are ranked by recent ship velocity. Browse the "OSSEC alternatives" section above for the current picks, or visit /alternatives/ossec for the full list with editorial commentary on each.