Home › Sovereignty
Security & data sovereignty

Your data lives where you say it does.

One database per client. Air-gap as a real deployment mode. Hardware-bound, in-memory encrypted server appliances with an audit trail that answers instead of apologising.

The sovereign stack

Nine guarantees that don't bend

One client. One database.

Your data is never pooled. Every deployment runs an isolated database — no multi-tenant sharing means your customer list can't be mined, analysed or leaked through a neighbour's compromise.

Air-gap capable, by design

The entire operation can run with zero external calls — permanently. Proven inside a secured defence installation, not tested in a lab.

The register never waits on the network

Local execution first, consolidation second. A site keeps billing, stocking and auditing with the cable unplugged; upstream sync is a queue, not a lifeline.

Role isolation at field level

Permissions bound to entity, surface and field — a cashier sees three buttons, a director sees everything, and nobody exports what they can't see.

Every action provable

Append-only audit trails: who did what, on whose authority, with before/after values. Custody disputes and inspections resolve from the record.

Your stack, your keys

AI providers run on your own API keys; the data layer is yours. Self-host the entire stack on your own server rack — leave with everything.

C-extension in-memory code encryption

On-premise server deployments store application logic as unreadable ciphertext on disk, decrypting and executing directly in RAM via a compiled C-extension loader — protecting statutory and pricing logic from inspection or tampering with $0 runtime decoder tax.

WMI Motherboard-UUID hardware binding (0ms lag)

Each on-premise server licence is cryptographically bound to the physical chassis via Windows WMI Motherboard UUID attestation, cached daily in-memory for 0ms transaction latency — a cloned disk or stolen backup cannot boot on unauthorized hardware.

NTFS icacls Read-Only code perimeter

Provisioned via Inno Setup NTFS icacls security rules that lock the application code tree as strictly Read-Only at the OS kernel level — neither malware nor a local admin can modify fiscal calculation code, while MySQL ledger writes and document intake run at full NVMe speed.

Talk to the engineers — or run the numbers yourself.

Bring your hardest requirement — offline, scale, sovereignty, hardware — to a live engineering session, or model your exact site count and five-year TCO right now.