What shipped, dated and explained.
Every change to Acme Cloud — features, fixes, and the occasional breaking change — written by the team that built it. Newest first.
Per-key rate limits for the v2 API
Set request ceilings on individual keys from the dashboard. Defaults stay at 100 req/s, with per-key overrides on the Keys tab — the most-requested control from multi-tenant teams.
The legacy /v1/charges endpoint is retiring
v1 charges sunset on Apr 1, 2026. Migrate to /v2/payments — the response shape is unchanged, only the path moves. Full migration note on the entry.
The dashboard overview now paints in under a second
We moved the usage rollups to a read replica and trimmed the first payload by 60%. Cold-start loads that took three seconds now finish before you blink.
Webhook retries no longer double-deliver on timeout
A race in the retry queue could deliver the same event twice if your endpoint responded right at the 10s boundary. Each event now carries a stable idempotency key.
Scoped API keys with read-only and write roles
Mint a key that can only read, or only write to a single resource. Roles are visible on the Keys tab and enforced at the edge — no more all-or-nothing secrets in your CI.
Clearer error bodies on 4xx responses
Every client error now returns a stable code, a human message, and a docs link. Your error handling can switch on the code instead of parsing strings.