iShield Resource Library, Trust & Commercial · Deployment & Data Residency FAQ
SaaS, Hybrid, or On-Prem — pinned to the region you require
One codebase. Three deployment models. Region pinning at tenant, workflow and AI-route level. Get the answers compliance, security and architecture teams ask before shortlisting.
Three ways to deploy. Zero functional drift.
Same product, same APIs, same upgrade path. Choose the operating model that fits your governance — not a fork of the codebase.
Fastest time-to-value, no infra to operate, standard enterprise compliance.
- Control plane
- iShield cloud
- Data plane
- iShield cloud (pinned region)
- Residency
- EU, US, UK, GCC, APAC — chosen at tenant creation
- Identity
- SAML 2.0, OIDC, SCIM 2.0, MFA, just-in-time provisioning
- BYOK / HYOK
- BYOK via AWS KMS / Azure Key Vault / GCP KMS
- Updates
- Continuous, zero-downtime
- Air-gapped
- Not applicable
Regulated industries, data sovereignty, cloud-of-record workloads.
- Control plane
- iShield cloud (orchestration, UI, metadata)
- Data plane
- Customer VPC on AWS, Azure, GCP or OCI
- Residency
- Any region the customer cloud offers; per-flow pinning supported
- Identity
- Federated SSO to customer IdP, optional private OIDC
- BYOK / HYOK
- Customer-managed CMK; iShield never holds plaintext data keys
- Updates
- Customer-approved windows, blue/green
- Air-gapped
- Not applicable
Defense, intelligence, critical national infrastructure, no-internet environments.
- Control plane
- Customer datacenter (Kubernetes / OpenShift)
- Data plane
- Customer datacenter, same cluster or segregated
- Residency
- 100% on customer premises — no data leaves the facility
- Identity
- Active Directory, LDAP, PIV/CAC, FIDO2 hardware keys
- BYOK / HYOK
- HSM-backed (Thales, Entrust, AWS CloudHSM)
- Updates
- Offline bundle, signed artifacts, customer-controlled
- Air-gapped
- Supported
SaaS vs Hybrid vs On-Prem at a glance
The decisions that drive procurement and architecture review.
| Dimension | Managed SaaS | Hybrid | On-Prem & Air-Gapped |
|---|---|---|---|
| Best for | Fastest time-to-value, no infra to operate, standard enterprise compliance. | Regulated industries, data sovereignty, cloud-of-record workloads. | Defense, intelligence, critical national infrastructure, no-internet environments. |
| Control plane location | iShield cloud | iShield cloud (orchestration, UI, metadata) | Customer datacenter (Kubernetes / OpenShift) |
| Data plane location | iShield cloud (pinned region) | Customer VPC on AWS, Azure, GCP or OCI | Customer datacenter, same cluster or segregated |
| Tenant isolation | Logical tenant isolation, per-tenant keys, quotas, audit | Single-tenant data plane, customer-owned subnets and keys | Dedicated cluster, no shared services, hardware-rooted trust optional |
| Network model | TLS 1.3 in transit, AES-256 at rest, public endpoints + IP allow-listing | Private link / VPC peering, no public data egress, customer-managed firewall | Fully disconnected supported; no outbound calls required |
| Residency control | EU, US, UK, GCC, APAC — chosen at tenant creation | Any region the customer cloud offers; per-flow pinning supported | 100% on customer premises — no data leaves the facility |
| Identity & SSO | SAML 2.0, OIDC, SCIM 2.0, MFA, just-in-time provisioning | Federated SSO to customer IdP, optional private OIDC | Active Directory, LDAP, PIV/CAC, FIDO2 hardware keys |
| Key management | BYOK via AWS KMS / Azure Key Vault / GCP KMS | Customer-managed CMK; iShield never holds plaintext data keys | HSM-backed (Thales, Entrust, AWS CloudHSM) |
| Observability | Tenant-scoped metrics, audit log streaming to SIEM | Logs, metrics and traces stream to customer SIEM/APM | Local Prometheus / Grafana / OpenSearch, optional export |
| Upgrade cadence | Weekly minor, monthly feature, quarterly major | Customer-scheduled, max 90-day version drift | Customer-controlled, LTS releases supported 24 months |
| Air-gapped support | No | No | Yes |
Pin tenants, workflows and AI routes to a specific region
Residency is enforced at storage, processing and inference layers — not just at the storage bucket.
GDPR, Schrems II compliant, EU-only operators
FedRAMP Moderate-ready, ITAR-aware deployments
UK GDPR, NCSC Cloud Security Principles
SDAIA, NCA ECC, UAE IA, in-country operators
MAS TRM, APRA CPS 234, India DPDP
Customer-defined; iShield deploys to it
Object store, database and search index physically reside in the chosen region. No cross-region replication unless explicitly enabled.
Workflow engine and integration runners are scheduled only to nodes in the pinned region. Audit log includes execution region.
Inference requests are routed only to model endpoints in the pinned region. EU tenants never hit US inference, by policy and by route.
The questions security, compliance and architecture ask
