Regions

Sahabti runs in one region today: Jordan East, in Amman, Jordan. Everything you create runs there, close to users across the Levant and the Gulf, and its data is stored there.

Where your workloads run

Apps, managed services, virtual machines, game servers, load balancers and Kubernetes clusters all run in Jordan East, and so do their disks and backups. With one region there is nothing to choose: the console fills it in, and the API uses jordan-east when a request leaves it out.

An instance keeps the region it was created in; it can't move to another one later.

Where you'll see it

• Instances: the Region on an instance's page, and the region field in the API.
• Kubernetes: every worker carries the labels topology.kubernetes.io/region: jordan-east and topology.kubernetes.io/zone: jordan-east-1. A node pool runs in one zone, and a volume stays in the zone it was created in.

Data that leaves the region

Your workloads and the data in them stay on our own infrastructure in Jordan. One feature sends text elsewhere, and only once you turn it on:

• PromptOps: when a workspace turns it on, its conversations and what PromptOps reads to answer them are processed in Singapore by its AI provider. Passwords, connection details, kubeconfigs and environment variables are never sent. See PromptOps.

Payments are handled by our merchant of record. The Privacy Policy lists every subprocessor and where it operates.

Coming regions

We plan to open regions across the Middle East and North Africa, starting with:

None has a date yet. Each will appear in the console, and in the changelog, once you can create resources in it. What you already run stays in Jordan East.

Need a region we haven't listed, or one sooner? Write to [email protected]: demand decides the order.