Validate the payload contract
Reject unmarked or malformed fixtures before any comparison result is produced.
Cloud data controls
See exactly what changed in the price catalog.
Two authorized AWS or Azure retail-pricing snapshots become a normalized current catalog, a reviewable change ledger and a frozen receipt.
2new price keys
1removed key
2changed prices
6/6proof tests passing
The delivery
A small pipeline with an acceptance boundary.
Normalize one provider
Map provider, SKU, region, operating system, price type, currency, unit and hourly price into stable keys.
Compare two snapshots
Separate new, removed, price-changed and unchanged keys while surfacing duplicates and invalid rows.
Freeze the review receipt
Return current-snapshot CSV, changes CSV, SQLite tables, summary JSON and deterministic content hashes.
Owned synthetic proof
Inspectable evidence, not a live-provider claim.
The downloadable proof uses deliberately synthetic AWS Price List-style and Azure Retail Prices-style payloads. It performs no network call and contains no account, credential, customer record or production endpoint.
Download the synthetic proof ZIP ยท Read the run summary
Proof ZIP SHA-256: 865e2c5e9ad603054f40fe68481cd237d302821fd50651be89b0b27230db047d
Included
One bounded audit.
- One AWS or Azure retail-pricing payload family
- Two authorized, sanitized JSON snapshots
- Up to 100 unique price keys
- CSV, SQLite, summary and receipt
- One written review round
Excluded
No hidden production promise.
- Cloud-account login, credentials or billing access
- Calculator scraping or browser automation
- Deployment, monitoring, SLA or live schedule
- Cost optimization, budgeting or financial advice
- Regulated, government or official-institution work
Start with metadata
Describe the catalog shape, not the data.
The public form asks only for provider, record count, key dimensions and target output. Files, credentials and private URLs stay out of the issue.