Cloud Run · asia-southeast1 · request-based billing
What this site costs
Every request to this site is metered. This is the month so far, read from Cloud Monitoring and priced at Google's list prices: what it costs, where the money goes, and what a busy day would do to it.
PORTFOLIO · CLOUD RUN
asia-southeast1 · request-based billing
Reading this month's meters…
Where the money goes
Where the money goes
On the live site this part reads the month's meters and says where the time and money went: how much of the traffic is the site watching itself, what Cloud Run's 100 ms billing step does to a fast server, and what the free tier does not cover.
What if it got busy?
priced with the receipt's list
Loading the price list…
What stops a runaway bill
- Scale to zeroNo instance runs while nobody is visiting, so a quiet hour costs only its uptime checks.
- At most 3 instancesThe instance cap is a ceiling on CPU and memory however busy the site gets.
- Rate limits where a request does workAsk answers 8 questions a minute per client, the contact form takes 3 messages per 10 minutes, and the MCP server 60 requests a minute.
- A S$1 budget alertOn the billing account, so a surprise reaches my inbox before it reaches an invoice.
- Not capped: bandwidthData out has no ceiling of its own. The budget alert is the tripwire, and a CDN in front of the site would be the fix if traffic ever made it matter.
How this is measured
Usage is Cloud Monitoring's own metering of this service: requests, billed instance time, CPU and memory allocation, and bytes sent to the internet, summed from the start of the month (UTC). The Go server reads it with the identity it already uses for the SLO, at most once an hour. The code
Prices are Google's list prices in US dollars on 12 November 2026: Cloud Run with request-based billing in Singapore, a Tier 2 region, and Premium Tier data transfer out of Singapore. The billing account pays in Singapore dollars at Google's own price list, and its month runs on Pacific time, so the invoice will not match to the cent.
Not on the receipt, because each stays inside its free allowance: image storage (about 0.5 GiB, held there by a cleanup policy), the uptime checks themselves (about 130,000 a month of a million free), logs and traces.
The invoice itself is only in the billing console. This page is an estimate from the same meters the invoice is built from.