silx
silx settles into maintenance a release after its PySide6 migration
A side-by-side editorial comparison of NocoDB and TimescaleDB — release velocity, themes, recent moves, and the top alternatives to consider.
With Interfaces, NocoDB stops being a database view and starts being an app builder.
NocoDB's monthly releases alternate between view types and data-source reach. In three months it added Gantt, Shared Pages, Calendar Sync, image annotations and Oracle as a connectable source, alongside routine bug-fix and dependency releases. The August release breaks that pattern: Interfaces lets you build focused apps on top of a base instead of handing users the whole base.
TimescaleDB is paying down correctness debt in its columnstore query paths.
The 2.29 line is in patch mode after 2.29.0 landed chunk exclusion for DML in late July. 2.29.1 carried three security advisories alongside compression fixes, and 2.29.2 is bug fixes only - most of them wrong-results bugs in the columnar execution paths rather than crashes. Every release note in this window recommends upgrading at the next opportunity.
NocoDB's monthly releases alternate between view types and data-source reach. In three months it added Gantt, Shared Pages, Calendar Sync, image annotations and Oracle as a connectable source, alongside routine bug-fix and dependency releases. The August release breaks that pattern: Interfaces lets you build focused apps on top of a base instead of handing users the whole base.
The direction is away from 'spreadsheet with a nicer grid' and toward the internal-tools layer. Every recent addition points the same way — more data sources to sit on top of, more ways to present a table to someone who isn't the person who built it, and now a way to hide the base entirely behind a purpose-built page. The Enterprise-only Oracle add-on shows where the monetization pressure is coming from.
Interfaces will need the pieces app builders always need next — permissions and role targeting per page, write-back actions, and embedding — and the CE/paid split in each release table suggests some of that lands on the paid tier.
The 2.29 line is in patch mode after 2.29.0 landed chunk exclusion for DML in late July. 2.29.1 carried three security advisories alongside compression fixes, and 2.29.2 is bug fixes only - most of them wrong-results bugs in the columnar execution paths rather than crashes. Every release note in this window recommends upgrading at the next opportunity.
The feature work of 2.27 and 2.28 - vectorized filter evaluation, first/last derived straight from columnstore batch metadata, sparse indexes, SkipScan on compressed data - has been followed by a steady stream of fixes to those same code paths. 2.29.2 alone repairs SkipScan dropping uncompressed rows, sparse-index pushdown returning wrong results for IS NULL, and gapfill over window aggregates. That is the normal cost of pushing query optimizations into a compressed columnar store, and the project is working through it release by release rather than pausing.
With three consecutive patch releases on the 2.29 line and no new highlighted features since 2.29.0, the next minor is likely to resume the columnstore performance work - though the density of wrong-results fixes suggests more patches first.
Other Analytics 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 NocoDB or TimescaleDB.
silx settles into maintenance a release after its PySide6 migration
Plotly is turning its cloud into a metered compute platform with an enterprise on-ramp.
aniread stops asking you to know which tracker wrote the file
Rho's release machinery finally produced a stable build — and it shipped no new product.
Usermaven closed the loop: data comes in from anywhere, and now it goes back out.
OpenCTI spends a release unblocking queues and hardening upserts
See all NocoDB alternatives → · See all TimescaleDB alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. NocoDB 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. NocoDB 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 Analytics products to evaluate alongside.
Top NocoDB alternatives in Analytics are ranked by recent ship velocity. Browse the "NocoDB alternatives" section above for the current picks, or visit /alternatives/nocodb for the full list with editorial commentary on each.
Top TimescaleDB alternatives in Analytics are ranked by recent ship velocity. Browse the "TimescaleDB alternatives" section above for the current picks, or visit /alternatives/timescaledb for the full list with editorial commentary on each.