Runway Aleph 2.0 vs Gemini Omni Flash edit as a Sora remix swap
Sora's remix endpoint is gone. Runway lists Aleph 2.0 video-to-video at $0.28 per second; Sume's Gemini Omni Flash edit takes video_url at $0.125 per second.

Two practical video-to-video replacements for a Sora remix call are Runway's Aleph 2.0 and gemini-omni-flash-1.1 in edit mode on Sume. Runway lists Aleph 2.0 at $0.28 per second; Sume bills the Omni 720p rate of $0.125 per second, and its edit mode takes a video_url plus a prompt describing the change.
What remix did
OpenAI's guide marked the remix endpoint as deprecated, and the Videos API itself was shut down on September 24, 2026. Remix meant sending a finished video id plus a new prompt. Both options below replace that with a source video you hold yourself, so you need the original file, which is another reason to export your assets now.
The price gap deserves context. Runway's $0.28 per second for Aleph 2.0 and Sume's $0.125 at 720p are different models doing different jobs, so a cheaper edit is only a saving if its output is good enough for the shot. Compare on one clip you care about, not on the rate card.
Side by side
Runway's models page, read 2026-10-07, also lists Gen-4.5 at $0.12 per second and Gen-4 Turbo at $0.05 for generation, which makes a Runway account a viable one-stop alternative if you prefer its tooling. The same page lists Seedance 2.5 from $0.20 per second, so check which vendor's price you are comparing before you compare.
| Property | Runway Aleph 2.0 | gemini-omni-flash-1.1 edit on Sume |
|---|---|---|
| Route | /v1/video_to_video | POST /v1/videos with video_url |
| Price per second | $0.28 | 720p $0.125 billed; 1080p $0.1875; 4K $0.375 |
| Source input | Video | video_url, resolution optional (default 720p) |
| Aspect ratio | Set by Runway | aspect_ratio is rejected on edits |
| Duration | Per second billing | Only a reserve hint, check usage.cost when done |
| Result tracking | SDK helper waits for task output | Poll the job or use callback_url |
What the Sume edit accepts
Edit mode on Sume is limited by what the model sees: up to 10 reference images, up to 3 reference videos of at most 3 seconds each, and a prompt of up to 20000 characters. The prompt can address inputs with tokens such as <IMAGE_REF_0> and <VIDEO_REF_0>. The limits post lists them.
Budgeting an edit
Because the duration on an edit is only a reserve hint, quote per-second rates to your users and read the final charge from the job. Do not multiply the hint by the rate and call it the price. Runway, by contrast, documents per-second pricing for Aleph 2.0 directly on its models page.
For the Sume side, run the edit once at the default 720p and read usage.cost from the finished job. Use that number, not an estimate, when you set a per-edit price for your own users.
Choosing
Pick Runway if you already hold a Runway account and want its editing tooling. Pick Sume if you want the edit to sit behind the same /v1/videos call, key and webhook as your generation jobs. The Sora remix post walks through the request.
Sources
Related posts
More in Comparisons
- Runway API vs Sume: price of a Wan 3 and Seedance 2.5 10-second clip
Runway lists Wan 3 at 5 to 20 credits a second and Seedance 2.5 at 20 to 68, at $0.01 a credit. Here is the 10-second clip price next to Sume's, before the fee.
- Runway API credits to dollars: cost per second and per 100 clips
Runway's API credit is $0.01, so WAN3 is $0.05 to $0.20 per second and Seedance 2.5 is $0.20 to $0.68. Per-clip and 100-clip table, with the Sume comparison.
- Runway Dev usage exception request vs Sume 429 and 402
Runway Dev says higher usage needs an exception request. On Sume a burst hits 429 or 402. What each means for a batch of ad variants and how to retry.
- Runway Dev image_to_video, video_to_video: one Sume route?
Runway Dev names image_to_video, video_to_video and text_to_image paths. Sume's POST /v1/videos infers the mode from your fields. What it changes in ad code.
Written by Sume