Cloud for Banks, Government & Enterprise in Bangladesh

What this page is, and what it will not invent

This is the industry map for TiCON’s AWS work in Bangladesh. It is not a client-logo wall, a certificate list, or a gazette of circulars.

On AWS, TiCON is an Advanced Tier Partner you can check on AWS Partner Solutions Finder, and it resells usage on a taka invoice. Those two facts are sourced. They apply to the industry estates on this page when the workload is on AWS. They do not transfer to Azure or Google Cloud because a bank or a broadcaster also runs Microsoft 365 or BigQuery. Multi-cloud is allowed when there is a reason. Two identity systems and two undocumented regions is how regulated estates fail an audit.

The five public case studies on this site use descriptor titles: a private bank billed in taka, a government broadcaster with a sovereignty brief, a telecom data platform, national-scale OTT on BlessBit, and e-commerce peak-traffic scaling. Legal names of those organisations are omitted until they are cleared to be named. A previous version of this page listed names. That list is not restated.

Staff certification lists, ISO or other company certificates, PCI-DSS certificates, numeric SLA minutes, sample taka bills, and ping times are not published here. Empty in the facts file means unpublished, not implied. The residency page is the place to discuss what Bangladesh’s rules mean for cloud; even there, circular numbers wait on a sourced list rather than being guessed.

• AWS partner and reseller
• Data residency in Bangladesh
• Pay AWS in taka

Banking

Bangladesh Bank is the sector regulator for banks. This page does not restate circular numbers. The architecture pattern is a governed AWS landing zone, a taka invoice for usage, and an audit pack that names the region and the controls before cutover.

A typical bank estate we will actually design is not “lift the core onto a bigger VM.” It is an organisation-and-account structure (Control Tower or the equivalent landing-zone pattern), IAM that an auditor can follow, logging, encryption, and a written answer to where the bits sit. The usual AWS regions from Bangladesh are Asia Pacific (Mumbai) and Asia Pacific (Singapore). There is no AWS region in Bangladesh. Hybrid is allowed: some categories stay in-country on a local data centre or a custom CDN; the rest run in the named region. The split is documented, not implied.

Billing matters as much as the landing zone. A bank that cannot file a local invoice does not finish the project. AWS usage on a TiCON reseller engagement is invoiced in taka. Azure or Google Cloud, if they are already in the building for identity or analytics, stay on their own paper. This page does not invent an Azure-in-taka or GCP-in-taka reseller product so that a bank can have one vendor for every logo.

The published write-up for this shape of work is the private-bank case study. It uses a descriptor title, not a legal name. Read that page for the billing and landing-zone story; do not treat a homepage logo wall as the same evidence.

• ✓Regulator note: Bangladesh Bank. Circular numbers are not restated here.
• ✓Architecture pattern: landing zone, IAM, logging, encryption, named region, taka invoice, audit pack.
• ✓Residency stance: document the region; hybrid in-country for categories that must stay.

• Private bank — AWS billed in taka
• Data residency in Bangladesh
• Managed cloud & FinOps

Fintech

Fintech and payments sit under the same financial-sector umbrella as banks. This page does not invent a separate named-client case study, and it does not claim a PCI-DSS certificate.

The architecture pattern is the bank landing zone plus a cardholder-data boundary. Wallets, issuing, acquiring, KYC and fraud analytics need identity, encryption, audit logs and a written map of which systems may hold primary account numbers. PCI DSS is a card-industry standard that exists. Building toward those controls is architecture work. This page does not claim a PCI-DSS certificate. The facts file has no certificate list, so none is claimed.

Regulator notes stay at the institution level: Bangladesh Bank for financial services; other licences are the customer’s to name. Circular numbers, e-money notices and card-limit figures are not restated here. Tax treatment of cloud invoices is also omitted — that is a finance input, not a slogan.

No fintech-titled case study is published. The nearest public write-up is the private-bank case study, because the landing zone, taka invoice and audit pack are the same shape of work. If the workload is analytics-heavy on Google Cloud, that is operations on BigQuery, not a GCP taka reseller invoice.

• ✓Regulator note: financial-sector umbrella. Circular numbers and card limits are not restated.
• ✓Architecture pattern: bank landing zone plus a documented cardholder-data boundary.
• ✓This page does not claim a PCI-DSS certificate.

• Private bank — AWS billed in taka
• Data residency in Bangladesh
• Google Cloud in Bangladesh

Government

Public-sector and broadcast workloads need a documented residency and sovereignty choice. This page does not restate ICT Division circular numbers, gazette IDs, or a “cloud-first” circular as if it had been checked this week.

The architecture pattern is a landing zone the auditor can follow, identity that is not a shared admin login, logging, and a written region. Citizen-scale apps and national broadcast are different products on the same foundation: the app needs elasticity; the broadcaster needs origin, CDN and a sovereignty story for the content that must not leave the country. TiCON’s custom CDN inside local data centres is the in-country content path already described on the company pages. AWS remains Mumbai or Singapore for the part that runs in region.

A badge that says “sovereign” is not a control. The control is the document: which data categories, which region or local path, who can reach them, and how that is evidenced. Azure is a usual shortlist when Entra ID and Microsoft 365 are already in the ministry. That does not make TiCON an Azure taka reseller, and it does not invent a Microsoft designation on this page.

