Deployment, Architecture, and Data Residency
Nevis ID runs as SaaS on Microsoft Azure with a dedicated instance per customer: its own Azure resource group, Kubernetes cluster, and PostgreSQL database. The analytics layer is shared across instances in the same Azure region, isolated by filtering. Data residency is a first-class choice: dedicated regions include Switzerland, Germany, France, the EU, the UK, US East and West, and Southeast Asia, with additional regions on request subject to Azure capacity in that region, and data at rest, including logs and backups, stays in the selected region; operational telemetry used to measure service-level objectives is processed outside it and carries no personal data. The platform scales from thousands to millions of users through vertical and horizontal scaling per instance, distributes services across multiple independent data centers, and deploys platform and configuration changes without downtime for end users; availability targets and recovery objectives are defined in the contractual agreement, and incidents are communicated on the public status page. Nevis is ISO 27001 and SOC 2 Type II certified and operates under GDPR, CCPA, and Swiss data protection law, with regular external penetration tests whose reports are available on request.
Also known as
platform and architecture, SaaS deployment model, hosting and availability, tenancy options, data localization, data sovereignty, data residency, scalability, certifications.
At a glance
| Capability | Details |
|---|---|
| Deployment model | Dedicated instance per customer: own Azure resource group, Kubernetes cluster, and PostgreSQL database. The analytics layer (Databricks) is shared per Azure region, isolated by filtering |
| Regions and data residency | Switzerland, Germany, France, the EU, the UK, US East and West, Southeast Asia; additional regions on request, subject to Azure capacity; data at rest, including logs and backups, stays in the selected region; operational telemetry for service-level objectives is processed outside it, with no personal data |
| Environments | TEST and LIVE environments included per instance; parametrized promotion of configuration between them |
| Availability | Services distributed across multiple independent data centers; WAF and DDoS protection at the edge; incidents communicated at status.nevis.net; availability targets are defined in the contractual agreement |
| Backup and disaster recovery | Encrypted, geo-redundant backups in a separate region; automatic in-region failover; standard and premium disaster recovery tiers; recovery objectives are defined in the contractual agreement; recovery procedures are tested regularly |
| Updates | Platform components and configuration deploy without downtime for end users; the management console can be briefly unavailable during its own updates, and infrastructure maintenance occasionally needs a short window; the customer controls the upgrade schedule with side-by-side testing; configuration changes are audited and instantly reversible |
| Encryption | TLS 1.2 or newer in transit and FIPS 140-2 validated AES-256 at rest, always on; quantum-resistant TLS (TLS 1.3 with ML-KEM) at the edge; automated certificate lifecycle; signing keys backed by Azure Key Vault |
| Certifications and compliance | ISO 27001, SOC 2 Type II; OpenID Connect certified, FIDO certified; GDPR, CCPA, Swiss data protection law; regular external penetration tests with reports on request |
| Data protection operations | Privacy by design and data minimization; DSAR assistance; documented subprocessors with scope and processing locations, available on request; secure data return or destruction on termination |
| Scalability | From thousands to millions of users; vertical and horizontal scaling configured per environment through performance profiles |
| Tenant isolation | Dedicated clusters as the isolation boundary; see also Multi-tenancy and Delegated Administration |
Concepts
- System overview: the architecture of a Nevis ID instance: components, network topology, endpoints, and environments
- Deployment and isolation: the deployment model in brief on the Introduction page
How-to Guides
- Console overview: the management surface of an instance; deployment and infrastructure themselves are operated by Nevis
References
- Changelog: the release history of the platform
- Service status: incident communication
- Microsoft Azure physical security: the data-center layer Nevis ID inherits