Local event storage
Raw telemetry written to S3-compatible object storage you control — your own cloud account or on-premises. Encrypted at rest with your KMS keys. Retention period under your control.
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.
On-prem telemetry · Cloud digests only · Your keys, your storage
Choose where your data lives. Air-gapped and on-prem deployments keep per-app telemetry inside your own environment. For managed hosting, our US region is available today and our EU region is rolling out, with multi-cloud deployment available for Enterprise on request.
The full stack runs inside your own environment. Per-app telemetry stays on your hardware and never leaves your network.
An on-prem collector keeps raw flow records on your network. Only Ed25519-signed licence and digest metadata reaches the control plane.
Prefer a fully managed control plane? Our US region is available today and our EU region is rolling out. Multi-cloud deployment is available for Enterprise on request.
Compliance-aligned
Regulated organisations in financial services, healthcare, defence, and the public sector face strict constraints on where network monitoring data may be processed or stored. The Hybrid tier is purpose-built for those constraints.
International data transfer restrictions. Raw device telemetry never leaves your network perimeter — no adequacy decision or SCCs required for the data plane.
Operational resilience for financial sector. Collector runs air-gap-capable; a cloud outage does not stop local event capture or log integrity.
Germany federal information-security catalogue. Customer-managed KMS keys (AWS KMS, Azure Key Vault, or on-prem HSM) satisfy BSI C5 criteria OPS-10 and OPS-11.
EU cyber-security directive for healthcare and energy operators. Hybrid deployment keeps critical telemetry under Article 21(2)(j) supply-chain controls.
Only the last arrow crosses your network perimeter — and it carries only a cryptographically signed aggregate digest, never raw telemetry.
┌───────────────────────────────┐
│ NetInsightPro agent │
│ on each managed device │
│ Windows / Linux / Android │
└──────────────┬────────────────┘
│ raw events (encrypted, never leave your network)
▼
┌───────────────────────────────┐ ← YOUR NETWORK PERIMETER
│ Collector │
│ runs as a container inside │
│ your environment │
│ Receives + normalises events │
│ Signs daily digest (Ed25519) │
└──────┬────────────────┬───────┘
│ │
│ raw events │ signed digest only
▼ ▼
┌────────────────┐ ┌───────────────────────────────┐
│ Your object │ │ NetInsightPro cloud │
│ storage │ │ a single narrow endpoint │
│ S3-compatible │ │ Billing + fleet health │
│ your KMS keys │ │ Signed digests only │
└────────────────┘ └───────────────────────────────┘
← All data at rest encrypted with YOUR keys →
← Cloud sees ONLY signed digests, NOT raw events →
NetInsightPro agent on each managed device. Sends raw events over an encrypted local channel to the collector — never to the internet directly.
Runs as a container inside your perimeter. Normalises events, writes them to your object storage, and produces a daily signed digest.
Raw events land in S3-compatible object storage you control — your own cloud account or on-premises. Encrypted with your KMS keys; we never hold or request them.
A single narrow cloud endpoint that accepts Ed25519-signed JSON digests only. Used for billing metering and fleet health. Zero raw events in transit.
Every capability is purposefully placed on the correct side of your network perimeter.
Raw telemetry written to S3-compatible object storage you control — your own cloud account or on-premises. Encrypted at rest with your KMS keys. Retention period under your control.
Collector operates without internet for event capture and local storage. Only the daily digest upload requires outbound connectivity — and can be proxied.
Customer-managed keys via AWS KMS, Azure Key Vault, GCP Cloud KMS, or HashiCorp Vault. Key rotation follows your own KMS schedule.
Forward normalised OCSF events to your on-prem SIEM via syslog-TLS. Splunk, Sentinel, Elastic, Chronicle, and QRadar tested. Data stays inside your perimeter.
Ed25519-signed daily digests only. Aggregate counters with no PII, no hostnames, no process names. Signature rejected if tampered.
Cloud console shows collector last-seen timestamps, digest receipt status, and anomaly-marker trends — all derived from digests, never raw events.
Seat count and usage metering operate from digest data only. Raw device telemetry is never transmitted to or stored in our cloud infrastructure.
Policy distribution, licence provisioning, and fleet health dashboards accessible from the cloud console without requiring VPN into your perimeter.
Every device runs the same Pro client. On Hybrid, the admin console sits in your VPC; raw events never leave your perimeter — cloud sees only Ed25519-signed daily digests.
| App | Bytes | Verdict |
|---|---|---|
DeepSeekcn | +3.1 MB/min | |
Qwencn | +1.8 MB/min | |
Mistraleu | +0.7 MB/min | |
Cohereus | +0.4 MB/min | |
Slack | +6.4 MB/min | |
Dropbox | +14.2 MB/h |
| Hostname | Last seen | Status |
|---|---|---|
| workstation-001 | 2 min ago | active |
| mbp-finance-04 | 5 min ago | active |
| devbox-01 | 14 min ago | active |
| pos-store-12 | 47 min ago | idle |
The interactive demo below shows the admin-side and customer-side forwarder / collector flow — the same architecture your deployment runs.
Raw events are normalised by your Forwarder/Collector and written to storage you own. Only an Ed25519-signed daily digest ever reaches our cloud — and only in the Hybrid shape.
Ed25519-signed. Verifiable by your auditor against the published collector public key — no cloud round-trip required.
Air-gap-capable collector supports classified networks and disconnected environments. No cloud dependency for telemetry capture. Ed25519 signatures provide tamper evidence for chain-of-custody requirements.
DORA and FCA Operational Resilience alignment. Local capture survives cloud outages. Immutable audit log with 7-year retention in your own object store. SIEM forwarding to your existing on-prem SOC.
Patient-adjacent devices generate telemetry that cannot leave controlled environments. Hybrid keeps all raw events under your clinical data governance. UK GDPR + NHS Data Security Standard alignment.
Data sovereignty requirements met natively — no adequacy decisions or SCCs required for the data plane. BSI C5 and NIS2 supply-chain controls supported. On-prem HSM key management via HashiCorp Vault.
Each daily digest is a compact JSON document signed with the collector's Ed25519 key. It contains only aggregate counters — no PII, no hostnames, no process names.
| Field | Type | Description | Contains PII? |
|---|---|---|---|
| event_count | integer | Total events captured in the 24-hour window | No |
| bytes_up | integer | Total bytes uploaded across all devices | No |
| bytes_down | integer | Total bytes downloaded across all devices | No |
| top_providers | string[] | Top 5 cloud provider labels (e.g. AWS, GCP) — no IPs | No |
| anomaly_markers | integer | Count of EWMA anomaly triggers in the window | No |
| tenant_id | uuid | Your tenant identifier (opaque to us for correlation) | No |
| date | ISO 8601 | UTC date of the digest period | No |
| signature | Ed25519 | Collector private key signature over the above fields | No |
No host identifiers, IP addresses, process names, usernames, or application payloads appear in any digest. The digest schema is versioned; breaking changes require a collector upgrade with advance notice.
All three encrypt data at rest with customer-managed keys. Keys never leave your account.
One VM or bare-metal server in your environment runs the collector and a local object store. Suitable for smaller regulated fleets or proof-of-concept.
The collector runs as a container in your environment. Secrets injected via environment variables. TLS termination via your reverse proxy. Collector image signed for supply-chain verification.
Collector deployed as a Deployment + Service inside your cluster. Persistent storage via a StorageClass backed by your CSI provider.
A signed Helm chart is provided. Values cover replica count, resource limits, and KMS provider (your choice — AWS, Azure, GCP, or HashiCorp Vault). Works with Istio or Cilium service mesh.
Bootstraps an object-store bucket with SSE + your KMS CMK, IAM role for the collector, and a container task definition — all inside your AWS account.
You retain key administrator role. Bucket policy denies all access without matching KMS grant. Module output exports bucket and task role ARNs for your own CI/CD pipeline. NetInsightPro never receives credentials.
The following artefacts are available to qualified procurement leads under NDA. Typical turnaround is two business days.
Hybrid tier is sales-quoted based on fleet size, deployment shape, and support SLA. Our sales engineers can arrange a technical deep-dive call with your security and ops teams.
Or email direct: sales@netinsightpro.com
On-prem telemetry · Cloud digests only · Your keys, your storage
Only strictly-necessary cookies for login. No third-party tracking. Read our Cookie Policy or Privacy Policy.