Firefly III
A nightly development tag fires daily; the actual changes stay off the feed.
A side-by-side editorial comparison of Hyperledger Besu and SolidInvoice — release velocity, themes, recent moves, and the top alternatives to consider.
Besu tags a release candidate a month, and half of them are titled after changelog chores.
Besu cuts a release candidate roughly monthly, and the feed titles each one after whatever commit sat at the head — which means 26.7.0-RC1 and 26.6.1-RC1 are presented to readers as changelog preparation rather than as releases. The candidates with substantive head commits show where the engineering attention is: bounding precompile result caches with a uniform memory ceiling, and fixing a snap-sync probe that treated an empty response as proof a range was fully covered.
SolidInvoice finally shipped the 3.0 it spent a year staging in alphas and betas.
After more than twelve months of alpha and beta releases, SolidInvoice 3.0 landed in June with the accumulated work of that cycle: email verification, Google OAuth, two-factor authentication, real user profiles, flat-rate tax support and a Meilisearch-backed search layer. Underneath it, the project moved onto a shared platform config and pulled trial and SaaS logic into an external bundle. The 2.3 line ran in parallel the whole time, absorbing security backports.
Besu cuts a release candidate roughly monthly, and the feed titles each one after whatever commit sat at the head — which means 26.7.0-RC1 and 26.6.1-RC1 are presented to readers as changelog preparation rather than as releases. The candidates with substantive head commits show where the engineering attention is: bounding precompile result caches with a uniform memory ceiling, and fixing a snap-sync probe that treated an empty response as proof a range was fully covered.
The visible work is client resource discipline and sync correctness — the unglamorous half of running an execution client, where a cache without a byte ceiling becomes an operator's memory incident and a sync helper that short-circuits leaves silently missing state. Both fixes are the kind found by reasoning about edge cases rather than by feature planning. The release process itself is the other story: an Unreleased section had to be folded back into 26.5.0 because RC2 was cut from the head of main, which is a process seam rather than a code change.
The monthly release-candidate rhythm should continue; based on these entries the substantive changes will keep landing in sync correctness and memory bounding rather than in new operator-facing features.
After more than twelve months of alpha and beta releases, SolidInvoice 3.0 landed in June with the accumulated work of that cycle: email verification, Google OAuth, two-factor authentication, real user profiles, flat-rate tax support and a Meilisearch-backed search layer. Underneath it, the project moved onto a shared platform config and pulled trial and SaaS logic into an external bundle. The 2.3 line ran in parallel the whole time, absorbing security backports.
Two threads run through this changelog. The visible one is identity and account management catching up to what users expect from a billing app — signup verification, OAuth, 2FA, self-serve company deletion. The less visible one is the codebase being restructured around reusable solidworx platform components with Sentry and Prometheus instrumentation, which is the shape of a project preparing to run itself as a hosted service rather than only as a download.
With 3.0 out and 3.0.1 already repairing the upgrade migration path, the near-term work is likely more 3.0.x stabilization for people coming off 2.3 rather than new features.
Other Finance 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 Hyperledger Besu or SolidInvoice.
A nightly development tag fires daily; the actual changes stay off the feed.
Invoice Ninja's patch train grinds on: QuickBooks sync, Peppol validation, gateway fixes.
Cloud cost observability is becoming AI spend control, with model routing as the first real lever.
A CPA firm publishing pricing pages, not releases — this feed is a sales funnel.
Pigment's Agents break out of single applications and start reading your spreadsheets.
Carta is pulling fund back-office paperwork in-app, then walking into the deal team's CRM.
See all Hyperledger Besu alternatives → · See all SolidInvoice alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Hyperledger Besu is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 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. Hyperledger Besu is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Finance products to evaluate alongside.
Top Hyperledger Besu alternatives in Finance are ranked by recent ship velocity. Browse the "Hyperledger Besu alternatives" section above for the current picks, or visit /alternatives/hyperledger-besu for the full list with editorial commentary on each.
Top SolidInvoice alternatives in Finance are ranked by recent ship velocity. Browse the "SolidInvoice alternatives" section above for the current picks, or visit /alternatives/solidinvoice for the full list with editorial commentary on each.