The published write-up is the government-broadcaster case study, under a descriptor title. It is the sovereignty-shaped story on this site. Other public-sector work is not listed by legal name here.

• ✓Regulator note: public-sector and broadcast. Circular numbers are not restated here.
• ✓Architecture pattern: landing zone, identity, logging, named region, local CDN where content must stay.
• ✓Residency stance: write the split down before cutover.

• Government broadcaster — cloud sovereignty
• Data residency in Bangladesh
• Microsoft Azure in Bangladesh

Telecom

The Bangladesh Telecommunication Regulatory Commission is the sector regulator for telecom. This page does not restate BTRC circular numbers. The architecture pattern is a data platform the business can actually query, not a slide labelled “data lake.”

A typical telecom engagement we will take is ingestion, a warehouse or lakehouse, BI for internal consumers, and IAM so that “everyone with a VPN” is not the access model. Billing systems and network telemetry are in scope only when they are written into the statement of work. High throughput is an engineering problem; it is not a reason to invent ping times or a concurrency prize on this page.

AWS is the usual substrate when the estate can be invoiced in taka and the platform team already speaks IAM and S3. Google Cloud is the usual alternative when the centre of gravity is BigQuery. Choose one centre of gravity. Copying the same telemetry into two clouds “for flexibility” is how the bill grows without a better answer for the regulator.

The published write-up is the telecom data-platform and BI case study, under a descriptor title. It is not a named operator, and it is not a licence filing.

• ✓Regulator note: BTRC. Circular numbers are not restated here.
• ✓Architecture pattern: ingestion, warehouse, BI, IAM for many internal consumers.
• ✓Residency stance: document region and who can query; do not invent a local-region promise.

• Telecom data platform & BI
• Google Cloud in Bangladesh
• Cloud migration (6 R’s)

Media & OTT

OTT and broadcast are origin, CDN, packaging and a playback engine that survives a national audience. TiCON builds BlessBit, its own OTT streaming engine. CloudFront on a reseller engagement carries the published bandwidth saving of up to 40 percent. Ping times are not published.

The architecture pattern is origin in a named AWS region (Mumbai or Singapore), CloudFront for the internet-facing bytes, BlessBit for the streaming application, and a local CDN path when content sovereignty requires bits to stay in-country. Live events and on-demand catalogues are different load shapes; both need autoscaling origin and a cache that does not collapse when a match or a serial drops. Seasonal Bengali calendar peaks (Eid, Pohela Boishakh) are real traffic events. Millisecond figures from Dhaka to the region are not restated here.

Some OTT licences sit under telecom or information-ministry overlays. This page does not restate those circulars. What we will write down is the region, the cache behaviour, and who can publish. A previous version of this page named platforms. Those names are not restated. The public write-up is the national-scale OTT case study, titled as a descriptor, with BlessBit as TiCON’s engine — not as a client brand.

CloudFront’s “up to 40 percent” figure is the AWS reseller bandwidth range in the facts file. It is not a promise that every OTT bill falls by that amount, and it is not applied to Azure Front Door or Cloud CDN as if those were the same product.

• ✓Regulator note: media and, where it applies, telecom overlay. Circular numbers are not restated.
• ✓Architecture pattern: named-region origin, CloudFront, BlessBit, local CDN for sovereignty.
• ✓Published case study uses a descriptor title, not a platform name.

• National-scale OTT streaming
• OTT on AWS from Bangladesh
• CloudFront pricing from Bangladesh
• AWS partner and reseller
• Cloud hosting in Bangladesh

E-commerce

E-commerce is elastic compute, a managed database, and a CDN that absorbs campaign and calendar spikes. Checkout staying up is the product. A public SKU table is not.

The architecture pattern is autoscaling application tiers, a managed database, object storage for media, and CloudFront in front. Eid, Pohela Boishakh and campaign drops are the load tests that matter in Bangladesh. This page does not publish a taka-per-month plan table; hosting is quote-based, and the BDT calculator is an estimate, not an invoice. Buying a server is a different intent from learning how hosting works — use the buy page to order, the hosting page to learn.

If the store takes cards, the cardholder-data boundary from the fintech section applies. This page still does not claim a PCI-DSS certificate. If the catalogue is only a storefront with a third-party payment redirect, say so in the architecture so that the audit pack does not pretend the shop holds primary account numbers it never sees.

The published write-up is the e-commerce peak-traffic case study, under a descriptor title. It is the spike-shaped story on this site. Client legal names are omitted.

• ✓Regulator note: payments overlay only if you take cards. No certificate claimed here.
• ✓Architecture pattern: autoscaling compute, managed database, CloudFront, quote-based hosting.
• ✓Peak calendar: Eid, Pohela Boishakh, campaigns — without invented concurrency prizes.

• E-commerce peak-traffic scaling
• Cloud hosting (learn)
• Buy a cloud server (order)

Industry map — pattern, residency, case study

One row per sector. Descriptor titles only. Circular numbers omitted.

• AWS vs Azure vs Google Cloud
• All case studies

How we start an industry engagement

The first meeting is a briefing, not a circular lecture and not a logo review. Bring the sector, the data categories, and who you answer to. We will not invent a gazette number you did not bring.

• Talk to an architect (contact)
• Cloud migration (6 R’s)