About

We teach usage as a craft, not a vendor screen.

Backup Cloudhub started when three Bangkok platform engineers realised their “analytics” stack could not explain a single invoice. The studio still sits in Chatuchak. The topic is still API Usage Analytics for Apps.

Bright office interior with long wooden tables and large windows
Evening light in the Phaholyothin studio — tables cleared for trace review, not keynotes.

Mission

Fewer panels. Better arguments.

Our mission is narrow on purpose. We help product and engineering teams in Thailand and the wider region decide what an API “use” is, capture it without wrecking the app, and defend the resulting numbers in a room with finance.

We do not sell observability platforms. We do not pretend a course replaces an SRE rotation. We do insist that usage analytics is a literacy, the same way accounting is a literacy.

Small team collaborating around laptops at a shared table

Pedagogy

How a week actually runs

Monday brief

A short written prompt lands before class: define the unit, sketch the sample, or mark the alert you would keep. No slide homework.

Studio night

Ninety minutes on live traces, then forty on critique. Instructors interrupt when a chart cannot survive a CFO question.

Quiet recap

A recorded walkthrough goes out the next morning for anyone covering a late shift across Thailand’s time zones.

Colleagues reviewing notes during a working session

Community

A small room, not a funnel

Cohorts stay under sixteen. Alumni return for open trace nights when a new endpoint starts lying. We host in English; Thai is welcome in discussion, and several case studies are drawn from domestic super-apps, logistics, and regional banking APIs.

If you need a private desk for a single company, that is a different contract — see In-house Desk — not a louder version of the public studio.

Student journey

From first login to a ledger you can defend

Most people arrive with a dashboard already in production and a vague sense that finance does not trust it. Week one is deliberately slow: write the unit of use, list what the current SDK actually emits, and mark three charts you would delete.

Mid-course, you instrument a small mobile-plus-API pair we provide. The point is not pretty Grafana. The point is being able to explain why a Bangkok Friday evening looks like a traffic spike rather than a fraud event.

By the close, you present a one-page usage ledger to the room. Some students leave still missing a production sampling story — we say so in the review. Honesty is part of the pedagogy; inflating confidence is not.

See what you can enrol in →