← Back to home
Comparison · DevOps

Liquidsoap vs Rivet

A side-by-side editorial comparison of Liquidsoap and Rivet — release velocity, themes, recent moves, and the top alternatives to consider.

Liquidsoap vs Rivet: at a glance

FeatureLiquidsoapRivet
SectorDevOpsDevOps
Velocity score6.37.5
Sparks · 30d02
Top themesaudio-streaming, subtitles, icecast, ocamlactors, serverless, storage engine, s3
Last editorial update2mo ago3d ago
WebsiteVisit →—

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.

Read the full Liquidsoap trajectory →

What is Rivet?

Rivet 3.0 Preview runs as one stateless binary on WarpDrive, with S3 as its only dependency.

Rivet has spent two months building infrastructure for long-lived actors and AI agents: BYOC in customer clouds, OpenTelemetry tracing, actor-scoped JWTs, Pi agent runtimes and agentOS Hosted VMs. On October 5 it said 3.0 would replace NATS with S3. The October 26 3.0 Preview delivers that: a new storage engine, WarpDrive, promises bottomless storage on S3 at SSD speed, and Rivet becomes a single stateless binary.

Read the full Rivet trajectory →

Liquidsoap vs Rivet: editorial side-by-side

L6.3

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.

R
Rivet
DEVOPS
7.5

Rivet 3.0 Preview runs as one stateless binary on WarpDrive, with S3 as its only dependency.

◆ Current state

Rivet has spent two months building infrastructure for long-lived actors and AI agents: BYOC in customer clouds, OpenTelemetry tracing, actor-scoped JWTs, Pi agent runtimes and agentOS Hosted VMs. On October 5 it said 3.0 would replace NATS with S3. The October 26 3.0 Preview delivers that: a new storage engine, WarpDrive, promises bottomless storage on S3 at SSD speed, and Rivet becomes a single stateless binary.

◆ Where it's heading

Each release removes operational burden: BYOC moved the control plane into the customer's cloud, and 3.0 reduces the self-hosted footprint to one binary plus an S3 bucket. The agent work (Pi, agentOS) sits on top as the main workload Rivet is courting.

◆ Prediction

Expect benchmarks and migration guidance for 2.x users during the preview, followed by a 3.0 GA. The entry gives no performance numbers, so the SSD-speed claim is unverified.

Alternatives to Liquidsoap and Rivet

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 Rivet.

See all Liquidsoap alternatives → · See all Rivet alternatives →

Recent activity from Liquidsoap and Rivet

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 3d agoRivetIntroducing Rivet 3.0 Preview ⚡
  2. 17d agoRivetIntroducing agentOS 0.4 & Hosted VMs
  3. 22d agoRivetIntroducing Pi Durable for Rivet
  4. 24d agoRivetReplacing Our Message Broker with... S3? ⚡
  5. 28d agoRivetIntroducing Pi 1.0 for Rivet
  6. 1mo agoRivetIntroducing JWT Authentication for Rivet Actors
  7. 2mo agoLiquidsoapSubtitles become a content type and Liquidsoap ships its own Icecast server ⚡
  8. 2mo agoLiquidsoapLiquidsoap Rolling Release 2.4.x
  9. 4mo agoLiquidsoapQueue removal commands and O(1) clock propagation in Liquidsoap 2.4.5
  10. 6mo agoLiquidsoapLiquidsoap 2.4.4 supersedes 2.4.3 days after release
  11. 6mo agoLiquidsoapRaw string literals arrive in Liquidsoap 2.4.3
  12. 9mo agoLiquidsoapLiquidsoap 2.4.1 opens the stabilization phase

Frequently asked questions

What is the difference between Liquidsoap and Rivet?

They serve adjacent needs but don't currently overlap on shipped themes. Rivet is currently shipping more aggressively (velocity 7.5 vs 6.3), with 2 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.

Is Liquidsoap better than Rivet?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Rivet is currently shipping more aggressively (velocity 7.5 vs 6.3), with 2 editorial sparks in the last 30 days against 0. 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 Rivet?

Top Rivet alternatives in DevOps are ranked by recent ship velocity. Browse the "Rivet alternatives" section above for the current picks, or visit /alternatives/rivet for the full list with editorial commentary on each.