Blog
What shipped in each release, why CloudBridge is built the way it is, and what we learn from the bills that go wrong. Posts in Chinese are on the Chinese blog.
- A $10,811 Durable Object alarmA dormant Cloudflare project looped through six trillion reads and writes and billed $10,811.41 before anyone knew. What happened, why nothing warned anyone, and how to make sure something warns you.
- 0.5.0: it keeps watchingCloudBridge stays in the menu bar and refreshes on a schedule, Cloudflare joins split down to the bucket and Durable Object, and Insights scans AWS and Cloudflare for what to cut.
- 0.4.0: more ways in, more ways to read itAWS Data Exports straight from S3, a Models page for what each LLM model costs per token, a read-only SQL console, monthly budgets — and the whole app running in a browser.
- CloudBridge vs OptScaleOne is a FinOps server for an organization, the other a desktop ledger for one person's bills. Which one fits depends less on features than on who is asking.
- 0.3.1: one of everythingA consistency pass over the whole interface — one shared set of cards, buttons, pills and table headers — plus a signed, notarized macOS build.
- 0.3.0: bring your own billA bill you downloaded from a console now imports into the same ledger the APIs feed, the Overview stops mistaking a covered cost for a cheap one, and the interface is rebuilt at desktop density.
- 0.2.0: a cost viewer becomes a ledgerCharges from every source now land in one FOCUS-shaped fact table, raw payloads are kept so a mapping fix costs nothing to replay, and a total is finally a single currency.