Runway 5 vs 15 parallel generations vs Sume queueing

Runway's Standard plan allows 5 parallel generations and Pro allows 15, with Pro also adding unlimited 4K upscaling. Sume does not sell parallel slots by credit tier. It accepts valid jobs as queued and runs as many as your plan's processing concurrency allows, and every job reports a USD cost.

Runway's plan numbers

These figures come from the Runway pricing page, read on 2026-10-03. Plan prices shown are the annual-billing monthly rates.

How Sume handles concurrency

Sume separates four controls: processing concurrency, queue capacity, submit rate limits and balance. Concurrency is a dispatch limit, not a submit limit. A workspace at its limit still accepts valid jobs into queued while queue capacity remains, and workers move them to processing as slots free up. Concurrency is plan-only; prepaid top-ups do not raise it.

The documented defaults per plan follow. The dashboard Concurrency tab and the generation_limits.concurrency_limit field are the source of truth, so prefer them over this table.

What full looks like

When accepted capacity is full, a paid submit fails with 429 queue_full. That is different from 429 rate_limited, which means too many requests in the window. Retry with backoff, honor retry-after when present, and reuse the same Idempotency-Key so a retry returns the original job instead of billing twice.

Cost shows up per job

Video jobs on Sume bill from a workspace USD balance, reserved on submit at provider list price times 1.25. The poll response carries usage.cost, the Sume billable amount. That makes a batch comparable by summing receipts rather than converting credits.

The two models are not interchangeable: a credit plan buys a pool and a parallel cap together, while Sume ties concurrency to the plan and cost to each job. Compare your expected jobs per hour against the processing column, not against the credit count.