dbt Core
dbt Fusion's second beta is adapter work: ClickHouse gets materializations, indexes, and catalogs
A side-by-side editorial comparison of cfbfastr and NocoDB — release velocity, themes, recent moves, and the top alternatives to consider.
College football's open data client hit v2 — and now reports how many API calls you have left.
cfbfastR retrieves college football data — play-by-play, box scores, betting lines, ratings and recruiting — from the CollegeFootballData API, ESPN endpoints and the sportsdataverse data repository. Version 2.0.0 in September 2025 was the first release in over three years and rebuilt the package against CFBD's v2 API. Every load_cfb_*() function changed its underlying source to comply with CFBD's terms, the play-by-play dataset gained team and game identifiers users previously had to join in themselves, and a batch of new endpoints arrived covering opponent-adjusted metrics, FPI ratings and live scoreboard and play data.
Interfaces gets the permissions layer it needed, one release after launching.
NocoDB ships monthly, and the last two releases are a launch and its follow-through. 2026.08.0 introduced Interfaces, custom app surfaces built over a base; 2026.08.1 gives that layer what it was missing — per-dashboard visibility and editing permissions, field edit permissions enforced on interface pages, team-granted access, and page reordering. Alongside it the grid gains realtime presence with per-collaborator colours and jump-to-cursor, folders for grouping tables and views, up to three frozen fields, and nested records in List View.
cfbfastR retrieves college football data — play-by-play, box scores, betting lines, ratings and recruiting — from the CollegeFootballData API, ESPN endpoints and the sportsdataverse data repository. Version 2.0.0 in September 2025 was the first release in over three years and rebuilt the package against CFBD's v2 API. Every load_cfb_*() function changed its underlying source to comply with CFBD's terms, the play-by-play dataset gained team and game identifiers users previously had to join in themselves, and a batch of new endpoints arrived covering opponent-adjusted metrics, FPI ratings and live scoreboard and play data.
The package's direction is now set by the data provider rather than by its own plans, and that provider has moved to metered access — the free tier is capped at 1,000 calls a month, with limits tied to membership level. cfbd_api_key_info() reporting a user's tier and usage is the clearest sign of that shift: quota is now something an analysis has to manage. The long gap before 2.0.0 and its arrival largely through a first-time contributor also indicate a package sustained by community effort rather than steady maintenance.
The live scoreboard and play endpoints are the natural place for the next work, since they are the ones that benefit from in-season iteration. Given the release notes warn users to check their pipelines, follow-up fixes for the changed loading functions are likely before anything new lands.
NocoDB ships monthly, and the last two releases are a launch and its follow-through. 2026.08.0 introduced Interfaces, custom app surfaces built over a base; 2026.08.1 gives that layer what it was missing — per-dashboard visibility and editing permissions, field edit permissions enforced on interface pages, team-granted access, and page reordering. Alongside it the grid gains realtime presence with per-collaborator colours and jump-to-cursor, folders for grouping tables and views, up to three frozen fields, and nested records in List View.
The pattern is consistent: NocoDB launches a surface, then spends the next release making it governable and usable at team scale. Presence and folders are collaboration parity rather than new direction — the directional bet was Interfaces, and this release is that bet being made safe for the eighty people who only need to approve something. The permission system is now the same one across tables, fields, dashboards, and interface pages, which is the consolidation that makes the app layer sellable.
Write-back actions and embedding are the remaining pieces app builders expect from Interfaces, and the availability tables in each release suggest they land on the paid tier.
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 cfbfastr or NocoDB.
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.
The 0.0.x train stops at CRAN: tulpa's engine ships to the ecosystem it already anchors.
AgencyAI got skills three weeks ago; everything since has been making them routine.
See all cfbfastr alternatives → · See all NocoDB 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 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. NocoDB is currently shipping more aggressively (velocity 6.3 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 Analytics products to evaluate alongside.
Top cfbfastr alternatives in Analytics are ranked by recent ship velocity. Browse the "cfbfastr alternatives" section above for the current picks, or visit /alternatives/cfbfastr for the full list with editorial commentary on each.
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.