Regions
UAE me-central-1 is live today; Syria me-north-1 is next and Jordan me-east-1 follows in the 12-month regional expansion program.
A region is where your project physically runs. You pick it once, when you create the project, and it never changes afterwards. Every service in the project — container apps, managed databases, object storage, and AI — runs in that one region, because a project is a single private network on a single cluster.
To run workloads in another region, create a separate project there. A project can't be moved between regions after it exists; a "move" is really a new project in the new region.
Available regions
| Region | Code | Status | Currency |
|---|---|---|---|
| UAE | me-central-1 | Available | AED |
| Syria | me-north-1 | Coming soon | SYP |
| Jordan | me-east-1 | Coming soon | JOD |
me-central-1 (UAE) is live today and is pre-selected as the default. Syria is
the next planned physical region, followed by Jordan. The 12-month expansion
program is focused on that order, but neither region receives a promised opening
date before its infrastructure and launch gates are complete.
The code (for example me-central-1) is the stable identifier: it's what you
pass to the API and what shows up in your object-storage credentials, and it
never changes. The country name is how the region is labelled in the
dashboard.
Choosing a region
You choose the region in the project-creation step — the Cloud Studio wizard or the New project dialog. Only an available region can launch:
- Send an unknown or empty code to
POST /v1/projectsand you getBAD_REGION. - Send a real but coming-soon region and you get
REGION_UNAVAILABLE— the create is refused, not silently redirected. - Request a service that isn't offered in your region yet and you get
REGION_SERVICE_UNAVAILABLE.
Coming-soon regions and “Notify me”
Syria and Jordan appear in the region picker but can't be launched yet. Syria is the next planned region and Jordan follows. Choose Notify me to join the waitlist, and we'll let you know when it opens. Interest helps capacity planning but does not replace the launch-readiness gates or change a region's status.
Currency follows the region
Prices are shown in your region's currency for clarity — AED for UAE, SYP for Syria, JOD for Jordan. You can override the display currency in your account settings (for example, to see prices in USD).
The currency is display only. Your balance and every charge stay in USD credit, topped up with vouchers — nothing is ever charged in local currency. The local currency is there so the numbers read naturally for where you are, not to change what you pay.
Object storage and your region
A new object-storage bucket uses your region as its S3 region string — for
me-central-1, the region value is me-central-1. The endpoint stays
https://basin.alawadi.cloud. See the
Basin overview and
Connect an app to object storage for the full
setup.
Older credentials keep working
Credentials issued before the region was renamed show damm-1. That value is
a permanent alias for me-central-1, so any saved SDK config, rclone
remote, or aws profile keeps authenticating unchanged — you never have to
update it.
Which services are available where
Not every service is offered in every region at the same time. Today only
me-central-1 (UAE) offers services; Syria and Jordan are coming soon across the
board. The service catalog in the dashboard always reflects what's available in
your project's region, and the API returns REGION_SERVICE_UNAVAILABLE for a
service that isn't live there yet.