Runway launches Aleph 2.0 API for 30-second 1080p multi-shot edits

• runwayml's launch post says Aleph 2.0 is now in the Runway API for precise video editing, with support for up to 30 seconds of 1080p footage across multi-shot sequences.
• Runway's API changelog adds the implementation details missing from the tweet: aleph2 runs on the video-to-video endpoint, accepts 2 to 30 second inputs, and supports up to five timestamped keyframe images.
• The main API docs frame Aleph 2.0 as editing existing videos with text prompts and keyframe images, which puts it closer to programmable post-production than a one-shot generator.
• In a same-day hands-on post, icreatelife's Firefly test showed Aleph 2 running inside Adobe Firefly, alongside Gen Fill, Precision Flow, Markup, Nano Banana 2, and GPT Image 2 in one workflow.
• Runway's pricing page lists aleph2 at 28 credits per second with a 56 credit minimum, while Runway's model list shows the model as video plus text or image in, video out.

Runway already has the developer portal, the docs homepage now sends visitors straight to Aleph 2.0, and the changelog entry quietly adds the useful bits: timestamped keyframes, a five-image cap, and a deprecated aleph2_alpha alias that still works. Then icreatelife's Firefly clip turned the launch into a broader workflow story by showing the model inside Adobe's tool stack on the same day.

Runway's public pitch is narrow and useful: edit up to 30 seconds of 1080p video across multi-shot sequences while changing only selected elements. That is the part creative-tool builders care about, because it describes controlled edits, not full-scene regeneration.

The official API documentation uses nearly the same framing and adds one more clue about how Runway wants developers to use it: "edit existing videos with text prompts and keyframe images." In practice, that makes Aleph 2.0 an editing endpoint that can sit inside larger review, approval, or remix flows.

The tweet only mentions multi-shot 1080p editing. Runway's API changelog fills in the mechanics.

• Input video length: 2 to 30 seconds
• Optional guidance images: up to 5 keyframes
• Keyframe placement: specific timestamps
• Endpoint: video-to-video
• Moderation: optional content moderation settings

That combination is the real product surface. Timestamped keyframes mean the API is set up for shot-level steering, not just broad prompt nudges.

The first interesting reaction did not come from a developer demo. icreatelife's post showed Aleph 2 running inside Adobe Firefly and argued that Adobe's advantage is the environment around the models, not any single model.

The stack named in that post:

• GenFill
• Precision Flow
• Markup
• Nano Banana 2
• GPT Image 2
• AI video editing models, including Aleph 2

That is a better read on the launch than the raw API spec alone. Aleph 2.0 is now a programmable editing model from Runway, but the same-day creator interest was already about where it plugs into end-to-end creative software.

Runway's pricing page lists aleph2 at 28 credits per second with a 56 credit minimum per generation. Its model list classifies aleph2 as video plus text or image in, video out.

One small but useful migration note sits in the changelog: the old aleph2_alpha identifier still works as a deprecated alias. That means existing prototypes do not need a same-day break-fix just because Runway moved the model into its main API surface.