Services
// Cloud Billing by Digithun
Same Google Cloud. Better buying.
Pay in THB with a proper tax invoice, get support in Thai, and have engineers watching your spend.
Switch your billing Request a current-state review
Switching is a billing-account change — no migration, no downtime, no lock-in.
Google Cloud Partner & Authorized Reseller · ISO/IEC 29110
// The problem
The technology was never the hard part for finance.
-
A foreign credit card is doing the buying
Someone’s card, someone’s limit, and a monthly reconciliation nobody enjoys. It does not scale past a certain spend, and it does not survive an audit comfortably.
-
The invoice is not a Thai tax invoice
Withholding tax, VAT and documentation requirements do not fit neatly around a foreign charge in a foreign currency.
-
The budget is in baht. The bill is not.
The workload did not change, but the number did — and someone explains that variance to the CFO every quarter, for a decision nobody in the room made.
-
Support starts in another time zone
The first response arrives after your incident is over, in a language your on-call engineer is translating at 2am.
// Direct versus through us
What actually changes — and what does not.
| What changes | Buying direct | Through Digithun |
|---|---|---|
| Payment | International credit card | Bank transfer or card, THB |
| Tax documentation | Foreign invoice | Full Thai tax invoice and receipt |
| Payment terms | Card cycle | Aligned to Thai business payment cycles |
| Services & console | — | Identical — same services, same console, same SLAs |
| Support | Vendor hours, English | Thai engineers who know your workloads, plus vendor escalation |
| Spend visibility | Per-console | Reports and optimization advice built in |
// How it works
Three steps, and none of them touch your infrastructure.
-
Switch billing
We move your account under Digithun billing. No migration, no downtime — your infrastructure doesn’t move an inch.
-
Same console, same cloud
Everything stays exactly where it is. Only the invoice changes.
-
Better every month
THB invoicing, Thai support, and spend insights from month one.
// Multi-cloud
More than one cloud?
We also resell Alibaba Cloud and BytePlus.
// What comes with it
Included with billing.
-
Consolidated billing report
Broken down by project, environment or team, in a format finance can actually post.
-
Utilisation and asset report
What you are running, what it costs, what changed since last month, and the things nobody remembers creating.
-
Optimisation advice
Where the money is going that does not need to. Acting on it is optional; knowing is not.
-
A named person to escalate to
A local team that can look at your account with you before deciding whether it needs to go to the vendor.
// Common questions
What finance asks first.
Does anything change in my environment?
No. Billing changes; infrastructure does not. Your projects, consoles and access stay exactly where they are.
Is it more expensive than paying Google directly?
Before you switch, we put your exact terms in writing next to what you pay today — the comparison is yours to make before you commit to anything.
Can I combine this with managed services?
Yes — most clients pair billing with Managed Cloud or Managed FinOps.
What about Google Workspace?
Same model, same invoice.
Can we move back if we change our mind?
Yes. Billing can move back to direct purchase or another reseller. We would rather you stay because it works than because leaving is difficult.
What happens to our committed-use discounts?
Existing commitments are reviewed as part of the written proposal — what transfers, what is re-established, and what that does to the numbers, before you sign anything.
Who do we call when something breaks — you or Google?
Us first, if you want a human who has seen your account before. Your support entitlements from the provider are unchanged; what we add is a Thai team in your time zone and an escalation path into the vendor when it needs to go further.
Send us last month’s bill
We will tell you exactly what changes if you buy through us, in writing, before you commit to anything.
Innovate for the better tomorrow.
// Corporate update
Our
Move
-
Buying the platform and building on it used to be two conversations with two suppliers. It is one conversation now: we resell Google Cloud, Alibaba Cloud and BytePlus, and the same engineers who size the environment stay with it through production support.
For teams already running with us, nothing changes technically — the difference is commercial. Licensing, quota and billing sit with the people who know what the workload actually does.
-
A certified implementation partner works to the cloud provider's published reference architectures. In practice that means your landing zone, IAM model and network layout look like something any Google Cloud engineer can pick up — including the next team you hire.
It also means the review gates are not ours to waive. Where the reference architecture asks for separation of duties or a break-glass path, it gets built.
-
Hospital data arrives in fragments — HIS exports, lab feeds, scanned forms, free-text notes in Thai and English. Before a model sees any of it, someone has to answer where each field came from, who consented to what, and which records must never leave the country.
We build that layer first. It is slower to demo and it is the reason the pilots survive contact with a real ward.
-
Live commerce moves fast enough that the recommendation loop has to close in the same session. That puts the weight on the event pipeline, not the model: what counts as a view, when a cart event lands, how quickly the feature store sees it.
We treat the BytePlus components as a stack to be wired properly rather than a switch to be flipped. The lift comes from the wiring.
-
The site you are reading ships as static HTML, one stylesheet and one script, served by a Node process with a strict content security policy. There is no analytics tag, no font CDN and no tracker.
It is partly a statement of taste and partly a working sample: the same restraint we bring to a client's platform, applied to our own front door.
-
Warehouses fill up faster than they get governed. By the time a model needs a feature, nobody can say which of the four revenue columns is authoritative, and the project stalls in a meeting about definitions.
The fix is unglamorous: contracts on the ingest side, lineage through the transformations, and one owner per domain. Do that and the AI work stops being archaeology.