Shared credits per seat vs one Sume workspace balance and keys

Runway's Team plan, per its Sep 4, 2026 changelog entry, adds 6,900 credits a month for every seat to one shared pool, for up to nine people with 1TB of storage. Sume does not price by seat in the pages cited here: API keys are workspace-scoped, spending comes from the workspace USD balance, and generation concurrency is set by plan.

Vendor text is from the Runway changelog as read 2026-10-01. Sume facts are from Authentication and Generation admission.

How do the two models differ?

Where do API keys live in Sume?

Keys are created in the API Keys dashboard and are workspace-scoped. Sume resolves the workspace, owner, and key metadata from the key itself. The docs say not to put workspace_id, owner_user_id, or user_id in public API request bodies. Every run made with a key therefore charges that key's workspace. See which wallet does a run charge.

What does adding more people change for concurrency?

Nothing, going by the docs: generation concurrency is plan-only, and prepaid top-ups do not raise the processing limit. Extra jobs wait in queued while capacity remains. Spend and throughput are separate controls.

How should a team split spend?

Within one workspace the balance is shared by everyone whose jobs run on its keys, and the video docs say amounts are reserved from that balance on submit. If you need separate budgets, the documented unit is the workspace, so use separate workspaces and keys. Keep each key in a server-side environment variable, as the authentication page advises.