Every system your company has ever bought had an expiry date built into it. This one does not. Updates add, they never break, and a document written today still opens in thirty years. There is no next migration.
Runs in this tab. Nothing to install, nothing sent anywhere.
Generate DATEV-compatible booking batches directly from your git ledger. Your tax advisor imports the file without manual re-entry.
Produce legally compliant XRechnung 3.0 XML for German B2B and public sector. Zero dependencies. Zero float math.
Every booking is a cryptographically signed git commit. Tamper-evident by design. Verify with standard git tools.
BigInt minor units. 1,000.00 EUR is stored as 100000. No floating point. No rounding errors. No epsilon. Exact down to the cent.
Immutable audit trail, exact money, and documented procedures. Verfahrensdokumentation included. German tax law, satisfied.
Pure JavaScript. No npm install. No 500MB node_modules. Runs in the browser, on a Raspberry Pi, or in a bunker.
The licence was never the expensive part. The expensive part is that every few years the format changes, and your company has to be carried across by people who charge by the day.
scroll the diagram sideways
New rule constructions are additive, so rules written years ago keep running unchanged. There is no version of this software that stops reading the previous one.
A company is documents and the transactions that change them. Both are signed commits in a git repository. A format that simple has nothing in it to break.
Meet a rule it does not understand and it stops and says so. Silent wrong arithmetic is the one failure an accounting system must never have, so it is designed out.
No maintenance window, no coordinated cutover, no fleet on the same build. Machines on different versions keep working together.
An integration is a project: a scope, a partner, a six figure number and a date it slips past. A dialect is a file. It describes how a foreign system names things, and the runtime reads it. Adding Shopify is not a change request.
scroll the diagram sideways
The same mechanism runs in both directions, which is why an export is not a separate feature. What DATEV is owed and what Shopify is told are the same rules read the other way round.
An ERP is normally a translation. The business explains itself to consultants, consultants explain it to developers, and five years later nobody can change a discount rule without a project. We deleted the translation. The description of the company is the running system.
A purchase order over 10,000 EUR needs a second signature from the managing director.
Order PO-2027-0114
refused: 14,200 EUR
exceeds the limit and
carries one signature.
No configuration screen, no consultant, no release train. The rule is the text and the runtime reads the text.
Debt collects in the gap between what the business meant and what was built. Remove the gap and there is no gap to fill.
A German auditor asks whether a booking can be traced to the rule that permitted it. This system refuses the write when no rule covers it, which is a stronger answer than a log.
Every interface your company uses today will look wrong in ten years, and in most systems the interface and the data are the same object, which is why replacing one means replacing both. Here the core has no screen at all. Interfaces dock on.
scroll the diagram sideways
It reads and writes through the same API everything else uses. It has no privileged path and it cannot decide anything the rules do not already allow.
A model can draft a rule and propose a screen. What actually runs is the written rule, evaluated the same way every time. No model sits in the decision chain.
The interface talks to a documented core. Replacing the screen has never been the part that costs money here.
Storage and compute flow to wherever there is capacity, across the laptops, servers and phones you already pay for. Add a machine and the system gets bigger. Lose one and nothing stops, because no machine is irreplaceable.
Five companies decide how most of the world's businesses are allowed to operate, and what that costs. The point of this project is that a company should not structurally need any of them. Sovereignty here is not a contract clause or a hosting region. It is that there is nothing to revoke.
There is no Enterprise Edition, because there is nothing to upgrade to. The freelancer and the group with three continents run identical code. The only difference is how many machines are in the mesh and how much of the company is written down.
A founder with a laptop, offline on a train.
same coreA Mittelstand company across two sites and a warehouse, no server room.
same coreA group across three continents, each entity sovereign, one operating model.
same coreYou cannot negotiate your way out of a dependency. You can only stop having it. Open a working company in this tab and see what that feels like.