Two entries read against each other on one column

A side-by-side page takes one column and two entries whose published answers diverge, then sets the two readings against each other without scoring either. As of 2026-09-12.

Two entries can both be recorded as compliant with the same column and still leave a production in completely different positions. One counts a notice period in months, another states that the date cannot move. Reading them apart makes both look reasonable; reading them together is where the consequence appears.

Pairs are chosen for divergence, not for popularity. Where two entries publish the same nothing, there is no page: the register already records that once per entry and repeating it as a comparison would be padding.

Nothing here ranks the two. Where one publishes more, that is stated as more published rather than as better, because the column measures disclosure and the reader is the one who knows what their production needs.

1The pairs

• Foundry and Bedrock — Both publish a notice period before a model goes.
• Foundry and the Gemini API — One entry commits to a period counted in days.
• Bedrock and the Gemini API — One entry can end access after fifteen days of disuse.
• Foundry and Sora — One entry publishes a notice period before anything is scheduled.
• LTX Studio and SceneMixer — Neither publishes a notice period.
• LTX Studio and Bedrock — One page states that no continued availability is guaranteed.
• Wan-AI and Foundry — One entry publishes weights that keep running after a withdrawal.
• Wan-AI and Sora — One entry's output was never in anybody's product.
• Pika and invideo AI — One entry carries a single house model and controls its schedule.
• Pika and Adobe Firefly — One entry names the same model on every plan.
• Kling AI and Hailuo AI — One maker sells two generations on a single membership.
• Luma and Vidu — One entry lists two house generations beside licensed models from several makers.
• fal and SceneMixer — On one entry nothing runs unless a call names it.
• fal and Pika — One entry requires every call to name a model from a priced list.
• Runway and SceneMixer — Both name the models they sell.
• Runway and Luma — Both put house and licensed models on one table with no marking, so two failure modes are presented in the same type by two different sellers.
• Firefly and Kling AI — One entry gates partner models by tier, so the plan decides the engine.
• The Gemini API and Sora — One maker keeps a standing table of dated identifiers.
• invideo AI and Luma — One entry aggregates six makers and builds no model of its own.
• PixVerse and Vidu — Both promote a numbered house generation and neither addresses the versions before it.
• Bedrock and Wan-AI — One entry publishes a window with a clause that can shorten it.
• Hailuo AI and Pika — Both publish one model line.
• SceneMixer and Pika — One entry names the model and resolution a new project starts on.
• Foundry and Runway — One entry publishes stages that decide what a retirement owes.
• The Gemini API and LTX Studio — One entry publishes dates described as the earliest a model might go.
• Stages and states — One entry publishes two stages that set the notice owed.
• Sora and the listing — One entry used a single undefined word on two dates.
• A right and an order — Neither publishes a state.
• invideo AI and fal — One entry bundles six makers into a subscription with no default stated.
• Wan-AI and fal — Neither entry holds material, for different reasons.

A pair earns a page when the two entries have each published something on the same column and the two statements do not agree.

Other notices: Apps, Models, Fields, Questions, Terms, Learn, Data. Where each line comes from is set out on the sourcing page.