Firefly III
Firefly III publishes a nightly develop build whose notes never say what changed
A side-by-side editorial comparison of GOAT.tax and Zluri — release velocity, themes, recent moves, and the top alternatives to consider.
| Feature | GOAT.tax | Zluri |
|---|---|---|
| Sector | Finance | Finance |
| Velocity score | 5.0 | 8.8 |
| Sparks · 30d | 0 | 2 |
| Top themes | tax-compliance, rd-credits, state-coverage, auditability | access-governance, identity, certifications, account-granularity |
| Last editorial update | 21h ago | 2d ago |
| Website | Visit → | — |
State credit math keeps deepening while the study tables get easier to work in.
GOAT.tax runs R&D tax credit studies end to end, from wage and expense collection through business component allocation to a filed deliverable. This release tightens three state rules at once — Colorado now requires three years in the same Enterprise Zone, Indiana Research Activities fields get defaults so deliverables are never generated incomplete, and Minnesota picks up startup treatment that derives the applicable historical years and Fixed Base Percentage method dynamically. On the workspace side, R&D allocation percentages become directly editable in BC Allocation for single- and multi-state records, and the All Studies page and BC Allocation table are rebuilt on the newer design.
Zluri is rebuilding access governance around the account rather than the application.
Zluri has spent August moving its data model below the application boundary. Accounts and instances became first-class entities with their own owners, roles and lifecycle actions; source prioritisation replaced the single-primary-source rule for deciding whether a user is active; and activity-based discovery gained a default status and an inactivity threshold. Access certifications now review individual accounts rather than a user's application access as a whole. Most of it ships as beta, on demand, or behind an enable flag.
GOAT.tax runs R&D tax credit studies end to end, from wage and expense collection through business component allocation to a filed deliverable. This release tightens three state rules at once — Colorado now requires three years in the same Enterprise Zone, Indiana Research Activities fields get defaults so deliverables are never generated incomplete, and Minnesota picks up startup treatment that derives the applicable historical years and Fixed Base Percentage method dynamically. On the workspace side, R&D allocation percentages become directly editable in BC Allocation for single- and multi-state records, and the All Studies page and BC Allocation table are rebuilt on the newer design.
The state coverage thread has shifted from adding jurisdictions to encoding their harder eligibility and computation rules — Enterprise Zone tenure, startup Fixed Base Percentage methodology, and visible reasons when a state credit is ruled ineligible. That last one, plus the new Fixed Base Percentage details view and override, points at the same goal from a different angle: making the calculation auditable by the person running the study rather than trusting it. Fee handling entered the product this window too, with an optional not-to-exceed percentage and cap threaded through the fee structure, credit and deliverable pages.
Fee logic just appeared across three pages at once, so the next step is likely the rest of the billing path — applying the not-to-exceed cap to invoicing or partner-facing fee reporting. The notes give no schedule.
Zluri has spent August moving its data model below the application boundary. Accounts and instances became first-class entities with their own owners, roles and lifecycle actions; source prioritisation replaced the single-primary-source rule for deciding whether a user is active; and activity-based discovery gained a default status and an inactivity threshold. Access certifications now review individual accounts rather than a user's application access as a whole. Most of it ships as beta, on demand, or behind an enable flag.
The releases read as one program: make the account knowable, make its status trustworthy, then make it reviewable. Identity resolution moved off email matching onto source-native identifiers, status resolution moved from one trusted source to a ranked fallback chain, and certification moved from user-level to account-level decisions. Zluri is also layering its own judgment on top, with recommendation signals on access requests and categorised risk chips on account reviews, which is a different competitive claim than routing requests faster. The instances release names non-human identity as the destination, and this data model is the prerequisite for it.
Expect the account-level primitives to graduate out of beta and the advisory scoring to acquire teeth, with recommendation thresholds that auto-approve or auto-revoke rather than merely advise. Non-human and service account coverage is the step the entries name themselves.
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 GOAT.tax or Zluri.
Firefly III publishes a nightly develop build whose notes never say what changed
CloudZero is turning cloud waste into named recommendations, and AI spend into a line item
Invoice Ninja's feed is a freelancer advice blog with no trace of the software
Bigcapital ships every two days, and the SDK is quietly becoming the second product
Copperleaf's feed is a thought-leadership blog making one argument in a dozen variations
This entry is a certification course page scraped as a product, with no release signal at all
See all GOAT.tax alternatives → · See all Zluri alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Zluri is currently shipping more aggressively (velocity 8.8 vs 5.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. Zluri is currently shipping more aggressively (velocity 8.8 vs 5.0), with 2 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 GOAT.tax alternatives in Finance are ranked by recent ship velocity. Browse the "GOAT.tax alternatives" section above for the current picks, or visit /alternatives/goat-tax for the full list with editorial commentary on each.
Top Zluri alternatives in Finance are ranked by recent ship velocity. Browse the "Zluri alternatives" section above for the current picks, or visit /alternatives/zluri for the full list with editorial commentary on each.