LLMSwaps

Which model each app runs today, and when it last changed

Active deployment: who a notice is sent to

An active deployment is a configured use of a specific model version. One platform in this register states that retirement notices go to subscriptions that have one, which means the notice reaches whoever set up the configuration and nobody downstream of them. As of 2026-09-22.

Who a notice reaches, and who it does not. Recorded 2026-09-22.
Receives the noticeDoes not
The subscription holding the deploymentA customer of an application built on it
Whoever configured the versionWhoever is producing work with it
An account with billing attachedA freelancer using that account's tooling
Somebody who can edit the configurationSomebody who can only stop working

Inclusion rule. Read from the lifecycle policy of the one platform in this register that states who its notices are sent to. Order. From the recipient outward.

1A notice is only useful to somebody who can act

Sending a retirement notice to the account that configured a deployment is sensible: that is who can change the version string. It also means the warning stops at the layer that administers software rather than reaching the layer that makes the work.

For a production two layers down, the notice period exists and the notice does not arrive. The commitment is real and it was made to somebody else.

A targeted notice stops at the layer that can actSending a retirement notice to the account that configured a deployment is sensible: that is who can change the version string. It also means the warning stops at the layer administering software rather than reaching the layer making the work.The platformSends a notice to subscriptionswith a deploymentTargetedReaches whoever can editthe configurationThe applicationHolds the version string on itscustomers' behalfNot passed onNo published route forforwarding itThe productionBuys a tier and deliversepisodesHears nothingLearns from output, orfrom a public pageOne retirement noticeWhere the warning stops travelling
Fig. 1 The dated page is public; the notice is not, which is why a public schedule matters more than a mailing list.

2The requirement cuts the audience twice

A subscription without an active deployment gets nothing, which is reasonable and means a team evaluating a model rather than running it in production hears nothing about its retirement.

That matters for anybody choosing a model for a season starting next quarter. The dated page is public; the notice is not.

3Which is why the public page matters more

Because notices are targeted, the only warning available to everybody else is the published schedule and the published period. Those are readable without an account, which is the standard this register applies to every source.

The sourcing page sets out why nothing behind a login is recorded here, even where it would be more informative.

A definition rather than a dated entry: no line above is a vendor statement. Where this word turns up in a real notice, the wording and the date are on how much warning anyone gives. Nearby terms: Export window, House model, Licensed model.