It’s 2026, and I’m facing a reality check: 80% of small businesses are on cloud accounting now. When I tell prospective clients I use Beancount with Git version control, I increasingly get this response: “That sounds…complicated. Why aren’t we on the cloud like everyone else?”
I’ve been running my bookkeeping practice for 10 years, converted 20 clients to Beancount over the past 3 years, and honestly? I love it. Plain text accounting gives me transparency, version control gives me an audit trail commercial platforms can’t match, and Python importers give me true automation. But here’s the problem: my clients don’t care about any of that.
The Cloud Pressure Is Real
Clients see QuickBooks Online ads promising:
- Real-time mobile access to their financials
- Automatic daily bank sync (no manual imports)
- Collaboration with their business partners from anywhere
- “Open the app and see your numbers instantly”
Meanwhile, my current setup:
- Git repos hosted on my private server
- Fava instances I run for each client (they don’t access it directly)
- Manual importer runs twice a week
- Reports delivered via email as PDFs
When I try to explain that version control is superior to QuickBooks’ “audit log,” their eyes glaze over. They don’t want to understand Git. They want to tap an app icon and see their cash balance.
Is Beancount Actually “Cloud-Ready”?
I keep hearing that plain text accounting is flexible and can work in the cloud, but I’m struggling to see how. Here’s what I mean:
Mobile access: Clients expect native iOS/Android apps. Fava is a web interface, sure, but it’s not designed for mobile. And I’m not about to expose my Fava instances publicly without serious security hardening.
Automatic bank sync: QuickBooks connects to 14,000+ financial institutions. I write Python importers for each client’s specific banks and run them manually. Yes, I could automate with cron jobs, but then I lose the review step. And if an import fails, clients won’t know until I tell them.
Collaboration: In QuickBooks Online, I can set user permissions for the business owner, their partner, their accountant. In Beancount, collaboration means granting SSH access to my server or teaching them Git. That’s a non-starter for 90% of small business owners.
Client perception: Let’s be honest—telling a client “I’ll commit your transactions to a Git repository” sounds either overly technical or actively suspicious. QuickBooks sounds normal. Beancount sounds like a hobby project.
My Real Question to This Community
Are you successfully running Beancount practices in 2026’s “cloud-or-die” environment? How?
Specifically:
- How do you host Beancount for client access? DigitalOcean? AWS? Local server with VPN?
- Do you show clients Fava directly, or just deliver reports?
- How do you handle the “why can’t I check my balance from my phone?” question?
- Have you built custom client portals on top of Beancount?
- What’s your pitch when clients ask “Why not just use QuickBooks Online like everyone else?”
The Bigger Question: Should We Even Try?
Part of me wonders if I’m fighting a losing battle. Maybe plain text accounting is only viable for:
- Personal finance enthusiasts who love tinkering
- Solo practitioners tracking their own business
- Developers who already live in text editors and terminal
Maybe for professional bookkeeping practices serving non-technical clients, commercial cloud platforms are just…the reality. And I need to either adapt (migrate clients back to QuickBooks/Xero) or accept I’ll only serve a tiny niche of clients who value data ownership over convenience.
Has anyone else felt this pressure? How did you navigate it? I’m not ready to give up on Beancount—it’s transformed how I think about bookkeeping—but I also can’t ignore that my clients are asking for features I can’t easily provide.
Would love to hear how others are handling this. Especially if you’ve successfully built a “cloud-native” Beancount practice that satisfies modern client expectations.