TiCON Cloud (TICON System Limited) designs, migrates and operates Google Cloud Platform for companies in Bangladesh. The work is architecture and operations: data platforms on BigQuery, machine-learning products on Vertex AI, containers on GKE or Cloud Run, and the IAM and networking that keep those services from becoming a second, unmanaged estate. This is not an AWS reseller page with the logo swapped. Google Cloud usage is billed on whatever paper the Google agreement produces. A badge on this site is not a Partner Advantage or Partner Network tier — Google’s Partner Finder is the record.
Last updated 21 September 2026
TiCON architects, migrates and runs Google Cloud in Bangladesh. That sentence is the whole commercial claim this page is allowed to make. It does not include a taka reseller invoice for GCP usage, a Google Workspace licence table, or a Partner Network designation copied from a brochure.
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 do not transfer to Google Cloud because the logo is in the same mega-menu. On GCP, the engagement is design, migration and operations. The Google bill stays a Google bill unless a separate Google or partner programme — written in a contract, not invented here — changes the paper.
That split is useful. A Bangladeshi product team can keep the application on AWS (and pay that usage in taka) while the warehouse or the ML product lives on Google Cloud because BigQuery or Vertex AI is the product, not a side experiment. Multi-cloud is allowed when there is a reason. Two identity systems and two bills without a reason is how estates get expensive and unauditable.
Staff certification lists are not published here. Numeric SLA minutes live in the managed-services contract, not on this page. Committed-use discounts exist as a Google pricing mechanism; this page does not quote a percentage saving on GCP to match the AWS 15–35% / CloudFront-up-to-40% ranges, because those ranges are AWS reseller facts, not Google list-price facts.
Google Cloud does not operate a region in Bangladesh. Traffic from Dhaka lands in India or Singapore. This page does not publish ping times; those need a dated measurement from a Bangladeshi ISP.
Compute Engine’s nearby regions, checked on Google’s public regions-and-zones page on 21 September 2026, include asia-south1 (Mumbai), asia-south2 (Delhi) and asia-southeast1 (Jurong West, Singapore). Other Google Cloud products may add locations later; announced is not the same as live, so the table below uses the regions Google already lists.
For a regulator who asks where the bits sit, the honest answer is India or Singapore, then a document that names the region, the services in scope, and who can reach them. This page does not restate Bangladesh Bank circular numbers.
| Topic | On this page | Not on this page |
|---|---|---|
| Region in Bangladesh | No | A local-region promise, a Local Zone, or a ping-time winner |
| Nearest published regions | asia-south1 Mumbai; asia-south2 Delhi; asia-southeast1 Singapore | Millisecond figures from Dhaka |
| TiCON’s commercial path | Architecture, migration and operations, quoted in taka for that work | A GCP-in-taka reseller invoice, or bKash as a Google payment rail |
| Partner record | Google Cloud Partner Finder is the directory. This page does not invent a Partner Advantage or Partner Network tier for TiCON | A screenshot of a badge, or a competitor’s tier copied from a brochure |
| Pricing | Quote after discovery. Google committed-use discounts exist; they are not restated as a TiCON percentage here | A public SKU table, or the AWS 15–35% range applied to GCP |
Region names are from Google’s Compute Engine regions and zones page, accessed 21 Sep 2026. Ping times and a taka-per-month winner are omitted.
Source: Google Cloud — Compute Engine regions and zones (opens in a new tab) Checked
Start from the workload. Google publishes BigQuery and Vertex AI as strengths of the platform. AWS and Azure both have capable data and ML stacks. Pick the product you will actually run, then put it in a nearby region.
A serverless warehouse when the question is analytics at warehouse scale, not a VM you have to patch. Streaming ingest, scheduled queries, and BI that sits on top of the same tables. Looker is Google’s BI product; this page does not claim a Looker partnership.
Train, tune and serve models, including generative-AI workloads, when the ML product is the product. TiCON already runs production ML on Vertex AI as well as SageMaker. Model choice and region still have to be written down for the auditor.
Managed Kubernetes and serverless containers when the app belongs on Google Cloud, not only the warehouse. GKE Autopilot and Cloud Run are Google products; they are not a reason to invent a hybrid-mesh product name on this page.
Deploying and administering Workspace (Gmail, Drive, Meet) for a team in Bangladesh is operations work. It is not a Workspace reseller price list, and it is not a substitute for the Google Cloud project that holds BigQuery.
A badge on a company website is self-published. Google keeps a public Partner Finder. Google has also described a Partner Network programme sitting alongside Partner Advantage levels in that directory. Use the directory. This page does not publish a TiCON tier from it.
Check a Google Cloud partner on Partner Finder
About 5 minutes
Use Google’s directory, not a screenshot on this site, as the source for partner status.
Open Google Cloud Partner Finder
Go to cloud.google.com/find-a-partner/ (the URL is in the sources below). That is the public directory Google currently points buyers to.
Search the legal name, not only the trading name
Search TICON System Limited as well as TiCON Cloud. A trading-name miss is not evidence the company is unlisted, and a homepage badge is not evidence that it is listed.
Read the level from the listing, if there is one
If a listing exists, the directory is the record for Partner Advantage levels and any specialisations Google currently shows. If no listing exists, this page still does not invent one.
Match the legal entity to the contract
The company that will design or operate your project should be the company on the listing and on the statement of work. Ask for that match in writing.
Re-check before you renew
Partner programmes are reviewed and have been renamed. Repeat the check when the contract renews, not only at first signature.
Moving a warehouse or an ML product onto GCP is still a migration: inventory, a TCO model, a wave plan, a rollback. The 6 R’s still apply. MAP co-funding is an AWS programme; this page does not invent a Google equivalent amount.
A typical split we will actually recommend is AWS for the application and Google Cloud for BigQuery or Vertex AI. The other way around is allowed when the product is already on GCP. What we will refuse is a fashion multi-cloud: every new service on a third logo because a conference slide said so.
After cutover, operations are the same job as on AWS — monitoring, IAM hygiene, backups, a named person who answers — with the Google bill remaining a Google bill. FinOps on GCP is committed-use advice and idle-resource removal, quoted as work, not as a public saving percentage.
This page does not publish a Partner Advantage or Partner Network tier. Google’s Partner Finder is the record. TiCON designs, migrates and operates Google Cloud in Bangladesh. If a sales deck names a tier, believe the directory.
Yes: architecture, migration and operations on BigQuery, Vertex AI, GKE and Cloud Run, with local support from Dhaka. That is not the same as reselling GCP usage on a taka invoice.
TiCON’s taka reseller invoice is for AWS usage. Google Cloud work is quoted in taka for architecture and operations; the GCP usage bill follows the Google agreement. This page is not a GCP-in-BDT product.
There is no region in Bangladesh. Nearby Compute Engine regions are asia-south1 (Mumbai), asia-south2 (Delhi) and asia-southeast1 (Singapore). Ping times are not published on this page.
Google publishes BigQuery and Vertex AI as strengths. AWS is usually the broader catalogue and the path that can be invoiced in taka through TiCON. Pick the product you will run. The compare page is the criteria table, not a winner.
Yes, when the workload belongs there — typically analytics or ML. We can also keep the app on AWS and land only the warehouse on GCP. MAP funding amounts are not quoted; MAP is an AWS programme.
No Workspace licence table is published here. TiCON can deploy and administer Workspace as operations work. Buying the seats still follows Google’s own commercial path unless a written contract says otherwise.
Yes: monitoring, IAM, backups and a named owner for in-scope Google Cloud projects, quoted in taka for that work. Numeric response times stay in the contract. GCP usage itself is not a TiCON reseller line.
