Firefly III vs Candis
Side-by-side trajectory, velocity, and editorial themes.
Firefly III ships nightly, but its feed only surfaces boilerplate dev builds
Firefly III is a mature, self-hosted personal finance manager for budgeting and transaction tracking. The entries we can see are all automated `develop`-tag nightly pre-release builds carrying identical boilerplate rather than a substantive changelog, so actual feature movement isn't visible from this feed. What the cadence does confirm is an actively maintained project pushing builds most days.
The signal here is development tempo, not direction: multiple `develop` builds land per day with no per-release notes attached. Until a tagged stable release with real changelog content appears, there's no feature-level arc to read from these entries. The project is clearly alive and shipping; what it's shipping is opaque from the pre-release tag alone.
Expect the nightly `develop` cadence to continue and a tagged stable release to follow eventually, but these boilerplate builds don't support a confident prediction about specific features. What's unclear is any user-facing change, since the develop feed omits the changelog by design.
Candis collapses approval-workflow sprawl — dynamic approvers and mandatory step fields land alongside an editor revamp.
The centerpiece of this window is a five-part Workflows release: a redesigned workflow editor, configurable mandatory fields per approval step, dynamic-field approver resolution (the right approver is picked from the receipt data — cost-center owner, project owner, invoice recipient), custom step labels, and the ability to import a workflow from another organization. Around that, Candis added Visa Click to Pay, a new layout and attachment support for Auslagen/Reisekosten (expenses and travel), an upcoming streamlined document layout (in beta from June 15), and improved automatching between credit-card transactions and invoices.
Candis is reducing the number of workflow templates a finance team has to maintain — dynamic approver resolution and mandatory-fields-per-step replace what used to be a copy-paste workflow per cost center. The expense/document side gets steady UX polish on a separate cadence. Together it reads as a product moving from configurable-but-fiddly AP toward an opinionated AP backbone for German mid-market finance.
Expect dynamic-field resolution to widen beyond approvers — likely to account assignment and cost-center splits — and the upcoming document-layout beta to roll out as the default in late June. The cross-org workflow import has the shape of a future template marketplace if Candis chooses to lean into it.
See more alternatives to Firefly III →
See more alternatives to Candis →