Pika parallel generations: 2 on Free, 8 on Creator; Sume by plan

Pika's pricing page lists 2 parallel video generations on Free and Starter, 8 on Creator, and unlimited on Fancy. Sume also limits parallel work by plan, but a job over the limit is accepted and waits as queued; only a full queue returns 429 queue_full.

Pika numbers are from its pricing page and Sume numbers from Generation admission and Errors and credits, all read 2026-10-01.

How many parallel generations does Pika allow?

The pricing table has a row for parallel video generations and another for parallel image and audio generations. Pika lists the video row as follows.

How does Sume set concurrency?

Sume's pricing FAQ defines it plainly: "Concurrency is how many generation jobs can run at the same time." The docs list it per plan, and say it is plan-only: prepaid top-ups do not raise the processing limit.

What happens when I go over the limit on Sume?

Concurrency is a dispatch limit, not a submit limit. A valid job over the limit can still be accepted as queued while queue capacity remains, then moves to processing when a slot opens. When concurrency plus queue is full, submit fails with 429 and code queue_full. Queue capacity defaults to max(3, concurrency_limit × 5).

What should I do about a full queue?

The admission docs suggest canceling queued jobs you no longer need, and retrying with the same idempotency key after capacity opens. A separate 429 rate_limited is abuse protection; back off on retry-after there. For how the two states differ in practice, see queue_full 429 vs a job that stays queued.

Does a bigger balance raise the limit?

No. Per the docs, a top-up changes your balance, not your concurrency. If you need more jobs running at once, the lever is the plan.