Version Control for Your Finances

Your books. Every change, accounted for.

Bring the clarity of Git to your finances. Keep your ledger in plain text, work with the tools you love, and make every change traceable.

Start Free Explore a live ledger

Start free. No credit card required. Your ledger stays yours.

expenses.beancountmain

12026-09-01 * "Client payment"
2  Assets:Bank:Checking   2,500.00 USD
3  Income:Consulting    -2,500.00 USD
4
52026-09-02 * "Workspace"
6  Expenses:Office         120.00 USD
7  Assets:Bank:Checking    -120.00 USD

Add office expense

+ 2026-09-02 * "Workspace"
+   Expenses:Office         120.00 USD
+   Assets:Bank:Checking    -120.00 USD

One new expense. A clear record of why.

Illustrative ledger

Data Ownership
Git Protocol
Version History

CLONE. EDIT. COMMIT.

Your workflow. Now for your money.

Three simple steps to version-controlled financial management

01
Clone Your Ledger
Clone your ledger repository to your local machine using standard Git commands
```
git clone ssh://[email protected]:2222/you/ledger.git
```
Use the clone URL from your own ledger.
02
Edit Locally
Use your favorite editor: VS Code, Vim, Emacs, or specialized Beancount tools. Your choice, not ours.
```
cd ledger
vim expenses.beancount
```
03
Push Changes Back
Commit your changes and push to sync automatically. Every change is tracked with full audit history.
```
git add expenses.beancount
git commit -m "Add office expense"
git push origin main
```

BUILT TO STAY YOURS

A file you own. A history you can trust.

Your ledger is a readable Beancount file in a standard Git repository. Take a full clone with you, keep your preferred editor, and choose where your data lives.

expenses.beancount

Plain text. Open format. Yours to keep.

Tool Freedom

Edit with any editor: VS Code, Vim, Emacs, or specialized Beancount tools. Your choice, not ours.

Complete Audit Trail

Review what changed, when it changed, and the recorded author. A clear history makes it easier to explain and check your books.

Distributed Backups

A full clone keeps your ledger and its version history on your own machine. Fetch regularly to keep that copy up to date.

Collaboration Ready

Use branches, pull requests, and code review workflows to collaborate with your team or accountant.

How It Works

See the Git workflow in action

Follow a ledger from local edits to a synced repository.

Read the getting-started guide

Frequently Asked Questions

A few things worth knowing before your first commit.

How does Git hosting work with Beancount.io?

Your Beancount.io ledger has a private repository on git.beancount.io. Connect using your SSH key, clone the repository, edit locally, and push your changes back with standard Git commands.

Can I use my own Git server instead?

Absolutely! Since your ledger is in a standard Git repository, you can push it to GitHub, GitLab, your own Gitea instance, or any Git server you prefer. The data is yours, stored in an open format.

What happens to my data if I stop paying?

You keep everything. Your complete financial history is in a standard Git repository that you've already cloned to your local machine. The data is yours, not locked in a proprietary format. This is a key advantage of Git-based accounting.

Is my financial data secure in Git?

The Git workflow shown here connects over SSH. Keep your private key secure and grant repository access only to people you trust. A local clone contains your financial data, so protect your devices and backups too.

How do I collaborate with my accountant?

You can add your accountant as a collaborator on your Git repository. They can clone the repo, make changes or suggestions, and create pull requests for you to review. Every change is tracked with full history and accountability.

Get Started with Git

Make your next commit a financial one.