CLOUD INTEGRATION

Alibaba Cloud Cost Management: One Table + Real Payable

The billing console manages one cloud; depth means exporting to OSS/MaxCompute or calling the OpenAPI. Mof unifies Alibaba with your other clouds in one read-only table: Resource Center, anomaly detection, allocation and reseller real payable.

Documentation

Alibaba Cloud native · roll your own

Billing console

Bill export / subscription

OSS / MaxCompute

BSS OpenAPI

Depth means exporting to OSS/MaxCompute or calling the API yourself

Mof · one read-only key

Read-only key

Auto-sync

Full dashboard

One table

Resource Center

Real payable

Works out of the box — no SQL, no extra query fees

Why teams use Mof to manage Alibaba Cloud cost

Plenty of teams run ECS, OSS, RDS, SLB and CDN on Alibaba Cloud, reading the bill in the console and allocating by cost units. Going deep by resource means exporting to OSS/MaxCompute or calling the BSS OpenAPI yourself — and once you also run Tencent Cloud, Huawei Cloud or global clouds, “why did this cost more?” takes several places to answer.

Mof is a FinOps platform for teams running more than one cloud — AWS, Azure and GCP alongside Alibaba, Tencent and other clouds most tools can’t reach. It connects to Alibaba read-only, then layers on the Resource Center, anomaly detection, cost allocation and real payable — all in one view.

Three ways to read your Alibaba Cloud bill — each with a catch

Billing console, export / subscription, BSS OpenAPI — each solves a piece, and each stays inside Alibaba Cloud.

Billing console (BSS)

Alibaba-onlyTencent / Huawei / global clouds live elsewhere
Current month is provisionalFinal bill only after the 3rd of next month
Utilization is separateCost and CloudMonitor utilization aren’t in one place
Basic anomaly detectionMostly budget alerts

Bill export / subscription (OSS / MaxCompute)

Pushed to OSS/MaxComputeYou build tables and process it
Sprawling fieldsDiscounts / coupons / usage tiers, many columns
No ready dashboardThe export is just detail files
Periodic refreshAuto-subscription pushes on a schedule

BSS OpenAPI

You write codeCall the API and process it yourself
Engineer-onlyFinance and business teams can’t use it
All on youPull, clean and dashboard, all maintained by you

How Mof solves these

Connect read-only, unify Alibaba Cloud with your other clouds, and add the Resource Center, virtual tags, anomaly detection and allocation.

It’s Alibaba-only — Tencent Cloud, Huawei Cloud and global clouds all live in separate tools

Mof brings Alibaba Cloud together with Tencent Cloud, Huawei Cloud, AWS, Azure and GCP — one table to view and compare.

For depth by resource or team, you export to OSS/MaxCompute or call the OpenAPI and process it yourself

Mof connects read-only and gives you a detailed dashboard — drill down by resource, account or tag, no tables or code to build.

Billing fields sprawl (discounts, coupons, usage tiers…), making a consistent view hard

Mof normalizes billing fields into one clean schema — the same across Alibaba Cloud and your other clouds, so you stop reconciling column by column.

Cost and utilization are viewed separately, so over-provisioned / idle instances are hard to spot

Mof’s Resource Center shows it in one place: inventory + utilization (P95) + real cost per resource + over-provisioned / idle / orphaned / stopped, across accounts and clouds.

Alibaba Cloud bought through a reseller hides the real discounted payable

Mof supports custom discounts: it converts list pricing into your real payable, laying out billed, discount, saved and payable in one line.

With mostly budget alerts, spend spikes surface late

Mof’s anomaly detection (Holt-Winters) catches spikes in real time and pushes to Slack, email, DingTalk, Lark or WeCom, with thresholds per account / team.

Allocation relies on cost units / tags, shared resources are hard to split, and exports need cleanup

Mof does showback by team / project / tag, splitting shared resources by your rules — then exports to Excel that finance can book directly.

Alibaba Cloud native vs Mof

Dimension	Alibaba Cloud native	Mof
Multi-cloud	Alibaba-only	Alibaba + Tencent / Huawei / Volcengine + global in one table
Depth	Export OSS/MaxCompute or call API yourself	Detailed dashboard on connect
Billing fields	Discounts / coupons / tiers, sprawling	Normalized, one schema across clouds
Resource + usage + cost	Cost and CloudMonitor utilization split	Resource Center: inventory + P95 + payable + waste
Virtual tags	Native tags / cost units	Virtual tags, flexible allocation
Real payable (reseller)	Reseller hides discounted price	Custom discounts → real payable
Anomaly detection	Mostly budget alerts	Holt-Winters real-time
Unified alerts	Alibaba’s own notifications only	Cross-cloud, to Slack / email / IM
Allocation / export	Split detail / export needs cleanup	Showback + one-click Excel
Multi-account	Resource Directory, Alibaba only	Many accounts + multi-cloud together

Alibaba Cloud cost management FAQ

How is Mof different from Alibaba Cloud’s billing console and Cost Manager?

Both manage single-cloud billing and allocation inside Alibaba Cloud. Mof unifies Alibaba Cloud with Tencent Cloud, Huawei Cloud, AWS, Azure and GCP in one table, then adds the Resource Center (utilization + cost + waste), virtual tags, anomaly detection and reseller real payable — no exporting to OSS/MaxCompute or calling the OpenAPI yourself.

For Alibaba Cloud bought through a reseller, can Mof show the real payable?

Yes. Under a reseller, the console may show list pricing, not your discounted cost. Mof supports custom discounts to compute the real payable, and clearly shows billed, discount, saved and payable.

How does Mof connect to Alibaba Cloud billing data? Is it safe?

Through a RAM sub-account access key with read-only permissions (or a bill subscription to OSS). Mof reads billing and resources only — it needs no write access and changes nothing in your Alibaba Cloud account.

Does it conflict with Alibaba Cloud’s allocation and cost units?

No. Mof reuses your tags and account structure, and layers cross-cloud showback and virtual tags on top — shared resources split by your rules, aligned to how you account internally.

Which Alibaba Cloud services does it cover?

ECS, OSS, RDS, SLB / ALB, CDN, EIP, NAT, cloud databases and other major line items sync automatically — no per-service setup.