Summary
It answers the region question, which is where Azure bills actually diverge.
Searching and comparing go straight at the Azure Retail Prices API, so the same SKU can be priced in two regions in one pass and in the currency you work in. The estimate call turns that into a monthly figure for the hours you will really run.
What it is
A pricing server over the Azure Retail Prices API, run locally from a checkout. Every figure comes from the live API rather than a stored table.
What you get
- azure_price_search — Azure retail prices with flexible filtering, in the currency you ask for
- azure_price_compare — the same service priced across regions and SKUs
- azure_cost_estimate — an estimated cost for a usage pattern you describe, rather than an always-on assumption
- azure_discover_skus — the SKUs available for a service
- azure_sku_discovery — SKU discovery with fuzzy matching, for when you can only describe roughly what you want
- Savings plan pricing wherever the API publishes it
Requirements
Python and a clone of the repository — the setup script builds the environment, and the client config points at the module. The config carries no credentials.
Setup effort
Build from source — clone the repository and build it, then point your client at the binary