Cloud-billing-exporter
Prometheus exporter that tracks cloud spend across Azure, AWS, GCP, Hetzner, Microsoft 365 / Defender and Google Workspace.
Platform availability
Available on 1 of 10 platforms
- Unraid
- TrueNAS (not listed)
- Umbrel (not listed)
- ZimaOS (not listed)
- Proxmox (not listed)
- Helm (not listed)
- Mac (not listed)
- Windows (not listed)
- Linux (not listed)
- Any server (not listed)
Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.
41/100 Fair
- Maintained
- 69last commit 65 days ago
- Popular
- 00 GitHub stars
- Easy to install
- 351 install platform, install notes, Docker image
- Light to run
- No data
Based on 3 of 4 factors.
Availability: platform listings confirmed today, links checked 24 days ago
- GitHub stars
- 0
- Open issues
- 0
- Last commit
- 2026-09-17
- Activity
- stale
Checked 8 days ago - source: GitHub (louij2/cloud-billing-exporter)
Resources & Compatibility
ARM (e.g. Raspberry Pi) is not supported.
Checked 54 days ago - source: Docker Hub image tags and published docs
First-install notes
- Configuration and credentials Configuration is a JSON file (see config.example.json in the repo) plus per-provider credential files. Mount both read-only into the container; credentials are never baked into the image. source
Fetched 39 days ago - each note links to its source
Variants
Alternatives
No alternatives collected yet.
Common questions
Does the exporter use one endpoint for multiple cloud bills?
Yes. It provides one Prometheus endpoint for all configured cloud bills.
Which port should I publish for the exporter container?
Publish port 9825, as used in the example container deployment.
Where should I report a bug or problem?
File it in the project's GitHub issue tracker.
What GCP billing export gotchas should I check?
Check for delays, missing SKUs, credits, and setup mistakes in the exported GCP billing data.
Answers sourced from github.com, github.com, www.stackspend.app
Community
- Any SDK to Programmatically Manage Cloud Billing Export Enable or ... (forum)
- Cloud billing export to BigQuery: Modifying the dataset (forum)
- How often does Cloud Billing data export update network egress ... - Reddit (reddit)
- How to merge billing export tables in GCP BigQuery (forum)
- Best Free Self Hosted CRM, Billing Software or Invoicing Software - Reddit (reddit)
Collected 47 days ago - public community threads