Your data. Your borders. Your rules.
Security architecture should respect where your data must reside and who is authorized to act.cor.xyz supports sovereign deployment models aligned with your security, regulatory and data-residency requirements. The platform can run on your premises, within your private or public cloud, in a local or sovereign cloud environment, or through the Coordinates cloud.Wherever cor.xyz is deployed, your data environment, permissions and response authority remain governed by the architecture and policies agreed with you.
- Coordinates Global Cloud
- Coordinates Sovereign Cloud
- Customer Cloud
- On-Premises
- Your data
Sovereignty is an architecture decision.
Where your data resides, who can process it and who can act within your environment are determined by the architecture, permissions and policies you define.
cor.xyz supports deployment on your premises, within your private or public cloud, in a local or sovereign cloud environment, or through the Coordinates cloud. Data processing, agent execution and response authority can therefore remain within the technical and jurisdictional boundaries your organization requires.
Choose where cor.xyz runs.
Coordinates Global Cloud
Global Coordinates-hosted deployment.
cor.xyz is hosted and operated in the Coordinates cloud for organizations that do not require a client-controlled deployment.
Sovereign / Local Cloud
In-country Coordinates-hosted deployment.
cor.xyz and the client security data environment can be deployed within an approved local or sovereign cloud to meet residency and jurisdictional requirements.
Customer Cloud
Your tenancy. Your controls.
cor.xyz runs within your private or public cloud tenancy, under the architecture, access controls and policies agreed with you.
On-Premises
Inside your environment.
cor.xyz is deployed within your own infrastructure for organizations requiring the platform and client security data to remain within a client-controlled environment.
| Aspect | Coordinates Global Cloud | Coordinates Sovereign Cloud | Customer Cloud | On-Premises |
|---|---|---|---|---|
| Where it runs | Coordinates global cloud environment | Coordinates cloud environment deployed within the required sovereign or in-country jurisdiction | Your private or public cloud tenancy | Your own infrastructure or data center |
| Whose controls | Coordinates | Coordinates | Customer | Customer |
| Suited to | Organizations without specific sovereign or in-country hosting requirements | Organizations requiring in-country, sovereign or jurisdiction-specific hosting | Organizations that want cor.xyz deployed inside their own cloud tenancy | Organizations requiring cor.xyz and client security data to remain within their own infrastructure |
Which components run where, and which data flows are allowed, is agreed for each deployment.
Your architecture defines what stays and what can move.
- Raw telemetry, logs, context and evidence: they stay inside
- Detection content: it crosses, and your context does not
- Your boundary
Data residency.
Client security data is processed and stored according to the deployment architecture and residency requirements agreed with you.
Controlled data flows.
The architecture, permissions and policies define which data may move between components and which must remain within the client environment.
Shared intelligence without shared data.
Generalized threat intelligence and approved detection improvements can strengthen protection across clients while each client’s telemetry, identities and security context remain segregated.
Local processing.
Where data cannot leave the environment, cor.xyz, the Client Security Data Model and agentic infrastructure can be deployed within the local or sovereign environment.
Response authority remains governed by you.
Sovereignty is not only about where your data resides. It also defines who is permitted to act within your environment.
Your response policy determines which actions may execute automatically, which require authorization, which may be delegated to Coordinates and which remain prohibited. Material actions stay within those boundaries, with approvals, execution and outcomes recorded for auditability.
Read how response policy worksDefine your sovereignty requirements.
We’ll map the architecture.
Tell us what must remain in-country, where data may be processed and who may authorize action. We’ll map the deployment model, component placement, permitted data flows and response boundaries around those requirements.