Regions
BangmodStorage runs two regions today, each backed by an independent Ceph cluster in the corresponding country. Data does not move between regions without your explicit action.
Region matrix
| Region | Code | Endpoint | Supplier | Default currency |
|---|---|---|---|---|
| Bangkok | ap-southeast-1-bkk | s3.bkk.bangmod.storage | Bangmod Enterprise Co., Ltd. (TH) | THB |
| Singapore | ap-southeast-1-sg | s3.sg.bangmod.storage | BangmodStorage (Singapore) Pte Ltd | USD |
Choosing a region
Pick the region closest to your application or your users. Latency between Bangkok and Singapore is typically 20–35 ms.
- Thai customers / TH workloads: Bangkok. THB billing, TH RD-compliant tax invoices, 50-tawi withholding-tax handling.
- Most other Asia-Pacific: Singapore. USD billing, SG GST treatment.
- Multi-region workloads: create buckets in both. You will receive one invoice per region per billing period.
Cross-region behaviour
- Access keys are region-scoped. A Bangkok-issued key cannot sign requests against the Singapore endpoint; you will get
BGSRegionMismatch. - Object versions, lifecycle rules, and bucket policies are local to the bucket's region.
- Cross-region replication is on the roadmap; not available today.
- Customer billing is per-region per-supplier — a customer using both regions receives separate invoices from the Thai and Singapore entities.
Future regions
Additional regions are evaluated by customer demand. If a specific country or compliance regime is blocking your migration, email roadmap@bangmod.storage with your use case and expected volume.
Region health
Live operational status at /status.