KINGY / LIFECYCLE ARCHIVE
What shut down, what moved, and what you can use next.
Source-linked histories of AI tools and retired models. Acquisitions and pivots have their own view.
Last recorded hosted scan (live status requires JavaScript): 2026-11-21T22:30:30.574114+00:00. 5 histories need source review.
Plan the next step
Start with the affected product and date. A shutdown date, an export deadline and a data-deletion date can be different. An expired deadline does not establish that data can still be recovered.
Migration labels separate documented procedures or compatibility, provider recommendations and untested task alternatives. Compatibility applies only to the formats, endpoints or features named by the source. Kingy-tested requires a dated workflow test with its setup and result; full service/API migrations remain untested. The separately labeled local parser test covers response-format handling only.
The Change Tracker's next 90 days covers upcoming dates. Its replacement recommendations retain review holds; its source health shows stale or failed checks. A scheduled date passing does not by itself prove a service stopped working.
To cite a history, use its # link and name the affected service or model. Cite the linked original notice for the vendor's claim; preserve unknown dates and source-access limits.
14 expanded histories
25 histories. Filters require JavaScript; all records are readable below.
Humane Ai Pin
Consumer service ended 2025-02-28, noon PST
Humane announced the end of consumer Ai Pin server connectivity and .Center access at noon PST on February 28, 2025. Its notice identified calling, messaging, AI queries/responses and cloud features, asked users to export pictures/videos/notes before the deadline, and said remaining consumer data would be permanently deleted at that time. The announced export deadline has passed.
Historical evidence reviewed 2026-10-01. Source checked: not yet reverified by host.
Source could not be rechecked. Historical evidence retained; review required.
Timeline and migration sources reviewed 2026-10-29. The automated status above covers the original catalogue sources, not every source in these notes.
Affected scope: Consumer Ai Pin server connectivity and .Center data access. HP's asset transaction is a separate business event.
Verified timeline
2025-02-18 · HP announced an asset agreement
HP announced an agreement for Humane's Cosmos platform, technical talent and intellectual property. Its announcement does not establish continued consumer Ai Pin service or account transfer.
Sources: HP official announcement
2025-02-28 · Consumer service cutoff
Contemporaneous reporting of Humane's notice gives noon PST for the end of server connectivity and .Center access, including cloud-dependent calling, messaging and AI responses. The original support notice remains unavailable to this review.
Sources: Contemporaneous notice reporting · Original notice; currently unavailable
Data and export deadline
Deadline passed
February 28, 2025, noon PST (20:00 UTC)
The reported notice told users to download photos, videos and notes before the cutoff and said remaining consumer data would be deleted then. This is the documented notice, not a Kingy audit of deletion. No current .Center recovery route was verified.
Sources: Contemporaneous reporting of export and deletion notice
Migration evidence
No verified migration route
No supported transfer of the Ai Pin account, .Center archive or cloud service was established. HP's acquisition announcement is not migration documentation. A different assistant may cover some tasks, but this review supports no equivalent replacement or Kingy-tested migration.
Kingy has not tested this migration workflow. Documentation does not establish feature parity, preserved history or successful account access.
Sources: HP official announcement and transaction scope
Before relying on a replacement
- Keep any files already exported and confirm they open locally.
- List the functions you still need before evaluating another device; do not assume a purchase restores old data.
What to do now
- Check local copies of photos, videos and notes already exported; no current cloud recovery route is verified.
Cite this record
Attribute vendor claims to the linked source and preserve the affected product scope. Archive capture dates describe the preserved copy, not necessarily the announcement date.
Sources, scope and funding
Archived first-party Humane customer notice, snapshot February 19, 2025; direct origin DNS unavailable. Historical notice reviewed through archive replay; deletion execution not observed.
Funding raised: unknown; not established by the cited evidence. Deal values are not funding totals.
Date precision: day. Submit a correction.
Tome Slides
Hosted product sunset 2025-04-30
Tome announced its Slides sunset for April 30, 2025, with sign-in/content access ending after that date. It instructed users to migrate work beforehand, offered PDF export or support help, and said user data would be deleted after April 30. This archive cannot recover presentations.
Historical evidence reviewed 2026-10-01. Source checked: not yet reverified by host.
Source could not be rechecked. Historical evidence retained; review required.
Timeline and migration sources reviewed 2026-10-29. The automated status above covers the original catalogue sources, not every source in these notes.
Affected scope: Tome Slides hosted presentations and account content. This history does not establish the end of every business operated by its founders.
Verified timeline
2025-03-31 · Subscription cancellation deadline
Tome said all active subscriptions would be cancelled by March 31, with refunds for unused time. The notice survives in an April 10, 2025 Internet Archive capture; that capture date is not the announcement date.
Sources: Archived official sunset notice
2025-04-30 · Hosted presentation sunset
The notice said users would lose sign-in and content access after April 30, and files would be deleted afterward. The original help URL now returns 404; no exact shutdown hour or independently observed deletion completion is established here.
Sources: Archived official sunset notice
Data and export deadline
Deadline passed
Before April 30, 2025; no cutoff time specified
Tome directed users to export to PDF and offered help if that option was unavailable. Its earlier export guide warned that videos, narrations and other multimedia would not play in the PDF. Existing local exports are distinct from a recoverable hosted account.
Sources: Archived official sunset notice · Archived official PDF export guide
Migration evidence
Vendor-documented procedure
Gamma documents PDF, PPTX and DOCX import. A saved Tome PDF is therefore a candidate input, not a verified Tome migration. Gamma distinguishes its newer layout-preserving import from its text-only classic generator and notes that some charts become images. Kingy has not tested this workflow or verified Tome layout, media or account transfer.
Kingy has not tested this migration workflow. Documentation does not establish feature parity, preserved history or successful account access.
Sources: Gamma import documentation
Before relying on a replacement
- Keep an untouched copy of each existing export.
- Compare imported text, charts, links and fonts; rebuild multimedia from original assets where available.
What to do now
- Find existing PDFs and original media files. Test one retained presentation before importing the rest into another tool.
Cite this record
Attribute vendor claims to the linked source and preserve the affected product scope. Archive capture dates describe the preserved copy, not necessarily the announcement date.
Sources, scope and funding
Archived first-party Tome Help Center notice, snapshot April 10, 2025; direct origin currently404. Historical notice reviewed through archive replay; deletion execution not observed.
Funding raised: unknown; not established by the cited evidence. Deal values are not funding totals.
Date precision: day. Submit a correction.
Neeva consumer search
Closure 2023-06-02
Neeva closed its consumer search engine. Its enterprise technology had a separate continuation; this record concerns consumer search.
Historical evidence reviewed 2026-10-01. Source checked: 2026-11-21T22:30:02.930452+00:00.
Relevant entity, date precision and lifecycle wording checked
Cite this record
Attribute vendor claims to the linked source and preserve the affected product scope. Archive capture dates describe the preserved copy, not necessarily the announcement date.
Sources, scope and funding
DOJ brief corroborates May 20 announcement; notice report supplies closure. Original blog unavailable.
Funding raised: unknown; not established by the cited evidence. Deal values are not funding totals.
Date precision: day. Submit a correction.
Google Allo
Retired 2019-03
Google stopped supporting the Allo messaging app, which included Google Assistant and machine-learning features. Google directed its messaging work toward Messages.
Historical evidence reviewed 2026-10-01. Source checked: 2026-11-21T22:30:02.930452+00:00.
Relevant entity, date precision and lifecycle wording checked
Timeline and migration sources reviewed 2026-10-29. The automated status above covers the original catalogue sources, not every source in these notes.
Affected scope: Google Allo messaging and its conversation export window. Messages is a separate product.
Verified timeline
2018-12-05 · Google announced the end of Allo support
Google said it had paused Allo investment earlier in 2018 and would focus on Messages, which had received some Allo features.
Sources: Google announcement
2019-03 · Published service and export window ended
Google said Allo would work through March 2019 and users could export conversation history until then. This source gives month precision, not an exact final day or hour.
Sources: Google announcement
Data and export deadline
Deadline passed
March 2019; exact day and time unestablished in the cited notice
The historical export opportunity has ended. Google's linked Allo export-help page returned 404 in this review. The announcement does not establish a current recovery route or a precise server-deletion date.
Sources: Google announcement and historical export link
Migration evidence
Task alternative; migration untested
Google Messages documents text, photo, voice-message and video messaging. It is a current messaging direction, but the cited documentation does not establish import of Allo conversations or transfer of Allo's Assistant behavior. Kingy has not tested an Allo-to-Messages migration.
Kingy has not tested this migration workflow. Documentation does not establish feature parity, preserved history or successful account access.
Sources: Google Messages documentation
Before relying on a replacement
- Preserve any exports you already hold as separate archives.
- Check the messaging features your contacts and devices support before choosing a replacement.
What to do now
- Keep existing conversation exports as archives; the cited notice establishes no present-day export route.
Cite this record
Attribute vendor claims to the linked source and preserve the affected product scope. Archive capture dates describe the preserved copy, not necessarily the announcement date.
Sources, scope and funding
Google announcement. Assistant/ML messaging app; month precision.
Funding raised: unknown; not established by the cited evidence. Deal values are not funding totals.
Date precision: month. Submit a correction.
Duplex on the Web
Support ended 2022-12
Google’s archived Search Console notice says Duplex on the Web was deprecated and would no longer be supported as of December 2022, including its enabled automation features. This concerns the web automation product; it does not establish retirement of every Duplex technology or a separately named crawler.
Historical evidence reviewed 2026-10-01. Source checked: not yet reverified by host.
Source could not be rechecked. Historical evidence retained; review required.
Cite this record
Attribute vendor claims to the linked source and preserve the affected product scope. Archive capture dates describe the preserved copy, not necessarily the announcement date.
Sources, scope and funding
Archived first-party Google Search Console Help notice, snapshot December5,2022; original URL currently inaccessible. Historical web-product notice independently reviewed through archive replay.
Funding raised: unknown; not established by the cited evidence. Deal values are not funding totals.
Date precision: month. Submit a correction.
Google Keen
Shutdown 2024-03-24
Keen, Google’s machine-learning-assisted interest discovery experiment, closed. Its collections and associated content had a deletion deadline; the original sunset notice is no longer readable.
Historical evidence reviewed 2026-10-01. Source checked: 2026-11-21T22:30:02.930452+00:00.
Relevant entity, date precision and lifecycle wording checked
Timeline and migration sources reviewed 2026-10-29. The automated status above covers the original catalogue sources, not every source in these notes.
Affected scope: Keen / StayKeen interest collections, uploads and recommendation service.
Verified timeline
2024-03-14 · Shutdown email reported
9to5Google reported that users were emailed export instructions that day. This establishes the reported notice date, not a separately retrieved original announcement.
Sources: Contemporaneous notice reproduction; original unavailable
2024-03-24 · Access and deletion cutoff in the notice
The reproduced notice said the website would become inaccessible and Keens, posts, uploads, likes, follows and comments would be deleted. The time and time zone were not stated.
Sources: Contemporaneous notice reproduction; original unavailable
Data and export deadline
Deadline passed
Before the March 24, 2024 closure; exact hour unknown
The notice offered a ZIP containing curated links, uploaded images and owned text posts. No current download or recovery route is established; only exports already retained can be inspected. Deletion completion was not independently audited.
Sources: Contemporaneous notice reproduction; original unavailable
Migration evidence
Task alternative; migration untested
A source-following or bookmarking tool can cover part of the old task. No supported transfer of Keen recommendations, follows or likes is established. The original sunset page is unavailable, so the reporting remains explicitly attributed.
Kingy has not tested this migration workflow. Documentation does not establish feature parity, preserved history or successful account access.
Sources: Contemporaneous notice reproduction; original unavailable
Before relying on a replacement
- Keep an untouched copy of any existing ZIP; inspect it before importing or extracting files.
- Rebuild a reading list from retained links; check destinations before relying on old links.
What to do now
- Look for an existing Keen ZIP; keep an untouched copy and rebuild a source list from retained URLs.
Cite this record
Attribute vendor claims to the linked source and preserve the affected product scope. Archive capture dates describe the preserved copy, not necessarily the announcement date.
Sources, scope and funding
Google introduction, shutdown report. Original sunset page empty.
Funding raised: unknown; not established by the cited evidence. Deal values are not funding totals.
Date precision: day. Submit a correction.
Rewind
Capture disabled 2025-12-19
The Rewind update disabled screen and audio capture. The vendor separately described continued access to earlier Limitless meeting recordings and Pendant support; those are separate scopes.
Historical evidence reviewed 2026-10-01. Source checked: not yet reverified by host.
Source could not be rechecked. Historical evidence retained; review required.
Timeline and migration sources reviewed 2026-10-29. The automated status above covers the original catalogue sources, not every source in these notes.
Affected scope: Rewind's screen/audio capture. Local Rewind files, Limitless cloud meetings and Pendant support have separate evidence and deadlines.
Verified timeline
2025-12-19 · Capture disabled by the latest Rewind update
Limitless's sunset FAQ gives this date for disabling Rewind screen and audio capture. A generic help page still describes recording; this review found no explicit reversal of the sunset notice and did not test the app.
Sources: Limitless sunset FAQ · Conflicting generic screen-recording help
2026-09-09 · Local-data help dated separately
Limitless's Rewind help identifies the macOS data folder and says Rewind has no supported API. This documentation date does not establish renewed capture support.
Sources: Official Rewind data-location help
Data and export deadline
Scope-dependent; regional deadline passed
December 19, 2025 for listed unsupported Limitless regions; no universal local-Rewind export deadline established
The FAQ gave users in Brazil, China, the EU, Israel, South Korea, Turkey and the UK until December 19 to download Limitless information before account/data deletion. That does not establish deletion of every local Rewind archive. It separately promised access to earlier Limitless meetings throughout 2026 without naming a precise final cutoff.
Sources: Limitless regional and product-scope FAQ
Migration evidence
Vendor-documented procedure
The vendor identifies ~/Library/Application Support/com.memoryvault.MemoryVault as Rewind's local data location. Accessible Limitless accounts have a separate Data Exports tab with optional audio. Neither document establishes an importer for Rewind archives, recovery of deleted cloud data or a tested replacement. Kingy has not run either procedure.
Kingy has not tested this migration workflow. Documentation does not establish feature parity, preserved history or successful account access.
Sources: Official Rewind data-location help · Official Limitless export instructions
Before relying on a replacement
- Preserve existing local files before uninstalling or deleting data.
- For an accessible Limitless account, inspect a downloaded export before relying on it; keep Rewind and Limitless archives separately identified.
What to do now
- Identify whether your files are a local Rewind archive or a Limitless cloud export before following deletion or migration advice.
Cite this record
Attribute vendor claims to the linked source and preserve the affected product scope. Archive capture dates describe the preserved copy, not necessarily the announcement date.
Sources, scope and funding
Limitless FAQ. Screen/audio capture; other Pendant/meeting services are separate.
Funding raised: unknown; not established by the cited evidence. Deal values are not funding totals.
Date precision: day. Submit a correction.
Cortana standalone Windows app
Retired 2023
Microsoft retired Cortana as a standalone Windows assistant. Teams, Outlook and Microsoft 365 integrations ended on separate schedules. Sources disagree on the season, so the archive retains year precision.
Historical evidence reviewed 2026-10-01. Source checked: 2026-11-21T22:30:02.930452+00:00.
Relevant entity, date precision and lifecycle wording checked
Cite this record
Attribute vendor claims to the linked source and preserve the affected product scope. Archive capture dates describe the preserved copy, not necessarily the announcement date.
Sources, scope and funding
Microsoft support, deprecation table. Seasonal date discrepancy; year precision.
Funding raised: unknown; not established by the cited evidence. Deal values are not funding totals.
Date precision: year. Submit a correction.
Adept
Pivot / staff and licensing transfer announced 2024-06-28
Adept announced an enterprise agent strategy, an Amazon technology license and departure of founders and some staff. This does not establish that Amazon acquired or shut down Adept.
Historical evidence reviewed 2026-10-01. Source checked: not yet reverified by host.
Source could not be rechecked. Historical evidence retained; review required.
Cite this record
Attribute vendor claims to the linked source and preserve the affected product scope. Archive capture dates describe the preserved copy, not necessarily the announcement date.
Sources, scope and funding
Adept announcement. Context only; current commercial availability unestablished.
Funding raised: unknown; not established by the cited evidence. Deal values are not funding totals.
Date precision: day. Submit a correction.
Inflection AI / Pi
Microsoft staff transfer / enterprise pivot announced 2024-03-19
Inflection changed leadership and business direction when founders and staff joined Microsoft. Pi continued as a consumer product; it belongs in the transitions view.
Historical evidence reviewed 2026-10-01. Source checked: 2026-11-21T22:30:02.930452+00:00.
Relevant entity, date precision and lifecycle wording checked
Cite this record
Attribute vendor claims to the linked source and preserve the affected product scope. Archive capture dates describe the preserved copy, not necessarily the announcement date.
Sources, scope and funding
Microsoft, Inflection update. Pi remains publicly offered; context only.
Funding raised: unknown; not established by the cited evidence. Deal values are not funding totals.
Date precision: day. Submit a correction.
Character.AI
Google license / staff transfer 2024-08; announced 2024-08-02
Google obtained a non-exclusive technology license and hired some Character.AI employees. Character.AI continued its own consumer product. A licensing and staff transfer is not a product death.
Historical evidence reviewed 2026-10-01. Source checked: 2026-11-21T22:30:02.930452+00:00.
Relevant entity, date precision and lifecycle wording checked
Cite this record
Attribute vendor claims to the linked source and preserve the affected product scope. Archive capture dates describe the preserved copy, not necessarily the announcement date.
Sources, scope and funding
Alphabet SEC filing, announcement report, current product post. Context only.
Funding raised: unknown; not established by the cited evidence. Deal values are not funding totals.
Date precision: month. Submit a correction.
Uizard
Miro acquisition announcements 2024-05-27 / 2024-06-12
Uizard joined Miro while retaining a standalone public product offer. Two official announcement dates are retained; a distinct closing date is unknown.
Historical evidence reviewed 2026-10-01. Source checked: 2026-11-21T22:30:02.930452+00:00.
Relevant entity, date precision and lifecycle wording checked
Timeline and migration sources reviewed 2026-10-29. The automated status above covers the original catalogue sources, not every source in these notes.
Affected scope: Uizard joining Miro; a business transition without a documented product shutdown.
Verified timeline
2024-05-27 · Uizard announced it was joining Miro
Uizard said it would remain available and that the day-to-day product experience would not change for now.
Sources: Uizard announcement
2024-06-12 · Miro announced the combination
Miro welcomed Uizard and announced Autodesigner 2.0. Neither announcement supplies a distinct legal closing date.
Sources: Miro announcement
Data and export deadline
No shutdown deadline established
No acquisition-related export or deletion deadline stated
The public Uizard pricing page still offered the product when reviewed October 29, 2026; account access was not tested. Routine backups may be useful even when an acquisition does not require migration.
Sources: Official export guide · Public product offer; documentation only
Migration evidence
Vendor-documented procedure
Uizard documents screen exports as JPG, PNG, SVG or PDF and SVG use in supporting tools. Its guide says layers and comments cannot be exported and PDFs are not interactive. These are format-level procedures, not proof of an editable project transfer or Kingy-tested migration.
Kingy has not tested this migration workflow. Documentation does not establish feature parity, preserved history or successful account access.
Sources: Official export guide · Public product offer; documentation only
Before relying on a replacement
- Export representative screens and compare their appearance.
- Retain source projects and record comments separately where needed.
What to do now
- The acquisition alone establishes no forced move. Keep source projects and separate comments when using flat exports.
Cite this record
Attribute vendor claims to the linked source and preserve the affected product scope. Archive capture dates describe the preserved copy, not necessarily the announcement date.
Sources, scope and funding
Uizard, Miro. Close date unknown; standalone offer continues. Context only.
Funding raised: unknown; not established by the cited evidence. Deal values are not funding totals.
Date precision: day. Submit a correction.
MosaicML
Databricks acquisition completed 2023-07-19
Databricks acquired MosaicML and later integrated its model-building capabilities. This is platform lineage, not extinction of MPT weights or every former service.
Historical evidence reviewed 2026-10-01. Source checked: 2026-11-21T22:30:02.930452+00:00.
Relevant entity, date precision and lifecycle wording checked
Timeline and migration sources reviewed 2026-10-29. The automated status above covers the original catalogue sources, not every source in these notes.
Affected scope: MosaicML company/platform integration into Databricks; not a universal retirement of every model or endpoint.
Verified timeline
2023-06-26 · Acquisition agreement announced
Databricks announced a definitive agreement subject to closing conditions.
Sources: Databricks acquisition agreement
2023-07-19 · Acquisition completed
The closing release said MosaicML’s product would remain available for direct purchase.
Sources: Databricks closing release
2024-06-12 · Model-building integration described
Databricks said it had integrated and expanded capabilities from the acquisition. This is a dated vendor account of integration, not a current endpoint-access test.
Sources: Databricks integration announcement
Data and export deadline
No universal export/deletion deadline established
The cited transaction notices state no customer-data deletion deadline
The acquisition and integration dates do not establish that a particular hosted endpoint stopped or that customer data was deleted. Existing local checkpoints and account-owned artifacts need their own inventory and applicable licence review.
Sources: Databricks acquisition agreement · Databricks closing release · Databricks integration announcement
Migration evidence
No verified migration route
No blanket migration instruction follows from the acquisition. Identify the exact service, API URL and model version first; use that service’s current documentation and account notices to determine any required move.
Kingy has not tested this migration workflow. Documentation does not establish feature parity, preserved history or successful account access.
Sources: Databricks acquisition agreement · Databricks closing release · Databricks integration announcement
Before relying on a replacement
- Inventory hosted endpoints separately from local weights, checkpoints and training data.
- Preserve configuration, dependency versions and evaluation fixtures before changing a deployment.
What to do now
- Identify your actual hosted endpoint or local model artifact before deciding whether a migration is needed.
Cite this record
Attribute vendor claims to the linked source and preserve the affected product scope. Archive capture dates describe the preserved copy, not necessarily the announcement date.
Sources, scope and funding
Closing release, integration. Company/platform lineage; context only.
Funding raised: unknown; not established by the cited evidence. Deal values are not funding totals.
Date precision: day. Submit a correction.
x.ai scheduling assistant
Acquired, then sunset 2021-10-31
Bizzabo acquired the original Amy/Andrew AI scheduling service and sunset its standalone product. The original x.ai scheduler is unrelated to the later xAI/Grok company using a similar name.
Historical evidence reviewed 2026-10-01. Source checked: 2026-11-21T22:30:02.930452+00:00.
Preserved reviewed primary PDF unchanged
Cite this record
Attribute vendor claims to the linked source and preserve the affected product scope. Archive capture dates describe the preserved copy, not necessarily the announcement date.
Sources, scope and funding
Bizzabo acquisition, preserved sunset notice, pp. 23–26. Unrelated to today's xAI/Grok.
Funding raised: unknown; not established by the cited evidence. Deal values are not funding totals.
Date precision: day. Submit a correction.
Artifact standalone news app
Sunset announced 2024-04-02; actual cutoff unknown
Yahoo acquired Artifact and announced the end of its standalone news app. Its personalization technology continued in Yahoo News. The exact last-service date was not established.
Historical evidence reviewed 2026-10-01. Source checked: 2026-11-21T22:30:02.930452+00:00.
Relevant entity, date precision and lifecycle wording checked
Timeline and migration sources reviewed 2026-10-29. The automated status above covers the original catalogue sources, not every source in these notes.
Affected scope: Artifact standalone news app, distinct from the personalization technology acquired by Yahoo.
Verified timeline
2024-03-29 · Acquisition closed
Yahoo later identified this as the closing date.
Sources: Yahoo acquisition announcement
2024-04-02 · Standalone app ending announced
Yahoo said Artifact would no longer operate as a standalone app and that its technology would be integrated across Yahoo. This announcement does not establish the exact last-service date.
Sources: Yahoo acquisition announcement
Data and export deadline
Export and deletion dates unknown
No export/deletion deadline stated in the cited announcement
The announcement supplies no account-export procedure, saved-story transfer promise or data-deletion date. A later technology integration does not establish preservation of a former user account.
Sources: Yahoo acquisition announcement
Migration evidence
Task alternative; migration untested
A news reader can replace part of the reading task. Yahoo named Yahoo News as a destination for the technology, but that is not documented compatibility for Artifact accounts or reading history.
Kingy has not tested this migration workflow. Documentation does not establish feature parity, preserved history or successful account access.
Sources: Yahoo acquisition announcement
Before relying on a replacement
- Preserve saved URLs or exports you already have.
- Build a source list in your chosen reader; do not expect old personalization or saved items to transfer.
What to do now
- Preserve saved links you already have. No account/history transfer or current recovery route is established here.
Cite this record
Attribute vendor claims to the linked source and preserve the affected product scope. Archive capture dates describe the preserved copy, not necessarily the announcement date.
Sources, scope and funding
Yahoo announcement, Yahoo News continuation. Preserve unknown shutdown date.
Funding raised: unknown; not established by the cited evidence. Deal values are not funding totals.
Date precision: unknown. Submit a correction.
GPT-4.5 Preview
OpenAI API retirement 2025-07-14
OpenAI retired GPT-4.5 Preview from its API. The alias and dated snapshot belong to one retirement event; a model’s legacy documentation page does not prove it is callable.
Historical evidence reviewed 2026-10-01. Source checked: 2026-11-21T22:30:02.930452+00:00.
Relevant entity, date precision and lifecycle wording checked
Timeline and migration sources reviewed 2026-10-29. The automated status above covers the original catalogue sources, not every source in these notes.
Affected scope: OpenAI API: gpt-4.5-preview and gpt-4.5-preview-2025-02-27; separate from ChatGPT availability.
Verified timeline
2025-04-14 · Deprecation notice
OpenAI notified developers that GPT-4.5 Preview would leave its API.
Sources: Official deprecation history
2025-07-14 · API retirement
The deprecations table gives this shutdown date. The model page also labels the alias and dated snapshot shut down.
Sources: Official deprecation history
Data and export deadline
No export deadline documented
Not stated in this retirement notice
The cited notice concerns model access. It does not establish a customer-data deletion date or a recovery service.
Sources: Retirement notice
Migration evidence
Provider recommendation
The retirement table names gpt-4.1. Treat that as historical guidance: gpt-4.1-2025-04-14 now has its own listed shutdown date, January 14, 2027. Use the current model catalog and Change Tracker before choosing a replacement; a legacy model page is not evidence of account access.
Kingy has not tested this migration workflow. Documentation does not establish feature parity, preserved history or successful account access.
Sources: OpenAI deprecations · Retired alias and snapshot · Current model catalog
Before relying on a replacement
- Identify the exact model ID and endpoint in your application.
- Compare representative outputs, structured responses and tool calls before switching.
Check upcoming model retirement dates · Inspect current replacement recommendations and holds
What to do now
- Locate both the alias and dated snapshot in application configuration; use the current provider schedule before selecting a successor.
Cite this record
Attribute vendor claims to the linked source and preserve the affected product scope. Archive capture dates describe the preserved copy, not necessarily the announcement date.
Sources, scope and funding
`gpt-4.5-preview` / snapshot; history.
Funding raised: not applicable to a model. Deal values are not funding totals.
Date precision: day. Submit a correction.
GPT-4o in ChatGPT
App retirement 2026-02-13; Custom GPT exception ended 2026-04-03
GPT-4o left ChatGPT’s text-model selection, with a later cutoff for a Custom GPT exception. The announcement treated API, Voice and Images availability separately.
Historical evidence reviewed 2026-10-01. Source checked: 2026-11-21T22:30:02.930452+00:00.
Relevant entity, date precision and lifecycle wording checked
Cite this record
Attribute vendor claims to the linked source and preserve the affected product scope. Archive capture dates describe the preserved copy, not necessarily the announcement date.
Sources, scope and funding
OpenAI notice. API, Voice and Images scopes separate.
Funding raised: not applicable to a model. Deal values are not funding totals.
Date precision: day. Submit a correction.
GPT-4-32K
OpenAI API retirement 2025-06-06
OpenAI retired the GPT-4-32K API alias and its older snapshots. An original successor recommendation is a historical fact and needs a new availability check before use.
Historical evidence reviewed 2026-10-01. Source checked: 2026-11-21T22:30:02.930452+00:00.
Relevant entity, date precision and lifecycle wording checked
Timeline and migration sources reviewed 2026-10-29. The automated status above covers the original catalogue sources, not every source in these notes.
Affected scope: OpenAI API: gpt-4-32k, gpt-4-32k-0314 and gpt-4-32k-0613.
Verified timeline
2024-06-06 · Deprecation announced
OpenAI notified developers of retirement in one year.
Sources: OpenAI deprecation history
2024-06-17 · Existing-user restriction
OpenAI limited continued access to existing users from this date; that was not yet the final shutdown.
Sources: OpenAI deprecation history
2025-06-06 · API retirement
All three listed model identifiers share this shutdown date.
Sources: OpenAI deprecation history
Data and export deadline
No export deadline documented
No customer-data export/deletion date stated in this model notice
A model shutdown ends inference access; this notice does not establish loss of customer-held prompts or saved responses. Preserve those materials under their existing retention rules.
Sources: OpenAI deprecation history
Migration evidence
Provider recommendation
The historical table names gpt-4o. Treat it as a dated recommendation and check the exact successor snapshot against today’s supported-model catalog and Change Tracker. A model-name substitution does not establish equal context limits, output behavior, tool support or account availability.
Kingy has not tested this migration workflow. Documentation does not establish feature parity, preserved history or successful account access.
Sources: OpenAI deprecation history
Before relying on a replacement
- Search application configuration for all three old identifiers.
- Review limits, endpoint and response parsing; evaluate representative inputs before deployment.
Check upcoming model retirement dates · Inspect current replacement recommendations and holds
What to do now
- Search for all three retiring IDs; verify successor context limits and endpoint behavior before deployment.
Cite this record
Attribute vendor claims to the linked source and preserve the affected product scope. Archive capture dates describe the preserved copy, not necessarily the announcement date.
Sources, scope and funding
Alias and 0314/0613 snapshots grouped; history.
Funding raised: not applicable to a model. Deal values are not funding totals.
Date precision: day. Submit a correction.
InstructGPT text-davinci-003
Completions API retirement 2024-01-04
OpenAI retired text-davinci-003 from the Completions API. Its original gpt-3.5-turbo-instruct successor later retired too; migration guidance must follow the current supported endpoint.
Historical evidence reviewed 2026-10-01. Source checked: 2026-11-21T22:30:02.930452+00:00.
Relevant entity, date precision and lifecycle wording checked
Timeline and migration sources reviewed 2026-10-29. The automated status above covers the original catalogue sources, not every source in these notes.
Affected scope: OpenAI Completions API: text-davinci-003.
Verified timeline
2023-07-06 · Retirement announced
OpenAI announced retirement of older Completions models.
Sources: Official deprecation history
2024-01-04 · Model retired
The stated cutoff for text-davinci-003.
Sources: Official deprecation history
2026-09-28 · Successor also retired
The historical successor gpt-3.5-turbo-instruct subsequently shut down.
Sources: Official deprecation history
Data and export deadline
No export deadline documented
Not stated in this retirement notice
The cited notice concerns model access. It does not establish a customer-data deletion date or a recovery service.
Sources: Retirement notice
Migration evidence
Vendor-documented procedure
OpenAI originally documented changing the model parameter to gpt-3.5-turbo-instruct as a compatible Completions migration. That destination has retired. Modern Responses migrations use different response objects; the old compatibility claim does not carry forward to a new model or endpoint.
Kingy has not tested this migration workflow. Documentation does not establish feature parity, preserved history or successful account access.
Sources: Original migration instructions · Successor retirement · Responses migration guide
Before relying on a replacement
- Preserve your prompt templates and expected-output examples.
- Review endpoint, request parameters and response parsing together; test the complete workflow.
Check upcoming model retirement dates · Inspect current replacement recommendations and holds
What to do now
- Inventory legacy Completions request and parser code. Use the local fixture test below to see the response-format failure; validate a complete application separately.
Kingy-tested locally: response-parser fixtures
Executed October 29, 2026 with four synthetic JSON fixtures and no network requests. The legacy choices/text parser failed on all three Responses fixtures. A typed-output parser extracted completed text, preserved an incomplete-result warning, and flagged a tools-only response for application handling.
This is a local parser exercise. It does not verify a model, an API request, account access, tool execution, output quality or a complete migration. The tools-only case remains incomplete until the application executes the tool and continues the conversation.
Runnable method and synthetic fixtures · Dated results and limitations · Provider response-format guide
Cite this record
Attribute vendor claims to the linked source and preserve the affected product scope. Archive capture dates describe the preserved copy, not necessarily the announcement date.
Sources, scope and funding
History, original migration. Original successor later retired too.
Funding raised: not applicable to a model. Deal values are not funding totals.
Date precision: day. Submit a correction.
Claude 2.1
Claude API retirement 2025-07-21
Anthropic retired claude-2.1 on its own API. Amazon Bedrock and Google Cloud operate their own schedules; this date is not a universal hosted-model cutoff.
Historical evidence reviewed 2026-10-01. Source checked: 2026-11-21T22:30:02.930452+00:00.
Relevant entity, date precision and lifecycle wording checked
Timeline and migration sources reviewed 2026-10-29. The automated status above covers the original catalogue sources, not every source in these notes.
Affected scope: Claude API: claude-2.1. Partner-operated hosting can follow other schedules.
Verified timeline
2025-01-21 · Developers notified
Anthropic announced the upcoming retirement.
Sources: Official deprecation history
2025-07-21 · Claude API retirement
The documented retirement date for claude-2.1.
Sources: Official deprecation history
Data and export deadline
No export deadline documented
Not stated in this retirement notice
The cited notice concerns model access. It does not establish a customer-data deletion date or a recovery service.
Sources: Retirement notice
Migration evidence
Provider recommendation
The history table checked on October 29, 2026 recommends claude-opus-4-8. This is the current vendor recommendation, not evidence of its original 2025 advice or a working Kingy migration.
Kingy has not tested this migration workflow. Documentation does not establish feature parity, preserved history or successful account access.
Sources: Current recommendation and provider scope · Claude migration guide directory
Before relying on a replacement
- Confirm the deployment provider and its exact model schedule.
- Inventory API keys, model IDs, prompt templates and output parsers.
- Test representative prompts and tool-use loops, then check latency and total cost.
Check upcoming model retirement dates · Inspect current replacement recommendations and holds
What to do now
- Identify the deployment provider and exact model ID; retain locally owned prompts and evaluation examples before switching.
Cite this record
Attribute vendor claims to the linked source and preserve the affected product scope. Archive capture dates describe the preserved copy, not necessarily the announcement date.
Sources, scope and funding
`claude-2.1`; history. Partner schedules differ.
Funding raised: not applicable to a model. Deal values are not funding totals.
Date precision: day. Submit a correction.
Claude Sonnet 3.5
Claude API retirement 2025-10-28
Anthropic retired both listed Claude Sonnet 3.5 API snapshots in one event. Partner-operated deployments have separate lifecycle policies.
Historical evidence reviewed 2026-10-01. Source checked: 2026-11-21T22:30:02.930452+00:00.
Relevant entity, date precision and lifecycle wording checked
Timeline and migration sources reviewed 2026-10-29. The automated status above covers the original catalogue sources, not every source in these notes.
Affected scope: Claude API: claude-3-5-sonnet-20240620 and claude-3-5-sonnet-20241022.
Verified timeline
2025-08-13 · Developers notified
Anthropic announced the retirement of Sonnet 3.5 models.
Sources: Official deprecation history
2025-10-28 · Both snapshots retired
The two exact snapshots share this documented retirement date.
Sources: Official deprecation history
Data and export deadline
No export deadline documented
Not stated in this retirement notice
The cited notice concerns model access. It does not establish a customer-data deletion date or a recovery service.
Sources: Retirement notice
Migration evidence
Provider recommendation
The current history table recommends claude-sonnet-5-5. Its migration guide covers newer starting versions, not a direct 3.5 migration; it documents rejected sampling/prefill settings and thinking blocks that can break code reading only content[0].text. Treat it as preparation, not compatibility proof.
Kingy has not tested this migration workflow. Documentation does not establish feature parity, preserved history or successful account access.
Sources: Current replacement recommendation · Sonnet 5.5 migration guide
Before relying on a replacement
- Audit request settings and parse response blocks by type.
- Test the complete prompt and tool workflow on the intended provider before relying on it.
Check upcoming model retirement dates · Inspect current replacement recommendations and holds
What to do now
- Check both snapshot IDs. If an earlier migration took you to Sonnet 4.5, inspect the specific upcoming notice below.
Cite this record
Attribute vendor claims to the linked source and preserve the affected product scope. Archive capture dates describe the preserved copy, not necessarily the announcement date.
Sources, scope and funding
20240620/20241022 snapshots grouped; history.
Funding raised: not applicable to a model. Deal values are not funding totals.
Date precision: day. Submit a correction.
Claude Opus 3
Claude API retirement 2026-01-05
Anthropic retired claude-3-opus-20240229 on its API. This scoped record does not establish partner hosting availability.
Historical evidence reviewed 2026-10-01. Source checked: 2026-11-21T22:30:02.930452+00:00.
Relevant entity, date precision and lifecycle wording checked
Timeline and migration sources reviewed 2026-10-29. The automated status above covers the original catalogue sources, not every source in these notes.
Affected scope: Claude API exact snapshot claude-3-opus-20240229; partner-operated hosting has separate schedules.
Verified timeline
2025-06-30 · Retirement announced
Anthropic notified developers of the coming retirement.
Sources: Claude deprecation history
2026-01-05 · Claude API retirement
The history table lists this retirement date for the exact snapshot. Anthropic defines retired models as unavailable, with requests failing.
Sources: Claude deprecation history
Data and export deadline
No export deadline documented
No customer-data export/deletion date stated in this model notice
The model-access cutoff is distinct from a data-retention deadline. The notice does not establish deletion of locally retained prompts, outputs or application fixtures.
Sources: Claude deprecation history
Migration evidence
Provider recommendation
The history table reviewed October 29, 2026 recommends claude-opus-4-8. This is current provider guidance, not reconstructed original advice or a compatibility test. Confirm the actual deployment provider and test request settings, response parsing, tool use and cost.
Kingy has not tested this migration workflow. Documentation does not establish feature parity, preserved history or successful account access.
Sources: Claude deprecation history
Before relying on a replacement
- Use Console usage export to identify model usage by API key; this is an inventory CSV, not a conversation backup.
- Run representative non-sensitive prompts before switching the complete application.
Check upcoming model retirement dates · Inspect current replacement recommendations and holds
What to do now
- Use the provider’s usage inventory to find old calls; test the current recommended model on your own workflow.
Cite this record
Attribute vendor claims to the linked source and preserve the affected product scope. Archive capture dates describe the preserved copy, not necessarily the announcement date.
Sources, scope and funding
`claude-3-opus-20240229`; history.
Funding raised: not applicable to a model. Deal values are not funding totals.
Date precision: day. Submit a correction.
Gemini 1.0 Pro
Google Cloud/Vertex retirement 2025-04-21
Google Cloud retired the listed Gemini 1.0 Pro managed-service versions. This source does not establish a consumer Gemini app or Developer API retirement date.
Historical evidence reviewed 2026-10-01. Source checked: 2026-11-21T22:30:02.930452+00:00.
Relevant entity, date precision and lifecycle wording checked
Cite this record
Attribute vendor claims to the linked source and preserve the affected product scope. Archive capture dates describe the preserved copy, not necessarily the announcement date.
Sources, scope and funding
`gemini-1.0-pro-001` / `-002`; lifecycle table. Other platform dates not inferred.
Funding raised: not applicable to a model. Deal values are not funding totals.
Date precision: day. Submit a correction.
PaLM text-bison
Google Cloud/Vertex retirement 2025-04-21
Google Cloud retired its text-bison managed-service family. The lifecycle table lists the family identifier; individual snapshot dates are not inferred.
Historical evidence reviewed 2026-10-01. Source checked: 2026-11-21T22:30:02.930452+00:00.
Relevant entity, date precision and lifecycle wording checked
Cite this record
Attribute vendor claims to the linked source and preserve the affected product scope. Archive capture dates describe the preserved copy, not necessarily the announcement date.
Sources, scope and funding
Family identifier from lifecycle table; no invented snapshot dates.
Funding raised: not applicable to a model. Deal values are not funding totals.
Date precision: day. Submit a correction.
Mistral 7B v0.2
Mistral hosted retirement 2025-03-30
Mistral marks the v0.2 hosted model retired while still linking Apache-2.0 downloadable weights. Provider-hosted retirement does not eliminate local use of the released weights.
Historical evidence reviewed 2026-10-01. Source checked: 2026-11-21T22:30:02.930452+00:00.
Relevant entity, date precision and lifecycle wording checked
Cite this record
Attribute vendor claims to the linked source and preserve the affected product scope. Archive capture dates describe the preserved copy, not necessarily the announcement date.
Sources, scope and funding
Model card, hosted policy. Downloadable open weights remain linked.
Funding raised: not applicable to a model. Deal values are not funding totals.
Date precision: day. Submit a correction.
No histories match these filters. Try another view or clear the search.