Basin overview
S3-compatible object storage in the live UAE region for backup files, media, static assets, and app data, with explicit current durability limits.
Basin is alawadi.cloud's S3-compatible object storage.
One S3-compatible service
Basin stores and serves files: backups, images and video, static website assets, and application data, over the same S3 API your tools already speak. Point any S3 client or SDK at our endpoint, use the credentials you create in the dashboard, and pay only for the capacity you book, prepaid from the same voucher-funded balance that pays for your apps. Vouchers are the only live funding rail today; card and USDT top-ups remain coming soon.
Endpoint and region
| Setting | Value |
|---|---|
| Endpoint | https://basin.alawadi.cloud |
| Region | me-central-1 |
| Addressing | Path-style only |
All object storage lives in the live me-central-1 UAE region, on servers we
own and operate. Syria is the next planned region and Jordan follows; neither
coming-soon region stores customer objects today. Credentials issued before the
region rename show damm-1; it is a permanent alias for me-central-1, so any
saved SDK config keeps working unchanged.
Path-style addressing
Our endpoint uses path-style addressing
(https://basin.alawadi.cloud/BUCKET/KEY), not virtual-hosted-style. Every S3
SDK and CLI supports it: you set one option (forcePathStyle,
s3ForcePathStyle, or addressing_style=path). The
quickstart shows the exact setting for each tool.
Current durability boundary
Basin's live object data is not currently covered by a customer-facing multi-server replication or point-in-time recovery commitment. A bucket must not be treated as the only copy of critical data. Keep an independent copy in another system or region and test your restore process. We will update this page only after additional durability controls are deployed and verified.
Buckets are private by default. There are no public or anonymous buckets: every read and write requires your credentials, and those credentials reach your buckets only.
What it is good for
- Backup files: database dumps, app snapshots, and archives, pushed and
pulled with any S3 tool or
rclone— while retaining another independent copy for critical material. - Media: user uploads, images, audio, and video your app serves.
- Static assets: build artifacts, downloads, and files your site links to.
- App data: anything your service reads and writes as objects, from one region, over HTTP.
How it fits together
- Buckets: create them in the dashboard with a name, a capacity in GB, and optional versioning; see buckets.
- Access keys: an access key and secret, scoped to your buckets, shown once; see access keys.
- Billing: $0.04 per GB-month on booked capacity, egress free, metered hourly from your balance; see billing.
- Limits: per-object upload size, capacity behavior, and the S3 error codes you will see; see limits and errors.
Quickstart
Create a bucket and upload your first object with the aws CLI, rclone, or mc.
Buckets
Naming, capacity and quota, versioning, and permanent-delete semantics.
Access keys
Shown-once keys, scoped to your buckets, regenerated on demand.
Billing
What a GB-month costs, with a worked example.
Buckets API
Create, resize, delete, rotate keys, and attach a bucket to an app over the API.
Estimate your monthly cost with the pricing calculator on the landing page, or open Cloud Studio and pick Basin to create your first bucket.