Ending early: how access stops before a date

Access can stop before the date on the page. Amazon Bedrock states that an existing customer may lose access after fifteen days of inactivity once a legacy period begins, LTX Studio reserves the right to replace models at any time, and Microsoft Foundry states only that a date cannot be pushed back. From 5 source pages, read 2026-09-12 to 2026-09-22; no maker pays to be listed.

Inclusion rule. A cell is filled from a published sentence about access ending other than on a stated date. A reader's guess about how quickly a menu could change does not fill one. Order. Entries publishing something about early loss of access first, then the rest.

1The date is a ceiling, and sometimes not even that

Planning treats a published date as the moment work has to stop, which makes it feel like a floor as well as a ceiling. Two entries here say otherwise in opposite directions: one says the date cannot be pushed back, another says its dates are the earliest a model might go.

Those two sentences look similar and mean opposite things. One removes the hope of an extension, the other admits the date may quietly become later, and a production that read both as the same kind of commitment would plan two migrations wrong.

2Disuse is the clause nobody expects

The sharpest sentence in this column is about inactivity rather than about dates. Once a legacy period begins, an existing customer can lose access after fifteen days of not calling the model, which turns a six-month window into a fortnight for anybody between projects.

That is exactly the shape of a serial production: heavy use while an episode block is in flight, then weeks of writing. A team that stopped calling a model to finish a script can come back to find the window it was counting on already spent.

3Where nothing is published, a menu edit is the mechanism

For the entries with an empty cell there is no clause to read, and the way access ends is simply that a line disappears from a priced page. No date precedes it and no notice follows it, so the event is only visible to somebody comparing two readings.

This is the column where an absence is most expensive, because the other columns at least describe a future. Here the blank says the ending has no announced shape, and a plan that assumes a runway has assumed something nobody offered.

4This column, entry by entry

The ending early column read one entry at a time, wherever that entry has published something here or falls silent in a way the others do not. Ordinary blanks stay on the table above.

• Amazon Bedrock — fifteen days of inactivity can end access inside a window measured in months
• Microsoft Foundry — a date that cannot be pushed back, which removes an exception people expect to negotiate
• Gemini API — a date described as the earliest, so it is a floor that can quietly become later
• LTX Studio — a right to replace at any time, which leaves no date for anything to be early against
• Runway — a conversion table can be edited, which ends access with no date and no notice
• Adobe Firefly — a tier restructure ends access with nothing retired and no lifecycle page involved
• PixVerse — a promoted version with no predecessor named, so a line can vanish with nothing to compare

• How access can end before the date
  Once the Legacy period begins, existing customers may lose access after 15 days of inactivityAmazon Bedrock, model lifecycle / recorded 2026-09-22
• Whether a date can be pushed back on request
  Retirement dates are not extendableMicrosoft Foundry, lifecycle and support policy / recorded 2026-09-22
• What a date in that table commits to
  The shutdown dates listed indicate the earliest possible dates on which a model might be retiredGoogle, Gemini deprecations / recorded 2026-09-22
• Published notice
  The pricing page reserves the right to update, modify or replace available models and does not guarantee continued availability of any specific modelthe only one of its kind hereLTX Studio, pricing / recorded 2026-09-12
• Notice before the credit table changes
  No notice period published (as of 2026-09-12)nothing publishedRunway, pricing page / recorded 2026-09-22

5Production that outlasts a model

Model end dates touch “Ending early”; SceneMixer's guides describe how its pipeline treats the models it runs:

Typically 60–120 seconds, always 9:16 vertical, ending on a hook. SceneMixer's episode outlines are generated with that pacing, and setting a project to 9:16 makes every segment vertical (the default is 16:9).

SceneMixer, How to Make ReelShort-Style Dramas with AI — “How long is a ReelShort-style episode?” (read 2026-10-13)

When you edit a sheet (change the hair, swap the coat, add a scar) or generate a state (the drawn blade, the burnt room), the model starts from the existing image and reads your text as what to change.

SceneMixer, Editing a Sheet or Making a State: Write the Change, Not the Whole Picture (read 2026-10-13)

6Sources

Values come from the page the entry is read on: vendor announcements for endings, app pages for menus, both linked from the calendar. What counts as a value is on sourcing. Read 2026-09-12. Other fields: Named replacement, Stored work. All of them: the field list.