Data Regions

Neural Inverse Cloud launches in four regions, each on AWS. Accounts and sign-in are global. Resources live in the region where they are created and stay there. Neural Inverse Cloud is pre-release: only East US and Southeast Asia are running, on stage.

Regions

Region	Location	Address	Status
East US	Virginia, United States	cloud.neuralinverse.com	Preview
Southeast Asia	Singapore	sea.cloud.neuralinverse.com	Preview
Europe	Frankfurt, Germany	eu.cloud.neuralinverse.com	Planned
Japan	Tokyo, Japan	jp.cloud.neuralinverse.com	Planned

Europe is Frankfurt, Germany. Frankfurt and Tokyo are planned and are not available yet.

What is global and what is regional

Global: the account, users, roles, sign-in, Organizations and billing. This is identity metadata such as email and name.
Regional: workspaces, sandboxes, agents, skills, context, secrets, logs and the audit of regional actions. Content never leaves its region.

Controlling regions

Opt-in regions: East US is on for every account. An Owner or Admin turns on the others, and the change is audited.
Residency as policy: an organization policy can restrict every account to one region, for example Frankfurt only.
Recommended region: the server recommends a region based on where the visitor is.

Dedicated and self-hosted deployments

Dedicated cells and self-hosted deployments, including air-gapped, can run their own identity and data in a single jurisdiction, so users, sign-in and audit never leave it. Talk to us at sales@neuralinverse.com. See Neural Inverse for enterprise.

Contact

For questions about data regions, contact security@neuralinverse.com.

Was this page helpful?