Whatagraph
Whatagraph keeps fixing what breaks when one account runs a thousand sources.
Comparison · Analytics
NocoDB vs writexl
A side-by-side editorial comparison of NocoDB and writexl — release velocity, themes, recent moves, and the top alternatives to consider.
NocoDB vs writexl: at a glance
What is NocoDB?
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.
What is writexl?
writexl spent nine years refusing to do formatting, then shipped all of it in 2.0.0.
For most of its history writexl was a deliberately minimal wrapper: bump the vendored libxlsxwriter, handle NA and Date coercion correctly, support a list of data frames for multiple sheets, and nothing else. 2.0.0, released August 2026, changes that — near-full libxlsxwriter coverage, cell/worksheet/workbook formatting, cell comments, an `xl_cell_general` class carrying value, formula and hyperlink, a cell-by-cell refactor, libxlsxwriter 1.2.4, and memory-safety work. It landed the same day as 1.5.4, a typo fix on the old line.
NocoDB vs writexl: editorial side-by-side
NocoDB
6.3ANALYTICS
Interfaces gets the permissions layer it needed, one release after launching.
◆ Current state
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.
◆ Where it's heading
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.
◆ Prediction
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.
writexl
6.3ANALYTICS
writexl spent nine years refusing to do formatting, then shipped all of it in 2.0.0.
◆ Current state
For most of its history writexl was a deliberately minimal wrapper: bump the vendored libxlsxwriter, handle NA and Date coercion correctly, support a list of data frames for multiple sheets, and nothing else. 2.0.0, released August 2026, changes that — near-full libxlsxwriter coverage, cell/worksheet/workbook formatting, cell comments, an `xl_cell_general` class carrying value, formula and hyperlink, a cell-by-cell refactor, libxlsxwriter 1.2.4, and memory-safety work. It landed the same day as 1.5.4, a typo fix on the old line.
◆ Where it's heading
The package has changed category. Its selling point was being the dependency-free, opinion-free way to get a data frame into xlsx; 2.0.0 makes it a formatting-capable writer that now compares itself against openxlsx2 in its own test suite. The cell-by-cell refactor is what made that possible and is also the largest structural change in the package's history. Note that a single contributor drove essentially all of it.
◆ Prediction
Expect follow-up releases fixing edge cases in the new formatting and comment APIs — the cell-by-cell rewrite is too large to land clean, and the 2.0.0 notes already mention an off-by-one in date columns.
Alternatives to NocoDB and writexl
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 writexl.
Lightdash
Lightdash keeps handing authoring to outside agents and keeping the governed layer for itself.
Delta Lake
A 4.4.0 tag appears, but the feed carries only its release plumbing
distributions3
distributions3 0.3.0 adds sample-based distributions and likelihood derivatives
Basedash
Basedash keeps pushing its data out of the workspace — now to people without accounts
RStudio
RStudio ships through release branches, and the notes are commit messages
See all NocoDB alternatives → · See all writexl alternatives →
Recent activity from NocoDB and writexl
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1d agoNocoDB2026.08.1 : Introducing Realtime Presence and Folders
- 14d agowritexlwritexl 2.0.0 adds formatting, comments and full libxlsxwriter coverage ⚡
- 14d agowritexlwritexl 1.5.4 fixes a documentation typo
- 15d agoNocoDB2026.08.0 : Introducing Interfaces ⚡
- 1mo agoNocoDB2026.07.0 : Introducing Calendar Sync & Image Annotations
- 1mo agoNocoDB2026.06.2 : Introducing Oracle Database Support
- 2mo agoNocoDB2026.06.1: tsgo typechecking and rspack bump
- 2mo agoNocoDB2026.06.0: Bounded group-by fetch retries
- 5y agowritexlwritexl 1.4.0 updates libxlsxwriter to 1.0.3
- 6y agowritexlwritexl 1.2 fixes NA in formulas and hyperlinks
- 7y agowritexlwritexl 1.1 fixes NA strings and bit64 coercion
- 8y agowritexlwritexl 1.0 writes Date values as datetimes
Frequently asked questions
What is the difference between NocoDB and writexl?
They serve adjacent needs but don't currently overlap on shipped themes. NocoDB and writexl are shipping at a similar cadence (velocity 6.3 vs 6.3, both within Sparkpulse's "active" band). See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Is NocoDB better than writexl?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. NocoDB and writexl are shipping at a similar cadence (velocity 6.3 vs 6.3, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Analytics products to evaluate alongside.
What are the best alternatives to NocoDB?
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.
What are the best alternatives to writexl?
Top writexl alternatives in Analytics are ranked by recent ship velocity. Browse the "writexl alternatives" section above for the current picks, or visit /alternatives/writexl for the full list with editorial commentary on each.