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 QuestDB and Stirling-PDF — release velocity, themes, recent moves, and the top alternatives to consider.
QuestDB 10.0 collapses ingest and egress into one binary protocol, then aims at agent-run notebooks.
QuestDB's feed mixes release notes, engineering deep dives and customer stories, and the through-line for the past month has been QWP — its own binary columnar wire protocol. It shipped in 10.0, was benchmarked against InfluxDB Line Protocol on ingestion and against ClickHouse and TimescaleDB on Arrow reads, and now has a standalone explainer covering bidirectional dataframe transfer and built-in failover. Between the protocol posts sit JIT compiler internals and production references from banks and exchanges.
Stirling PDF is clearing the decks — six weeks of hotfixes ahead of a promised big release.
Every release in this window is corrective. 2.14.3 fixes tool operations failing on Debian 12 and Fedora 44, concurrency problems on merge, an automation bug in image removal, and crashes on 2GB PDFs, plus Linux startup and a Windows ARM64 test build. Before it, 2.14.2 patched Postgres user-data loading, 2.14.1 stopped PostHog loading before opt flags were read and fixed certificate signing, and 2.13.2 covered security fixes and desktop performance. The one feature release is 2.14.0, which added hardware token signing via PKCS#11 smart cards and OS certificate stores on desktop.
QuestDB's feed mixes release notes, engineering deep dives and customer stories, and the through-line for the past month has been QWP — its own binary columnar wire protocol. It shipped in 10.0, was benchmarked against InfluxDB Line Protocol on ingestion and against ClickHouse and TimescaleDB on Arrow reads, and now has a standalone explainer covering bidirectional dataframe transfer and built-in failover. Between the protocol posts sit JIT compiler internals and production references from banks and exchanges.
The protocol work is the thread that matters. QuestDB has been positioning against InfluxDB Line Protocol on ingestion throughput for a while, and 10.0 turned that from a benchmark argument into the default path both in and out of the database. The follow-up posts are consolidation rather than new capability: the same protocol re-explained for a different reader each time, which is what a project does when it needs an ecosystem to adopt a format. Live views and agent-driven notebooks remain the less-proven half of the release.
Expect client libraries and third-party connectors to be the next visible work, since a proprietary wire protocol is only worth its switching cost once the dataframe tools speak it. Whether live views leave beta is not something these entries settle.
Every release in this window is corrective. 2.14.3 fixes tool operations failing on Debian 12 and Fedora 44, concurrency problems on merge, an automation bug in image removal, and crashes on 2GB PDFs, plus Linux startup and a Windows ARM64 test build. Before it, 2.14.2 patched Postgres user-data loading, 2.14.1 stopped PostHog loading before opt flags were read and fixed certificate signing, and 2.13.2 covered security fixes and desktop performance. The one feature release is 2.14.0, which added hardware token signing via PKCS#11 smart cards and OS certificate stores on desktop.
The project is consolidating a desktop application on top of what was a server tool, and the defect pattern shows where that hurts: platform-specific startup failures, OS certificate integration, ARM64 builds, large-file memory behaviour. Hardware token signing is the strategically interesting piece, since it moves the product toward legally meaningful signatures that a browser-only tool cannot offer. The 2.14.3 notes state a large feature release is two to three weeks out.
The changelog explicitly promises a substantial feature release in two to three weeks, and the stabilisation pattern supports that. Hardware token signing spreading beyond desktop-only is the natural extension of the 2.14.0 work.
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 QuestDB or Stirling-PDF.
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 QuestDB alternatives → · See all Stirling-PDF alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. QuestDB is currently shipping more aggressively (velocity 6.3 vs 5.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. QuestDB is currently shipping more aggressively (velocity 6.3 vs 5.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 QuestDB alternatives in DevOps are ranked by recent ship velocity. Browse the "QuestDB alternatives" section above for the current picks, or visit /alternatives/questdb for the full list with editorial commentary on each.
Top Stirling-PDF alternatives in DevOps are ranked by recent ship velocity. Browse the "Stirling-PDF alternatives" section above for the current picks, or visit /alternatives/stirling-pdf for the full list with editorial commentary on each.