Enterprise · on-prem delivery · regulated industries
Keep your raw telemetry
on-prem.
The cloud control plane never sees a byte of your fleet's network data. Only Ed25519-signed digests flow up, for billing and fleet health. Built for financial services, healthcare, defence and the public sector.
No raw data leaves your networkKernel-level capture stays on-prem. Only aggregate, signed digests cross the boundary.
Your keys. Always.AWS KMS, Azure Key Vault, GCP Cloud KMS or HashiCorp Vault. We never hold or request your keys.
Air-gap-capable collectorLocal capture continues during any cloud outage. Only digest uploads need outbound connectivity.
Tamper-evident by designEvery daily digest is Ed25519-signed. Edited digests are rejected, which gives you chain-of-custody evidence.
Compliance-alignedUK GDPR Art. 44DORABSI C5NIS2ISO 27001 — in progress 2027SOC 2 Type II — in progress 2026
How hybrid works
Four components. One boundary.
Only the last arrow crosses your network perimeter, and it carries only a signed aggregate digest, never raw telemetry.
01 · YOUR NETWORKClient appAgent on each device sends raw events over an encrypted local channel to the collector, never straight to the internet.
02 · YOUR NETWORKCollectorA container inside your perimeter. Normalises events, writes them to your storage, signs a daily digest.
03 · YOUR NETWORKYour object storageS3-compatible storage you control, encrypted with your KMS keys.
04 · OUR CLOUDDigest ingestOne narrow endpoint. Accepts Ed25519-signed JSON digests only, for billing and fleet health.
▲ The violet line is your network perimeter.
Security & data residency
What is in a digest?
A compact JSON document signed with the collector's Ed25519 key, holding aggregate counters only. No host identifiers, IP addresses, process names, usernames or payloads.
| Field | Type | Description | PII |
|---|---|---|---|
| event_count | integer | Events captured in the 24-hour window | No |
| bytes_up | integer | Bytes uploaded across all devices | No |
| bytes_down | integer | Bytes downloaded across all devices | No |
| top_providers | string[] | Top 5 cloud provider labels — no IPs | No |
| anomaly_markers | integer | EWMA anomaly triggers in the window | No |
| tenant_id | uuid | Your opaque tenant identifier | No |
| date | ISO 8601 | UTC date of the digest period | No |
| signature | Ed25519 | Collector signature over the fields above | No |
Built for regulated constraints.
UK GDPR Art. 44Raw device telemetry never leaves your perimeter, so no adequacy decision or SCCs are needed for the data plane.
DORAAir-gap-capable collector: a cloud outage doesn’t stop local capture or log integrity.
BSI C5Customer-managed KMS keys or on-prem HSM satisfy criteria OPS-10 and OPS-11.
NIS2Keeps critical telemetry under Article 21(2)(j) supply-chain controls.
Fastest to deployYour VM — single containerOne VM or bare-metal server runs the collector and a local object store.
Production recommendedYour Kubernetes — Helm chartSigned Helm chart; your StorageClass and KMS provider. Works with Istio or Cilium.
Customer-cloud nativeYour AWS account — TerraformBucket with SSE + your CMK, IAM role and task definition, all in your account.
Ready for your procurement team.
Available to qualified procurement leads under NDA. Typical turnaround is two business days.
- MSA with Hybrid data-plane addendum
- DPA — GDPR Art. 28, EU and UK variants
- SIG-Lite / CAIQ questionnaire (pre-filled)
- ISO 27001 control cross-walk (Annex A)
- SOC 2 Type II — audit in progress, target 2026
- Penetration test executive summary
- Ed25519 public key bundle