Cloud Strategy

The Cloud Service Provider Journey in the Bangladesh Context

How a sovereign cloud business is shaped by BTRC licensing, BDT billing, BDIX peering, and a customer base that still treats colocation as the default.

Mahbub Hossain
·

Why does Bangladesh need a sovereign cloud when hyperscalers offer credit-card billing in a hundred regions? The answer is regulation, currency, and peering — none of which a global control plane was built around.

~190M
Mobile subscribers
BTRC quarterly stats
BDIX
Internet exchange since 2004
Peers most domestic ISPs
Tier-III
Floor for licensed CSP DCs
BTRC annexes
BDT
Practical B2B billing currency
USD invoices flag at the CFO

Where hyperscaler defaults break

On-demand compute, monthly billing, credit cards, public-internet delivery — each runs into friction. Procurement settles in BDT via EFT or L/C; transit to Singapore exceeds 250 ms; international bandwidth costs 4–8× a BDIX peer.

How Bangladeshi enterprises actually pay infrastructure invoices
Bank transfer (EFT) BDT, 30/60-day terms
62 %
Cheque on delivery Often paired with PO
18 %
Letter of credit Larger annual deals
12 %
Corporate credit card Almost always SaaS
6 %
Other
2 %

Source: Indicative distribution from Cloud Digit's enterprise pipeline.

Two structural moats

What a sovereign provider holds that a hyperscaler region cannot
1
BTRC Cloud Service Provider license Regulatory

Tier-III sites · in-country control plane · key-personnel attestation · annual audit

2
BDIX peering across all major ISPs Network

RTT collapses from ~280 ms (SG) to <50 ms · 4–8× cheaper per Mbps

3
BDT-denominated billing & contracting Commercial

No FX volatility on the customer P&L · matches procurement workflow