Regions and availability

npayload operates across six regions worldwide, giving you control over where your data lives and how it moves.

Available regions

Choosing a region

Select a region based on three factors:

1. Latency: Choose the region closest to your users or services for the lowest round-trip time.
2. Compliance: Regulations like GDPR may require data to remain within specific jurisdictions. EU West and EU Central keep data within the European Union.
3. Data residency: Some organisations require data to stay in a specific country or region. npayload guarantees that messages remain in your selected region unless you opt in to cross-region messaging.

Region-specific endpoints

Each region has a dedicated API endpoint:

Configure your SDK to use the appropriate endpoint:

import { NPayload } from '@npayload/node';

const npayload = new NPayload({
  clientId: process.env.NPAYLOAD_CLIENT_ID,
  clientSecret: process.env.NPAYLOAD_CLIENT_SECRET,
  region: 'eu-west-1',
});

Data residency

By default, all messages, metadata, and audit logs remain in the region where your instance is deployed. npayload does not move data between regions unless you explicitly enable cross-region messaging.

This guarantee applies to:

• Message payloads and metadata
• Channel configuration
• Subscription state
• DLQ entries
• Audit logs

Cross-region messaging

npayload supports cross-region channels for use cases that require it, such as global event distribution or multi-region architectures. Cross-region messaging is always opt-in.

To enable cross-region messaging:

1. An organisation admin grants data residency consent in the dashboard
2. Create a channel with cross-region replication enabled
3. Select the target regions for replication

Consent is granular. You can allow replication between specific regions (for example, US East to US West) without opening all regions.

High availability

Each region is deployed across multiple availability zones for resilience:

• Automatic failover: If one availability zone becomes unavailable, traffic is routed to healthy zones with no manual intervention
• No single point of failure: Database, compute, and networking are distributed across zones
• Continuous health checks: Automated monitoring detects and responds to failures within seconds
• Target uptime: 99.99% for Enterprise tier, 99.9% for Pro tier

Latency expectations

Typical API response times measured from within the same region:

Cross-region operations add the network round-trip between regions (typically 50 to 200 ms depending on distance).

Next steps

• Security for encryption, authentication, and network isolation
• Compliance for GDPR, SOC 2, and data protection details
• Limits and quotas for per-region resource limits