Bank and crypto transactions matched with receipts, automatically — on your devices and your team’s, no cloud account.
Le Space Belege matches payments to receipts, books crypto in euros at the day’s rate and exports a DATEV package every month. Your devices and those of the colleagues you admit sync directly, peer-to-peer and sealed with your passkey – no cloud outage can bring your business to a halt. If you choose, an automatic, sealed backup lies on decentralised storage.
Belege /beˈleːɡə/ German for “receipts”
For the self-employed: how it works For developers and partners: the code
- open source, AGPL-3.0
- runs locally in the browser, as a PWA
- peer-to-peer, end-to-end sealed
- decentralised backup
Still early: keep your statements and receipts somewhere else as well.
See Belege in two minutes
Payments and receipts, matched, on your own devices. No account, and no server holds your books.
What Le Space Belege is, and what it is not
No account, and no server holding your data. The rest is craft.
- 01
Local-first
The app runs entirely in the browser, as a PWA without a network too. Your books live on your devices, every record and every receipt file sealed with keys derived from your passkey. No account, and no server that holds them.
- 02
Peer-to-peer
Your devices and those of the colleagues you admit sync the books directly, end-to-end sealed. A relay only passes sealed data along; by QR code or through the relay of your own bridge, no server on the internet is asked.
- 03
Decentralised backup & Safe
If you choose, automatic and incremental: a sealed backup on Aleph Cloud, addressed by the hash of its content. The same passkey on another device, a second one in a drawer or 24 recovery words bring the books back. The storage provider cannot read the backup.
- 04
Your own bridge
Bank, mailbox and interfaces are reached by a small program on your computer: Hibiscus (FinTS/HBCI), Enable Banking for banks across Europe, the mailbox read-only. Or in a confidential VM whose attestation your browser checks before any secret goes in.
- 05
Private AI, only on a click
Your own model: local with Ollama, Qwen for instance, or in an attested enclave (TEE) such as LibertAI’s, whose proof the bridge checks before every connection. To hosted models text leaves redacted (privacy-preserving: names, IBANs and addresses stay home); for the enclave you decide whether to redact. Every request carries the ✦ mark, and tokens and cost are listed per day, month and receipt. Le Space runs no AI.
- 06
Open source (AGPL-3.0)
Every line of code is open; anyone can check what happens to your data. App and bridge live on GitHub, every release with a changelog.
- 07
Native crypto
Kraken, Bitcoin, EVM, Cosmos, Monero: in euros at the day’s rate with its source, matched like bank payments, in the DATEV export.
- 08
DATEV export
SKR 03 with BU keys, one ZIP per month including all receipt PDFs, travel expenses as a numbered statement. For your bookkeeping or your tax adviser.
Collect, match, export
Three steps, every month.
- 1
Collect
Bank transactions arrive through Hibiscus, Enable Banking or as a CAMT.053 file; crypto from Kraken and your own wallets. Receipts come from the accounting mailbox, uploads, a folder, customer portals or Paperless-ngx. A small bridge on 127.0.0.1 does what a browser is not allowed to.
IMAP · FinTS · CAMT.053 · xpub · IBC - 2
Match
Every receipt scores points against every payment: amount, invoice and customer number, IBAN, vendor, date. Sure pairs are linked; the rest become questions on the home page. Own transfers, bank fees and refunds need no receipt. “Why this match?” explains every link.
sure from 90 points · candidate from 50 · at most 3 suggestions - 3
Export
One ZIP per month: the DATEV batch (EXTF) for your bookkeeping, every receipt as a PDF with its number, a statement per account and an overview for people. Only once every booking has a confirmed account.
DATEV_2026-09.zip · EXTF_Buchungsstapel_2026-09.csv
Start small, add more later
Belege runs in the browser, and for a lot that is enough. For bank, mailbox and AI, the bridge on your computer joins in. Six ways, the simplest first.
- 01
Only the browser
Upload bank statements as CAMT files and receipts by hand or from a folder, and Belege matches them and makes the DATEV package.
You need a browser and a passkey. Nothing leaves.
- 02
One computer with the bridge
The bridge fetches transactions from your bank and receipts from your mailbox, Paperless and customer portals, reads Kraken and wallets, and asks an AI: local, hosted with redaction, or LibertAI in an attested enclave.
Passwords and keys stay in your computer's keychain.
- 03
Several devices of your own
The same books on computer and phone. The devices meet in three ways: directly by QR code, through your bridge's relay, or through a Le Space relay, which works on the road too.
By QR code and through the bridge your devices ask no server on the internet. Nobody there learns that they talk to each other. A Le Space relay sees only that they talk, never what.
- 04
The phone uses your computer's bridge
Either as a device of its own, paired by invitation: your phone then reaches the bridge on the road too, with no browser open on the computer.
Or through the open Belege tab on the computer: then the bridge never goes online itself.
- 05
Backing up and getting it back
An encrypted backup lies on Aleph Cloud. On an empty device you get it back with your passkey or with the 24 recovery words.
Aleph cannot read the backup.
- 06
Working with others
Colleagues or your bookkeeper work in the same books, each with a passkey of their own and under their own name, writing or only reading. Your tax adviser gets the DATEV package every month, an assistant a redacted read-only share with an end date, and the Le Space invoicing app learns which invoices are paid.
You can take a member out at any time, and end a share at any time.
- Paying with Le Space Credits
What lives where, and who can read it
The short answer: only on your devices, and only you. The long answer is the threat model, linked below.
- Passkey instead of a password
- At every unlock the passkey answers once; every key is derived from that answer, anew each time. No key is stored, and the private key never leaves the authenticator.
- Stored locally
- The books live only on your device, in the browser’s IndexedDB, every record sealed on its own (AES-GCM) and every log entry once more as a whole. Not even the databases’ names say what they hold.
- No cookies, no tracking
- Neither this site nor the app sets cookies or loads anything from third parties. Fonts, code and films come from the same address as the page.
- The network under your hand
- A badge in the app’s header shows what is online. One click pauses everything; own devices and the invoicing app switch on and off one by one.
- The bridge on 127.0.0.1
- Bank, mailbox, language model and exchanges are reached by a small bridge on your own computer. It listens on 127.0.0.1 only, keeps its secrets in the system keychain and opens mailboxes read-only.
- Backup, sealed
- If you choose, the app backs everything up as one sealed file on Aleph Cloud. Only the same passkey opens it, not even Aleph. The envelope is public: whoever knows the CID can fetch the file, but not read it.
Run confidentially
Where Belege does not compute on your own machine, it computes in attested hardware. Attestation shows which image runs, not what it does.
- LibertAI
- Receipts read in LibertAI’s attested enclave, model qwen3.8-27b-tee. The bridge checks the attestation before every connection; a hosted bridge accepts no other model.
- Aleph Cloud
- The hosted bridge in a confidential VM (AMD SEV-SNP), started and stopped from Belege. It receives its secrets only after your browser has checked its attestation. Backups are kept sealed on Aleph.
Every movement in euros, with quantity, rate and source
A crypto account holds exactly one asset and has a ledger account of its own. Every booking carries the exact quantity, the rate of its day and where that rate came from, so the valuation can be decided differently later.
0.0042 BTC → 412,08 € · CoinGecko · SKR 03 / 1200
Sources
- Kraken, read-only
- Bitcoin by xpub, ypub or zpub
- EVM: Ethereum, Base, Arbitrum One, OP Mainnet, Polygon
- Cosmos: Nym, Akash, with IBC
- Monero from your wallet’s own export, read in the browser
- Filecoin with USDFC
Rates
- the value of one unit at 00:00 UTC of that day
- CoinGecko, Kraken or the ECB; a DEX pool at the booking’s block
- the other side of a trade, or by hand
Recognised
- own transfers across accounts, chains and bridges
- DEX swaps, token migrations and dust
- network and exchange fees, on their account
Which rate and which valuation method apply (FIFO, average cost, year-end valuation) is the tax adviser’s call. Belege records quantity, rate and source so that any decision can be applied.
Every line open, under AGPL‑3.0
App, bridge and documentation live in one repository. Whoever wants to know what happens to the data reads it, instead of trusting.
- App and bridge on GitHub, a changelog with every release
- Unit, end-to-end and bridge tests run on every push
- Bugs and wishes as issues on GitHub, open to everyone
- The crypto ledger format is MIT-licensed and openly documented
Hosted on IPFS, and you can check that
- There is no server of ours behind the app: the release run on GitHub publishes the build’s IPFS hash (CID) in its summary.
- The domain points at exactly that CID through DNSLink.
dig TXT _dnslink.belege.le-space.dehas to show the CID from the release, andhttps://<CID>.ipfs.inbrowser.link/serves the same build with no domain in between, byte for byte. - With your own IPFS node (Kubo) or the IPFS Companion extension your browser fetches the app straight from the network; then not even the visit is logged anywhere. This is optional.
What it costs
The app, nothing. What needs storage or compute elsewhere, you pay there or in advance as credit.
- The app nothing
- No subscription and no licence fee: every function in the browser, the bridge on your computer, own devices, members and the DATEV package. Free software under AGPL-3.0.
- A backup Aleph credits
- Only if you make one. You pay the credits to Aleph, not to us.
- Services from Le Space later, as credit
- Topped up in advance, in euros, with no account and no subscription. The credit belongs to your books, and remaining credit can be refunded.
Coming soon AI in an attested enclave (TEE) · Your own bridge VM in a TEE, started from your own encrypted bridge image
Open the app in your browserDo it yourself, or have it done
For small businesses and the self-employed, including those who hold or spend crypto assets: income in coins as well as expenses in utility tokens, say for Filecoin, Akash, Aleph or NymVPN services. The monthly DATEV package goes to your bookkeeping software or your tax adviser; the actual posting happens there.
We set Le Space Belege up with you: bridge, bank access, accounting mailbox, customer portals, your own language model. And we build adaptations: further blockchains and exchanges, special cases, and the automation of business processes, such as invoicing straight into the books over UCEP. This is a paid service; the app itself stays free.
Le Space Belege is tailored to the German market today: SKR 03, VAT, DATEV. The pattern carries further, since receipts, payments and a monthly package for the bookkeeping exist everywhere. For adapting it to other countries and tax systems, we are looking for partners.
Write to us belege@le-space.deBelege against bookkeeping from the cloud
Both end in a DATEV export. The difference is who reads along on the way.
| Feature | Le Space Belege | Cloud SaaS |
|---|---|---|
| Where the books live | only on your devices, sealed | on the provider’s servers |
| Account | none; a passkey | e-mail, password, often 2FA |
| Who can read your receipts | only you | the provider and its processors |
| Price | the app without a subscription; backup and services by use | a monthly fee per client |
| Source code | open, AGPL-3.0 | closed |
| Crypto | Kraken, wallets, day’s rate with source | rarely, or as an add-on |
| AI | your model, only on a click: local, attested or redacted | the provider’s models, in the background |
| Offline-first | yes: the app is a PWA, and the books are on the device | no |
| If the provider stops | the app keeps running, the code stays | export while you still can |
In fairness: a cloud service takes backups off your hands. With Belege they are yours, with a second passkey and the sealed backup on Aleph.
What people want to know before the first start
Is it really free?
Yes. Le Space Belege is free software under AGPL-3.0, with no subscription and no per-client fee. What costs money is what you choose yourself: your own language model, if you use one, and the credits for a backup on Aleph Cloud, if you make one. That backup is not your only protection against data loss: Belege works local-first and replicates its database and the receipts themselves, sealed and peer-to-peer, between your own devices and those of the colleagues you admit to your books, once you switch the network on. Each of these devices holds a copy. We still recommend a backup with a decentralised host: currently Aleph Cloud, with Filecoin in preparation.
Where is my data?
On your devices, in the browser’s IndexedDB, every record sealed on its own, and with the network switched on also on the devices of the colleagues you admit to your books. Le Space runs no server for it and sees none of it. What leaves your computer is your decision: the monthly ZIP, a sealed backup on Aleph, and redacted text to the model you set up yourself.
Why a decentralised cloud for compute?
Because no single provider decides whether a service keeps running, and because what runs there can be checked. Aleph Cloud is a network of independent operators: if a compute node fails or its operator withdraws, the same image starts on another, with no hyperscaler contract and no migration. In a confidential VM (AMD SEV-SNP) memory is encrypted even from the operator, and Belege checks by attestation which image is running before it hands over a secret. With a central host, all you can do is trust the provider. Today Belege uses this twice, if you choose it: for the language model in LibertAI’s attested enclave, and for the hosted bridge in a confidential VM on Aleph, which you start and stop from Belege. The limits: attestation shows which image runs, not what it does, and the operator still sees when and how much is transferred.
Why decentralised storage for the backup?
Because what comes back can be checked, and because the file depends on no single provider. On IPFS a file’s address, its CID, is its own hash: what you restore is byte for byte what you backed up, and nobody can swap it unnoticed. Any node that holds the file serves the same CID; changing provider changes neither format nor address. If a node or Aleph’s gateway is down at restore time, the browser fetches the file itself from the IPFS network, from any node that holds it, and checks every block against its CID, so a stranger’s node is as safe as your own provider. Filecoin, in preparation, goes a step further: storage providers prove cryptographically, again and again, that they still hold the data, rather than merely promising it. None of them can read the file: Belege seals it before upload, and only a passkey of your books or their recovery words open it. The limits: the sealed envelope is public, so whoever knows the CID can fetch it but not read it; and it is kept for as long as there are credits.
What happens if I lose my passkey?
With a single passkey that is not synced, the books are lost, and so is every backup: it stays on Aleph, but nothing can open it any more. Hence the Safe: under Settings → Keys a second passkey gets a slot of its own and opens the same books. A passkey in iCloud Keychain or the Google Password Manager travels with you anyway. The app says so while only one passkey is registered. Books have to be kept for eight to ten years in Germany, so: a second passkey, and regular backups.
Which banks and sources work?
German banks through Hibiscus (FinTS) via the bridge, banks across Europe through Enable Banking with your own application, and any bank that provides CAMT.053 statements (Revolut or GLS, say) directly in the browser. Company credit cards as accounts of their own from the issuer’s CSV. Receipts from an IMAP mailbox, uploads, a folder, customer portals and Paperless-ngx; e-invoices (XRechnung, ZUGFeRD) are read without AI.
What is the bridge, and do I have to install it?
A small program that does what a browser is not allowed to: bank (FinTS), mailbox (IMAP), exchanges, wallets and the language model. Quite a lot works without it: importing CAMT.053, uploading receipts, matching, exporting. For the rest there are two ways. Technically minded people and administrators install the bridge themselves on their own computer (pnpm bridge from the repository): it listens on 127.0.0.1 only, keeps secrets in the system keychain, and is paired once with a code. Or you start it on demand in a confidential VM (TEE): credentials and API keys go in only after your browser has checked the VM’s attestation, and do not leave the enclave; Le Space never sees them. This way is still new.
Does an AI see my receipts?
Only when you click, and only the model you set up yourself. Recommended: a local model with Ollama or LM Studio, Qwen for instance, so nothing leaves your computer. If setting that up is too much: a model in LibertAI’s confidential enclave (TEE), Qwen as well (qwen3.8-27b-tee); the bridge checks the enclave’s attestation before every connection and follows none that has been swapped. A hosted bridge accepts only this model. With other hosted models the bridge first redacts names, IBANs, addresses and more; that limits what leaves, it does not make a text anonymous. For the enclave the setup asks whether to redact anyway and suggests no, as nobody between the bridge and the enclave can read along. Every call is listed with model, duration and tokens in the history, the cost in the statistics. Le Space runs no AI.
Does it replace my tax adviser?
No. Belege is pre-bookkeeping: it collects, matches, suggests SKR 03 accounts and BU keys for you to confirm, and hands over a DATEV package every month. The VAT overview is a help for the advance return, not the return itself. Valuing crypto, the year-end accounts and what belongs on which account remain your tax adviser’s work.
Does it run on my phone?
Yes, the app is a PWA. The same books on phone and computer after a passkey proof, over public relays, a relay in your own bridge, or by QR code with no relay at all on your own network. The QR code in this page’s header opens the app on your phone.
Which browser do I need?
A current browser and a password manager with PRF support: Chrome, Safari or Firefox with iCloud Keychain, Google Password Manager or 1Password, say. Without PRF Belege opens no data, and the app tells you so at the first start.