Liquidsoap
Liquidsoap opens its 2.5 line with subtitles as a first-class content type and a streaming server of its own
A side-by-side editorial comparison of Pelican and Speakeasy — release velocity, themes, recent moves, and the top alternatives to consider.
| Feature | Pelican | Speakeasy |
|---|---|---|
| Sector | DevOps | DevOps |
| Velocity score | 0.0 | 10.0 |
| Sparks · 30d | 0 | 1 |
| Top themes | static-site-generator, python, theming, maintenance-mode | ai-governance, shadow-mcp, policy-enforcement, agent-observability |
| Last editorial update | 7d ago | 1d ago |
| Website | Visit → | — |
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.
Speakeasy stopped inventorying MCP servers and started adjudicating them.
Speakeasy ships near-daily platform releases with unusually legible notes — each headline states what changed for a user, not a version number. The current one turns the Shadow MCP page into a single review surface where every server carries an approval state and an automatically gathered evidence dossier: publisher, requested scopes, declared capabilities, maintenance signals, and whether internal teams already talk to it. Decisions enforce on record. Around it, the assistant surfaces have been consolidating: one detail panel for configuration and observation, exact session totals, and canonical identities folding a person's work and personal AI accounts together.
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.
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.
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.
Speakeasy ships near-daily platform releases with unusually legible notes — each headline states what changed for a user, not a version number. The current one turns the Shadow MCP page into a single review surface where every server carries an approval state and an automatically gathered evidence dossier: publisher, requested scopes, declared capabilities, maintenance signals, and whether internal teams already talk to it. Decisions enforce on record. Around it, the assistant surfaces have been consolidating: one detail panel for configuration and observation, exact session totals, and canonical identities folding a person's work and personal AI accounts together.
The arc runs observe, then intercept, now adjudicate. Earlier releases catalogued spend and inventoried shadow MCP servers; the LiteLLM integration moved enforcement to the proxy so a violating prompt dies before inference; this release supplies the judgment layer, doing the research an approver would otherwise do by hand. The supporting work points the same way — prompt-injection scanning of captured skill manifests, risk policies that pause instead of being deleted, identity resolution that reports a whole person rather than an account. Each is a piece a control plane needs before its verdicts can be trusted.
Expect approval state to start gating traffic rather than only recording a decision, and the evidence dossier to extend from MCP servers to the skills and assistants already being captured. The rollout flag on the approval workflow suggests general availability is the next step rather than new capability.
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 Pelican or Speakeasy.
Liquidsoap opens its 2.5 line with subtitles as a first-class content type and a streaming server of its own
Appwrite keeps reworking its own plumbing — Go CLI, SquashFS mounts, and an MCP layer that refreshes itself
FusionAuth's feed publishes version numbers; whether they carry news is a coin flip.
Sanity ships across every package at once, and the agent-facing surface moves fastest.
The 6.1 candidate arrives carrying the same notes the beta already shipped in June.
Auth0 hands tenants a throttle on their own noisy apps
See all Pelican alternatives → · See all Speakeasy alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Speakeasy is currently shipping more aggressively (velocity 10.0 vs 0.0), with 1 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Speakeasy is currently shipping more aggressively (velocity 10.0 vs 0.0), with 1 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.
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.
Top Speakeasy alternatives in DevOps are ranked by recent ship velocity. Browse the "Speakeasy alternatives" section above for the current picks, or visit /alternatives/speakeasy for the full list with editorial commentary on each.