Simple cloud costs. Honest data. Local control.
See the latest reported hourly and daily cost from cloud accounts, broken down by service and kept clear of forecasts and guesses.
One focused view of current cloud spend.
Cloud Cost Meter shows what the selected provider has actually reported, with the period, currency, source, and freshness beside it.
Latest reported hour
See the newest cost bucket posted by the provider. A delayed provider feed stays delayed instead of being presented as current.
Today so far
See the provider-reported UTC-day amount when available. The meter does not project the rest of the day.
Services, not mystery totals
See the services that make up the reported day using the same dataset as the headline total.
Connect. Collect. Explain.
- 01
Connect
Add a provider account using its normal profile, credential, or browser/device login flow.
- 02
Collect
Cloud Cost Meter reads the provider billing surface locally through Web/API and/or CLI collection.
- 03
Explain
Every observation identifies its source, period, currency, freshness, and coverage.
Keep account contexts separate.
Work, personal, client, and experimental accounts can each keep an independent provider profile, credential path, login job, and cached observation identity.
A login for one account does not silently become another account’s cost data. Web/API and CLI observations are stored separately and are alternate views, never amounts to add together.
A delayed number is better than a made-up number.
Cloud billing is not instantaneous. Providers can lag and revise usage. Cloud Cost Meter shows the observation time and status, keeps missing data unavailable, and never turns a missing response into $0.
Reported billed cost, optional inventory list-rate estimates, forecasts, credits, free-tier allowances, and invoices are different concepts. The meter keeps them separate.
OCI, AWS, and Google Cloud adapters.
Coverage depends on provider permissions, billing exports, installed CLIs, account configuration, and the billing surfaces each provider exposes.
Oracle Cloud Infrastructure
Usage API and OCI CLI observations, plus supported resource inventory and list-rate estimates.
Requires an OCI signing-key profile or session-token profile.
Amazon Web Services
Cost Explorer hourly observations through the SDK and AWS CLI when configured.
Requires Cost Explorer permission and an AWS profile or configured login.
Google Cloud
BigQuery Billing export observations through the Python client and bq when configured.
Credentials stay on the computer running the meter.
Provider credentials are written to app-owned local files with restricted permissions. The account catalog stores references and settings, not private keys, access keys, tokens, or passwords.
Normal collection calls the provider API or billing export from the local application. Cloud Cost Meter does not require a hosted billing proxy for normal collection and does not upload credentials to a Cloud Cost Meter server.
What the meter does—and does not—claim.
Is this a real-time bill?
No. It shows the newest provider-reported data available to the selected source. Providers can lag and revise billing data.
Does it replace an invoice?
No. The provider invoice and billing console remain the official final source. Cloud Cost Meter is a focused operational meter.
Are Web/API and CLI amounts added together?
No. They are alternate observations. The meter selects a usable source for the headline and can show both for comparison.
Why is missing data not shown as zero?
No response, missing permission, or an unconfigured export does not prove that an account spent nothing.
Can multiple accounts be configured?
Yes. Each account is kept in its own provider context and can be refreshed independently.
What is the inventory estimate?
It is a separate list-rate estimate for supported resources. It is not provider-reported billed cost and is never silently combined with it.