Multi-cloud & data sovereignty
Run reconciliation where your data is legally allowed to live — any cloud, your own datacentre, or fully airgapped.
Your data can't always leave the building
Regulated and enterprise customers often can't send their data wherever a vendor happens to run. It has to stay in a specific region, inside their own datacentre, or in an environment with no outbound internet at all.
A SaaS-only tool forces every byte through one vendor's cloud. That's a non-starter when sovereignty, residency, or airgap rules apply — and it puts your reconciliation on a single vendor's availability.
One stack, running wherever your data lives
The identical platform runs on any Kubernetes — no cloud-provider lock-in.
Runs on any Kubernetes
The identical stack runs on Hetzner, Civo, GCP, AWS, bare metal, or fully airgapped.
No cloud-provider lock-in
No dependency on any single vendor's managed services in the data path.
Data stays in region
Deploy where residency and sovereignty rules require — the data never has to leave.
Per-tenant isolation
Every tenant is cryptographically isolated across storage, messaging, and database.
Standalone cells
A fully isolated tenant can run their own standalone cell with no dependency on any global service.
Airgap-capable
Run entirely without outbound internet when your environment demands it.
Not another SaaS-only silo
SaaS-only competitors force your data through one vendor's cloud — one region, one provider, one availability domain. DataRecs runs where you need it to run, so sovereignty and residency are a deployment choice, not a compromise.
Enterprise-grade by default
The hard parts of trustworthy reconciliation are built in — not bolted on later.
Envelope encryption + BYOK
Every credential and dataset is envelope-encrypted with a key unique to you. Bring your own key when policy demands it.
Tenant isolation
Each tenant runs in its own isolated space — separate storage, messaging and database scope. No shared buckets, no shared keys.
HMAC-signed webhooks
Outbound webhooks are signed so your systems can verify every payload really came from DataRecs before acting on it.
Multi-cloud
The same stack runs on any Kubernetes cluster — Hetzner, Civo, your own datacentre — with no cloud-provider lock-in.
- PostgreSQL
- MySQL
- Oracle
- SQL Server
- DB2
Reconcile your data where it's allowed to live
Tell us your residency and sovereignty constraints — we'll show you the same platform running exactly where you need it.