dbt Core
dbt Fusion's second beta is adapter work: ClickHouse gets materializations, indexes, and catalogs
A side-by-side editorial comparison of ThingsBoard and tulpa — release velocity, themes, recent moves, and the top alternatives to consider.
An IoT platform whose release notes have become a CVE ledger
ThingsBoard ships every release twice — once on the 4.3 line and once as a 4.2 backport with an identical security section — and those security sections now dominate the notes, running to twenty or thirty CVEs per release. The recurring classes are telling: SSRF through AI model provider URLs, SSRF and file access escapes from the TBEL script sandbox, DNS rebinding bypasses, and access control on alarm comments. Feature work continues underneath, mostly IoT Hub integration and an Angular 20 UI migration.
The 0.0.x train stops at CRAN: tulpa's engine ships to the ecosystem it already anchors.
tulpa is the C++/R Bayesian spatial inference engine sitting under gcol33's family of ecological occupancy packages, tagging 0.0.x releases several times a week. 0.1.0 is its first CRAN release, and the notes state outright that the engine surface is unchanged from 0.0.198 — the work is packaging discipline: local T bindings rebound to n_t/n_times, OpenMP teams capped under R CMD check, the pkgdown deploy narrowed, an aspell dictionary added. The window behind it splits between the S3 generics conversion and numerical-correctness work in the nested-Laplace grid.
ThingsBoard ships every release twice — once on the 4.3 line and once as a 4.2 backport with an identical security section — and those security sections now dominate the notes, running to twenty or thirty CVEs per release. The recurring classes are telling: SSRF through AI model provider URLs, SSRF and file access escapes from the TBEL script sandbox, DNS rebinding bypasses, and access control on alarm comments. Feature work continues underneath, mostly IoT Hub integration and an Angular 20 UI migration.
The platform is paying down the security cost of being extensible. TBEL scripting and user-configurable AI model endpoints are exactly the features that make ThingsBoard useful for industrial rule engines, and both are repeatedly the source of sandbox and SSRF findings — so the work has shifted to fencing them with allow-lists, opt-in SSRF protection and configurable security headers. Meanwhile the AI surface keeps growing, with structured output support spreading across more model providers.
The dual-branch pattern will hold, with 4.2 continuing to receive the same security sets as 4.3 until it reaches end of life; expect further hardening of the TBEL sandbox rather than new scripting capability.
tulpa is the C++/R Bayesian spatial inference engine sitting under gcol33's family of ecological occupancy packages, tagging 0.0.x releases several times a week. 0.1.0 is its first CRAN release, and the notes state outright that the engine surface is unchanged from 0.0.198 — the work is packaging discipline: local T bindings rebound to n_t/n_times, OpenMP teams capped under R CMD check, the pkgdown deploy narrowed, an aspell dictionary added. The window behind it splits between the S3 generics conversion and numerical-correctness work in the nested-Laplace grid.
Two moves in nine days point at the same destination: the generics conversion made tulpa extensible by downstream packages, and CRAN admission makes it installable by them. The current cadence — several tags a week, some existing only to record a measurement that produced no code change — does not survive CRAN's submission overhead, so the release rhythm has to slow whether or not the project intends it. The correctness work still clusters on the joint nested-Laplace driver, and 0.1.0 extends the same diagnostics habit with .NL_AXIS_SD_REASONS, a closed vocabulary for an outer axis whose grid does not contain its own posterior mode.
Expect tulpaObs to follow tulpa onto CRAN, since it is the consumer whose registrations the engine has spent this window unblocking, and expect the version line to move in larger, less frequent steps now that each one carries a submission.
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 ThingsBoard or tulpa.
dbt Fusion's second beta is adapter work: ClickHouse gets materializations, indexes, and catalogs
Fulcrum is betting its whole map stack on Esri, with a hard Google Maps cutoff on September 1.
Holistics keeps fencing in the AI layer it spent the summer building.
Dovetail spent July opening doors to other tools and August making its own rooms easier to enter.
AgencyAI got skills three weeks ago; everything since has been making them routine.
Interfaces gets the permissions layer it needed, one release after launching.
See all ThingsBoard alternatives → · See all tulpa alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. tulpa is currently shipping more aggressively (velocity 7.5 vs 0.0), 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. tulpa is currently shipping more aggressively (velocity 7.5 vs 0.0), with 2 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 ThingsBoard alternatives in Analytics are ranked by recent ship velocity. Browse the "ThingsBoard alternatives" section above for the current picks, or visit /alternatives/thingsboard for the full list with editorial commentary on each.
Top tulpa alternatives in Analytics are ranked by recent ship velocity. Browse the "tulpa alternatives" section above for the current picks, or visit /alternatives/tulpa for the full list with editorial commentary on each.