Dedicated, sovereign, OEM. Built for fleets that can't run on shared infrastructure.
Enterprise capabilities are a design and private-pilot program. No certification, residency commitment, SLA, named support entitlement, or signed legal package is offered unless it is explicitly included in an executed customer agreement.
Tenant-only LockiaMQ + Postgres + KMS bridge. Operators in your namespace, no neighbor noise.
A contract option that requires a validated deployment topology and explicit residency terms before activation.
A design option requiring implementation, security validation, and an executed agreement; it is not generally available.
Bundle Lockia with your hardware or carrier offering. Private APN, custom device agent, OEM-branded SDK.
Key custody is designed behind a provider trait so your KMS or HSM can hold the wrap keys. On the roadmap — no KMS/HSM provider is shipped yet, and we'll say so until it is.
Encryption, retention, incident response, and availability terms require counsel and operational approval before they are offered.
Protocol v2 implements signed lifecycle acknowledgements and atomic server state. Physical-device and production-failover evidence remain launch gates.
Named support, escalation, and availability commitments are negotiated only after the operating model is proven.