Feature: Multi-Region

Region-aware.

Multi-region capability

Nova AI Ops now operates as multi-region from a single tenant. Customer data and incident processing pinned to chosen regions; metadata replicated globally.

Two deployment models: replicated active-active across regions, or pinned active-passive with a designated primary. Customers pick based on their compliance and cost preferences.

Latency: per-region operation means dashboards and incident response operate at single-region latency. Cross-region only for explicit operations like global search.

Architecture

Per-region data plane: incident store, metric backend, configuration cache. Region-affinity for all customer-facing read and write paths.

Global control plane: tenant configuration, identity, billing. Replicated across regions for read; central writes flow through a primary.

Cross-region replication for customer data is opt-in. Customers in regulated industries can disable replication and accept reduced disaster recovery scope.

Compliance considerations

Data residency: customer data stays in chosen regions. Required for GDPR data subjects in the EU, and for some industry regulations.

Audit trail: per-region audit logs with cross-region aggregation for security teams. SOC2 Type 2 reports cover the multi-region story.

Encryption: per-region keys via customer-managed KMS. BYOK option for highest-sensitivity workloads.

Operating multi-region

Per-region status indicators in the customer dashboard. Customers see the health of their region and can identify if issues are region-specific.

Failover: in pinned mode, customers can manually invoke region failover. Automated failover available in replicated mode.

Cost: multi-region adds infrastructure cost. Available on enterprise tier; included in the per-host pricing for those tiers.

Rollout schedule

Q1 2026: us-east-1 and us-west-2 GA.

Q2 2026: eu-west-1 and ap-southeast-1 GA.

Q3 2026: additional regions on demand based on customer requests.