Git-native. Audit-proof. No vendor lock-in.
Gitcover.de bundles the entire GitCover ecosystem: the open community, the rules of the GCBoK, the Git-native tools — and the craft that brings it all into practice. A foundation that belongs to you: your data, your evidence, your sovereignty.
Three promises you can verify.
Audit-proof across the full period
Git historisation supports immutability. Process documentation and internal controls live traceably in the repository — from invoice to closing, across eight or ten years.
Sovereignty instead of cloud lock-in
Your data stays on your machine and in your repository. No provider switch with data loss, no insolvency dependency, no format change that renders evidence unreadable.
Order everyone understands
Millions of developers know Git. That shared foundation makes compliance verifiable and explainable — for tax advisers, auditors and authorities alike.
Paperwork does not do itself. But it does fall into order.
Most people look first for an e-invoicing solution. Good — that is exactly where it starts. The structured dataset becomes an invoice, the invoice a booking, and all of it a verifiable piece of evidence. Git-native, audit-proof, without your data landing in someone else's cloud.
- Invoices in the vendor's format
- Monthly fees, growing tiers
- Limited data access and exportability
- Switching costs evidence, time and money
- Open tools instead of an expensive cloud solution
- Invoices, books and evidence stay in your repository
- Readable with standard tools, permanently
- No lock-in — exportable at any time
Tools we use ourselves every day.
What we recommend, we run in our own network first: our gc-* tools are born in the daily work of the GitCover companies — with real invoices, books and signatures. Only what proves itself there moves on to the community and to users.
One invoice, one hash, one leading source
Capture, check, deduplicate and file inbound and outbound invoices in a GoBD-compliant way — with sidecar and an immutable evidence chain.
Books that reconcile themselves
Generate ledger, open items and reports deterministically — debits equal credits, traceable and verifiable.
Evidence you can verify
Sidecars, process containers and signatures — versioned in Git, agent-ready and traceable for auditors, tax advisers and authorities.
The tools keep growing — progress from the network, also in interplay with agentic helpers (GCA). See News.
The diary records what everyone does — human and agent.
Conventional solutions capture time, invoices and bookings — for people. With us, the diary records who acts: the acting person and the agent alike. Every step becomes a traceable, verifiable entry. Not a side effect — but the very foundation for humans and AI to work together.
The human in the lead
Whoever acts records it. The entry states time, activity, responsibility and evidence — the person keeps oversight and approval (human in the loop).
The agent as an actor
An agent that acts is recorded in the same diary — in the same entry format. Every action stays attributable, whether it comes from a person or a machine.
Verifiable, not guessed
Deterministic tools yield the same result for the same input. Only then does AI execution become solid evidence — the call for determinism, put into practice.
- Capture time and bookings — for people
- AI stays a tool beside the filing, with no evidence of its own
- What an agent did is not part of the record
- Automation without solid proof
- One format for everyone who acts — person and agent
- Every action becomes a verifiable, versioned entry
- Basis for clean human ↔ AI collaboration (HITL)
- No side effect — part of the evidence itself
Results that belong to you — not to a vendor.
The difference is not the feature set, but who owns the evidence and whether it outlives the retention period.
- Evidence in the vendor's format
- Dependence on price, insolvency, policy
- Format change can render invoices unreadable
- Migration risk on every switch
- Open Git repositories as the evidence layer
- Data stays on your machine
- Readable with standard tools, permanently
- Vendor-independent, exportable at any time
Theory, standardisation, tools and practice interlock.
Community & Open Source
The open trust and standards core: reference models, tools, community.
Body of Knowledge
The GCBoK standardises the proper use of Git repositories for compliance — freely accessible.
Tools & Compliance-as-Code
GCPN, GCEP, OSCAL, OPA/Rego — versioned, testable evidence and rule mechanics.
Practice & craft
The bridge between businesses and the service-provider craft that implements, operates and audits.
What we promise — and what we do not.
GoBD-compliant results following the rules of the GCBoK. Responsibility for regularity lies with the business (GoBD Rn. 21). GitCover partners support with their own, contractually defined services; open-source tools used are under their respective licences.