Price unknown consumers, expiring exceptions, and migration support instead of declaring an API deprecated forever.
An internal API has a sunset date, but nobody can name every consumer. Traffic remains after the deadline, exceptions have no owner, and the old service still requires on-call support. That is migration debt.
Use one ledger
consumer,monthly_calls,owner,migration_hours,exception_until,last_seen
billing-ui,120000,team-a,24,,2026-07-18
legacy-export,80,team-b,40,2026-08-15,2026-07-17
Killing an API endpoint is easy. Killing it without breaking your consumers is the hard part. Most...
We published a per-lookup overage rate on every paid plan from launch. None of it was ever charged to...
How I bill per-invoice on a small GST SaaS — reserve, settle, refund — and the concurrency bug an audit found where two uploads…
If your team has any custom Atlassian Cloud admin automation — IdP sync, SCIM glue, lifecycle...
Most API deprecations announce themselves. You pin a version, the vendor retires it, and your next...
The claims registry: one file where every public claim has a row, every row points at a versioned result file, and a 90-day…
