Sources and method

Only the vendors' own pages

Model and API dates come from each vendor's deprecation or lifecycle page: OpenAI's deprecations, Anthropic's model deprecations, the Gemini API deprecations, Google Cloud's model versions, Amazon Bedrock's legacy and end-of-life models, Azure OpenAI's model retirements and AWS's services in sunset (data and AI services only). Managed database, Kubernetes and data runtime versions come from the endoflife.date API, which links each version to the vendor's own notice. Every row links to the page it came from. Where a page gives no announcement date or replacement, the field stays empty.

Beyond those, Sunsets reads a growing list of sources: other model providers' deprecation pages (Groq, Together AI, Mistral, Cohere, Microsoft Foundry, Databricks, GitHub Copilot), cloud retirement feeds (Azure Updates, Google Cloud release notes, AWS What's New), version lifecycle tables (Cloud Run, App Engine, Azure Functions, Amazon EMR, Databricks Runtime, Confluent, MongoDB, Elastic) and the deprecation entries on releases.fru.dev. Each is read with the same plain parsers: a lifecycle table by the words in its header row, a feed or changelog by the sentences that name a retirement and a full date. A row without a full date is skipped, never guessed.

How new sources are found

Every run tries to add sources, not just rows. It reads the endoflife.date catalog and enrolls each managed data service, database and data runtime it has not tracked yet. It probes a rotating slice of the companies in the companies.fru.dev registry for deprecation, lifecycle, support-policy and changelog pages on their site and docs site. And it follows links on the pages it reads that point to another deprecation or lifecycle page. A page becomes a source only when it answers (robots.txt allowing) and lists at least one dated retirement; one that fails three reads in a row is dropped. Everything a new source adds is marked Unverified until checked.

Firm dates and earliest dates

A firm date is when requests stop working. Some vendors also publish the earliest date a current model could retire ("not sooner than"); those rows are marked and never counted as due.

Checked weekly, and daily near a deadline

Every Monday the site reads every source again with plain parsers (no language model). Every other day it reads the sources that list something due within 30 days, every new source, and a rotating slice of the ones read longest ago, so a date moved close to its deadline shows up the next day. A moved date keeps the old one in the change log, so a postponed shutdown shows as a change. A new retirement, a moved date, a changed replacement or an upcoming item a page stops listing is recorded as a dated change with the source, marked Unverified until a person checks it. A page that suddenly parses to far fewer items is set aside for a person instead of being trusted.

Calendar feeds

sunsets.fru.dev/calendar.ics holds every upcoming date; each vendor page has its own feed. Events are all-day, on the retirement date, with the replacement and the source in the description, and keep the same ID when a date moves, so your calendar updates.

Models across fru.dev

Model names link to their page on models.fru.dev where it has one; vendors follow the shared registry at companies.fru.dev.

Disclaimer

Retirement dates from vendors' own deprecation and lifecycle pages, cloud retirement feeds, changelogs and endoflife.date, checked daily; each run also looks for new sources. Rows a person has not checked against the vendor page yet are marked Unverified. The list grows as vendors announce new retirements. Vendors move dates; the vendor's page is the final word. Logos via logo.dev; trademarks belong to their owners. Anonymous usage stats via Google Analytics. Use Suggest a correction on any page.