Model A
Air-gapped
No egress. Signed offline update bundles, local identity, local telemetry retention.
Typical: defence, critical national infrastructure
On-premise & security
Where a system runs determines who can reach it, which laws apply to it, and what happens when connectivity or a supplier fails. We design for the strictest of those answers first, then relax deliberately.
Model A
No egress. Signed offline update bundles, local identity, local telemetry retention.
Typical: defence, critical national infrastructure
Model B
Runs in your data centre with controlled outbound paths for updates and support.
Typical: banking, public sector
Model C
Your subscription, your region, your keys — deployed and operated by us if you prefer.
Typical: healthcare, scale-ups
Model D
Regulated data stays inside; elastic compute and non-sensitive workloads run outside.
Typical: energy, telecommunications
We build to the evidence your auditors ask for and work alongside your compliance function. Certification remains yours; our job is to make it achievable. The frameworks below are ones we design evidence for — not certifications ElixTechs holds.
Performance
On-premise means fixed hardware, so efficiency is not optional. Each engagement sets a small number of budgets and reports against them every release.
Budget type
Read path latency, P95 and P99
Budget type
Sustained ingest throughput per node
Budget type
Memory and storage ceiling per tenant
Budget type
Recovery time and recovery point objectives
Contact
Send a short description of the system, the environment it must run in, and the obligations attached to it. An engineer replies — usually within one working day. We reply in English or Arabic.
[email protected]