Fulcrum
Fulcrum is consolidating on Esri, with Google Maps gone September 1
A side-by-side editorial comparison of dbt Core and Kameleoon — release velocity, themes, recent moves, and the top alternatives to consider.
| Feature | dbt Core | Kameleoon |
|---|---|---|
| Sector | Analytics | Analytics |
| Velocity score | 7.5 | 1.3 |
| Sparks · 30d | 2 | 0 |
| Top themes | dbt-fusion, rust-rewrite, static-analysis, semantic-layer | personalization, ab testing, prompt-driven editing, widgets |
| Last editorial update | 1d ago | 3mo ago |
| Website | Visit → | — |
The Rust rewrite crosses from alpha to beta, and it can now bind SQL without touching the warehouse.
dbt is running two release lines at once. The 1.x Python line reached 1.12.0 in July, a GA that removed the experimental dbt login command and the bundled dbt-state plugin outright while adding the v2 semantic layer YAML parsing. The 2.0 Fusion line — the Rust engine — moved through five alphas and reached its first beta on August 10, carrying catalog-free binding, dbt state explain, redundant-test skipping, and a lint rule system that understands node selection.
Kameleoon refines its prompt-driven personalization editor with widget, targeting, and PBX upgrades.
Kameleoon is iterating on the new Personalization editor and the prompt-based workflow that sits inside it. Recent changes: a simpler two-step widget event creation flow that ties directly to Kameleoon goals, the ability to reorder personalization targeting rules from the new editor, and PBX prompt-area improvements (resizable prompt area, image paste as input). Survey widgets get a configurable response-recording trigger.
dbt is running two release lines at once. The 1.x Python line reached 1.12.0 in July, a GA that removed the experimental dbt login command and the bundled dbt-state plugin outright while adding the v2 semantic layer YAML parsing. The 2.0 Fusion line — the Rust engine — moved through five alphas and reached its first beta on August 10, carrying catalog-free binding, dbt state explain, redundant-test skipping, and a lint rule system that understands node selection.
Fusion is being built to do statically what dbt-core did by asking the warehouse. Catalog-free binding lets SQL bind without introspection, tests get skipped when they are provably redundant, and dbt State speculatively submits nodes while the dependency prefetch is still in flight — all of it trading round-trips for compile-time analysis. Meanwhile 1.x is absorbing the v2 semantic layer YAML piece by piece, which puts metrics and entities into the model graph itself. Adapter breadth keeps widening in parallel, with Databricks service principal auth, Redshift group grants, and ClickHouse materialization configs.
With beta.1 out, the next milestones are further betas hardening the Fusion feature set toward parity, and continued v2 semantic YAML work landing in the 1.x line.
Kameleoon is iterating on the new Personalization editor and the prompt-based workflow that sits inside it. Recent changes: a simpler two-step widget event creation flow that ties directly to Kameleoon goals, the ability to reorder personalization targeting rules from the new editor, and PBX prompt-area improvements (resizable prompt area, image paste as input). Survey widgets get a configurable response-recording trigger.
The product is settling into the new editor as the default surface and accumulating the small ergonomics wins teams expect from a mature personalization tool — fewer clicks, fewer manual IDs, more control over evaluation order. The PBX prompt updates suggest AI-assisted variant creation is becoming a more prominent workflow, with multimodal input now supported.
Expect the editor's PBX surface to keep gaining capability — likely brand-context awareness, reusable prompts, and broader image-driven generation. Targeting and goal flows will continue to consolidate so users don't need to reach for IDs or admin pages.
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 dbt Core or Kameleoon.
Fulcrum is consolidating on Esri, with Google Maps gone September 1
Omni ships weekly, and almost every week the headline item is an AI feature
Four ODD Platform releases in two weeks, and not one of them changes the product
Baremaps got geoparquet and hillshading, then went quiet for eighteen months in incubation
Deequ ships GitHub tags whose release notes are one commit message long
Marquez spent 2024 turning a lineage store into a UI, then stopped releasing
See all dbt Core alternatives → · See all Kameleoon alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. dbt Core is currently shipping more aggressively (velocity 7.5 vs 1.3), 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. dbt Core is currently shipping more aggressively (velocity 7.5 vs 1.3), 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 dbt Core alternatives in Analytics are ranked by recent ship velocity. Browse the "dbt Core alternatives" section above for the current picks, or visit /alternatives/dbt-core for the full list with editorial commentary on each.
Top Kameleoon alternatives in Analytics are ranked by recent ship velocity. Browse the "Kameleoon alternatives" section above for the current picks, or visit /alternatives/kameleoon for the full list with editorial commentary on each.