← Back to home
Comparison · DevOps

Liquidsoap vs Pelican

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

Liquidsoap vs Pelican: at a glance

FeatureLiquidsoapPelican
SectorDevOpsDevOps
Velocity score2.50.0
Sparks · 30d00
Top themesaudio-streaming, clock-scheduling, stability, resource-leaksstatic-site-generator, python, theming, maintenance-mode
Last editorial update4h ago2h ago
WebsiteVisit →Visit →

What is Liquidsoap?

Liquidsoap spent the whole 2.4 line paying down the cost of its own rewrite

Liquidsoap is a scripting language and runtime for building audio and video streams. The 2.4 series has been almost entirely stabilization: five patch releases since November 2025, two of them shipped within days of each other because the preceding one broke source cleanup, and 2.4.4 arriving with an explicit recommendation to skip 2.4.3. The recurring subject matter is clocks, source lifecycle and resource leaks — sub-clock leaks, crossfade crashes when skip is called off-thread, encoder sharing, Strings.Mutable leaks.

Read the full Liquidsoap trajectory →

What is Pelican?

Pelican now ships roughly once a year, and 4.12 is theme housekeeping

Pelican is a mature Python static site generator in low-cadence maintenance: 4.12.0 in April 2026 followed 4.11.0 by fifteen months, which itself followed 4.10.0 by sixteen. Nearly all recent work lands in the bundled notmyidea and Simple themes, in summary generation, and in the file-watching and logging plumbing. The contributor pattern is telling — a handful of names carry most merged PRs, and the changelogs read as accumulated small fixes rather than planned feature arcs.

Read the full Pelican trajectory →

Liquidsoap vs Pelican: editorial side-by-side

L2.5

Liquidsoap spent the whole 2.4 line paying down the cost of its own rewrite

◆ Current state

Liquidsoap is a scripting language and runtime for building audio and video streams. The 2.4 series has been almost entirely stabilization: five patch releases since November 2025, two of them shipped within days of each other because the preceding one broke source cleanup, and 2.4.4 arriving with an explicit recommendation to skip 2.4.3. The recurring subject matter is clocks, source lifecycle and resource leaks — sub-clock leaks, crossfade crashes when skip is called off-thread, encoder sharing, Strings.Mutable leaks.

◆ Where it's heading

The project said outright at 2.4.1 that the internal rewrite and feature work were done and that effort would shift to stability, and the release record since then matches that claim. What new surface has appeared is diagnostic or defensive rather than expansive: clock and source graph pretty-printing, telnet commands for queue and output control, and raw string literals that stop interpolation from executing untrusted input. Performance work has targeted the same subsystem as the bugs, with clock sync-source propagation moving from a full scan to push-based updates.

◆ Prediction

The 2.4.3 notes state that 2.4.x was meant to end there and that 2.5.x work has begun, yet two more patches have shipped since — so the branch is likely to keep absorbing clock and source fixes until 2.5 lands. The notes give no date for it.

P
Pelican
DEVOPS
0.0

Pelican now ships roughly once a year, and 4.12 is theme housekeeping

◆ Current state

Pelican is a mature Python static site generator in low-cadence maintenance: 4.12.0 in April 2026 followed 4.11.0 by fifteen months, which itself followed 4.10.0 by sixteen. Nearly all recent work lands in the bundled notmyidea and Simple themes, in summary generation, and in the file-watching and logging plumbing. The contributor pattern is telling — a handful of names carry most merged PRs, and the changelogs read as accumulated small fixes rather than planned feature arcs.

◆ Where it's heading

The project is stable rather than growing: the last genuinely structural changes were switching the build tool to PDM and moving file watching to watchfiles back in 4.9.0, and nothing since has altered how Pelican works. Recent releases invest in making the bundled themes usable as inheritance bases — more template blocks, CSS_FILE support, dark mode — which pushes customization toward theme authors instead of core. Expect continuity, not reinvention.

◆ Prediction

The entries show no roadmap signal beyond incremental theme and Python-version support, so the next release most likely follows the same pattern: another year-scale gap, more Simple-theme inheritance hooks, and test-matrix updates for a newer Python.

Alternatives to Liquidsoap and Pelican

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

See all Liquidsoap alternatives → · See all Pelican alternatives →

Recent activity from Liquidsoap and Pelican

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

  1. 1d agoLiquidsoapLiquidsoap Rolling Release 2.4.x
  2. 1mo agoLiquidsoapQueue removal commands and O(1) clock propagation in Liquidsoap 2.4.5
  3. 3mo agoPelicanPelican 4.12 adds dark mode to the default theme
  4. 3mo agoLiquidsoapLiquidsoap 2.4.4 supersedes 2.4.3 days after release
  5. 4mo agoLiquidsoapRaw string literals arrive in Liquidsoap 2.4.3
  6. 6mo agoLiquidsoapLiquidsoap 2.4.1 opens the stabilization phase
  7. 6mo agoLiquidsoapClock and source graph inspection tools in Liquidsoap 2.4.2
  8. 1y agoPelicanPelican 4.11 makes Typogrify filters selectable
  9. 1y agoPelicanPelican 4.10.2 ignores hidden files by default
  10. 1y agoPelicanPelican 4.10.1 fixes live reload and theme symlinks
  11. 1y agoPelicanPelican 4.10 adds paragraph-count summaries and a Medium importer
  12. 2y agoPelicanPelican 4.9.1 fixes the tzdata dependency on Windows

Frequently asked questions

What is the difference between Liquidsoap and Pelican?

They serve adjacent needs but don't currently overlap on shipped themes. Liquidsoap is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 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 Pelican?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Liquidsoap is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 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 Pelican?

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