DON’T LET A RETIREMENT BREAK YOUR WORKFLOW
Your AI stack.
Your next deadline.
Know what’s changing, which route it affects and when to act. Keep a calendar or get the reminders you choose.
Loading the source catalog…
CHECK YOUR CONFIGURATION
Check your code
Runs entirely in your browser. Pasted text is never sent, logged, stored or included in analytics. Only model IDs are matched; pasted code is never run.
ONLY IF YOU ASK
Email alerts for your stack
Choose providers and reminder windows. Confirm your email before any alerts start. Optional notice-change alerts cover the selected catalog. Unsubscribe from every alert.
Your watchlist stays in your browser. Email and preferences are stored privately on Kingy’s hosting, separately from newsletters. Unconfirmed requests expire after 48 hours; unsubscribe deletes your record. Mail acceptance does not guarantee inbox delivery.
Your email preferences
Sources, date precision and how alerts work
This selected catalog combines retained Stack Change Radar records with official notices reviewed for this release. It is not a census of all providers. Read the route and source on each record: an API retirement may not affect the consumer app or another cloud provider.
Read each record’s date type and qualifier. “Not sooner than” is a minimum lifetime, not a scheduled retirement. An elapsed date alone does not prove a service is offline. Unknown dates have no calendar event. Records needing source review are excluded from calendars and email reminders.
Calendar downloads are snapshots. Subscribe to the copied calendar URL for updates; your calendar controls polling. Stable event IDs and revision numbers allow updates. A removed date becomes a cancelled calendar event. Reminder support varies by calendar.
Email reminders run hourly through the existing hosting scheduler. They are sent on the selected day at 30, 7 or 1 days before a listed date, at most once per record revision and window. There is no backfill of missed reminder days. Existing automated source wording checks run daily. The newly added provider and cloud sources require manual re-review after seven days; their checks do not crawl those sites automatically. Changed or stale evidence is held for review. Notice-change alerts follow catalog updates, not every edit to a vendor page. No AI inference testing is claimed.
Browse the lifecycle archive · Report a correction · Kingy privacy policy
Cloud lifecycle summaries credit Amazon Web Services (CC BY-SA 4.0, summarized with route/date fields), Google (CC BY 4.0, summarized), and Microsoft Learn. The original source controls. The Bedrock-derived summaries and factual review receipts are available under CC BY-SA 4.0.
Why counts differ
Radar counts individual model and route lifecycle facts. AI Deadlines is a selected catalog of actionable notices, sometimes grouping several model IDs in one notice. The open shutdowns dataset also covers products and plans. These counts measure different things. The former Deadlines import refreshed existing records but omitted new Radar records; additions are now reviewed against official sources.