Firefly III

Key features

• Double-entry bookkeeping Every transaction is recorded as a balanced double-entry movement between accounts, which keeps the books internally consistent as spending grows.[1]

• Budgets categories and tags Organize spending with budgets that cap categories, plus categories and tags that slice transactions by project, person, or purpose.[1][2]

• Automation rules Rules automatically categorize, convert, rename, or tag transactions as they arrive, and webhooks forward events to other tools.[1][2]

• Bank imports Pull transactions from banks through the companion Data Importer using providers such as GoCardless or Salt Edge, or import CSV files exported from online banking.[1][2]

• Recurring transactions Model salaries, subscriptions, and bills as recurring transactions so forecasts and budgets account for money that repeats.[1][2]

• Multi-currency accounts Hold accounts in any currency and record foreign-currency transactions, which suits households with money across borders.[1][2]

• Visual reports Review income, expenses, and budget adherence through charts and period reports that summarize where money went.[1][2]

• Open REST API A documented JSON REST API plus import paths from tools such as bunq and YNAB let third-party apps and scripts read and extend your data.[1][2]

Who will love it

• Privacy-first self-hosters People who want financial data on hardware they control get a complete free core: budgeting, rules, imports, and reports with no vendor cloud in the loop.[1][2]

• Hands-on budgeters Budgeters who enjoy tuning categories and rules get fine-grained control over spending awareness, including automated bank imports once configured.[1][2]

• Multi-currency households Households juggling accounts in several currencies benefit from native any-currency accounts and foreign-currency transaction support.[1][2]

Who should avoid it

• Server administration burden Running Firefly III means installing, updating, and backing up a PHP and database stack, so it suits people comfortable with Docker or server administration rather than absolute beginners.[1][2]

• Bank sync needs third parties Automated bank sync runs through the separate Data Importer and providers such as GoCardless or Salt Edge, which adds a link in the chain and provider coverage to verify for your bank.[1][2]

• Configuration learning curve Getting value from rules, categories, and the importer takes deliberate setup and tinkering, so the first weeks demand more attention than a managed app.[1][2]

What the reports suggest

Deployment and fit