Deployment inside your boundary
The software installs as a hardened container package on your servers — on-premises, in your private cloud, or fully air-gapped. There is no vendor cloud behind it and no account with mAIb Tech: inference, storage and audit all run inside your network.
Zero egress by design
Raw enterprise data egress is zero by design. In on-premises and air-gapped deployments this is enforceable at your network boundary — the strongest control available, because it is your control.
No telemetry
The product does not phone home. Updates and licences can transfer offline as signed, verifiable files for air-gapped sites.
Data residency
Because data never leaves your environment, residency follows your infrastructure decisions, not ours.
Known limitations, stated plainly
- Zero egress is an architectural design property, verified at your boundary — not a third-party-audited guarantee.
- Connected (non-air-gapped) deployments use a signed update path; the update channel is documented for your review.
These are architecture and control descriptions, not audit results. Current assurance status — implemented, tested, planned — is summarised in the Security & Trust Centre, and deeper material is available through the security architecture pack.