Host Firefly III without installing anything
A personal ledger kept in double entry: every euro leaves one account and lands in another, with envelope budgets, automatic rules and reports spanning years.
Starting at €8.99/month
Introduction
Firefly III installed, updated and backed up by us, on a machine in France. A complete personal finance manager: accounts, budgets, categories, automatic rules and reports. You install nothing and configure no server: the application is online a few minutes after you order, under your own name.
The plan that suits it is App Confort at €8.99/month incl. VAT — 4 GB of memory. Firefly III is not a spending notebook: it is a PHP application on top of a real relational database, whose rules engine can replay several thousand entries in one pass and whose reports aggregate years of history. After three or four years of statements, it is those recalculations that need the memory, not the daily data entry.
Your banking data stays strictly with you: Firefly III does not go and fetch it from your bank, you bring it in. The companion importer reads the CSV files banks offer for download and remembers how your columns map onto its fields, so next month's import takes two clicks. In the other direction everything comes back out as CSV, and a REST API exposes the whole set.
What Firefly III can do
Proper double-entry bookkeeping
Every operation has a source and a destination: current account to shop, salary to current account, current account to savings. A transfer between two of your own accounts therefore never shows up as spending — which is exactly what ordinary tracking apps get wrong.
Budget envelopes and savings jars
You set an amount per category and per period, and the application shows what is left at any moment. Piggy banks handle dated projects: putting something aside every month for a holiday or for a tax bill.
A rules engine
A rule says "if the description contains TESCO, then category Groceries, tag Food". It applies to future imports and can also be replayed over everything already recorded.
REST API and mobile apps
A full API, protected by a personal token, lets the project's third-party mobile apps record an expense at the moment you pay it, rather than waiting for the end-of-month statement.
What people actually use it for
Running the accounts of a two-person household
A joint account and two personal accounts in the same instance: you finally see who paid for what, and the monthly transfer into the joint account stops counting as yet another expense.
Setting money aside for tax when self-employed
A freelancer creates a jar for tax and social contributions and assigns a percentage of every payment received. "How much can I actually pay myself this month" finally has a number for an answer.
Following a loan to the end
The mortgage is declared as a liability: each instalment reduces the principal, and the net worth curve includes the debt instead of ignoring it.
Leaving a banking aggregator
Rather than handing bank credentials to a third-party service, you download the monthly CSV and import it. Account data never leaves the server you rent.
Understanding where the money went over three years
Reports compare planned budget against actual spending, category by category, over any period you choose. That is where forgotten subscriptions finally become visible.
Hosted in France
In our own datacentre in Nouvelle-Aquitaine, which we operate ourselves. Your statements and your net worth do not leave the country.
Frequently asked questions
Nothing. You choose the application, fill in the fields it asks for — often an email address and a name — and it goes online. Access arrives by email with the address and the credentials.
Not by itself, and that is by design: the application core holds no banking credentials. Data comes in through the project's importer, which reads the CSV exports banks provide and can also talk to PSD2-compliant aggregators. In practice the monthly CSV import is the sturdier route: it depends on no third-party contract and does not break when your bank redesigns its website.
No. Firefly III keeps personal accounts: it issues no invoices, handles no VAT and produces no statutory returns. For company accounting and invoicing, look at Dolibarr or Akaunting instead. Plenty of freelancers run both: one for the business, one for the household.
Yes, with nothing to negotiate. Every entry exports to CSV, and the REST API exposes accounts, budgets, rules and tags. Firefly III is free software: we host it, we do not own it.
Yes, they are part of the service. A self-hosted application left un-updated is a security risk, not a saving.