Skip to main content
Burst is available on Enterprise plans. It is enabled per workspace by your account team; contact sales to turn it on.
Every Enterprise workspace includes a fixed number of concurrent workflow slots (20 by default). Burst lets the workspace run above that number when a batch lands, without buying a higher permanent cap. You set one extra cap for the workspace, and it applies to each burst-eligible workflow type separately: with a +30 cap, up to 30 extra avatar renders and up to 30 extra video translations can run at the same time. Only the workflows that actually run above the included slots are billed at the burst rate. Burst is shared across the web app and the API.

​
Turn on burst

  1. Open Usage in the API dashboard. Under Capacity, the Concurrency tile shows your included slots.
  2. Click Set up burst, choose the extra cap (+5 to +50 workflows), and accept the rate notice.
  3. Save. The tile now reads 20 + 30 with a Burst chip, and Manage burst lets you change the cap or turn burst off at any time.
Workspace admins can also see included and burst capacity under Settings → Usage & History.

​
How burst is billed

A workflow takes a slot when it is admitted and holds it until it completes. If every included slot for its type is busy at admission, the workflow runs in a burst slot and its whole render is billed at the burst rate: the duration is billed to the second as usual, then the 1.5× is applied and rounded up to the next whole quota unit. Workflows admitted into an included slot bill at the normal rate even while others are bursting. You only pay the premium for workflows that actually burst. Burst covers full avatar renders and video translations. Segment renders and free regenerations run in the included slots at the normal rate, and Video Agent sessions keep their own concurrency limit.

​
See what burst cost you

Every burst workflow is tagged Burst in the Activity tab, next to its credits. While burst is on, the Usage sidebar shows a Burst panel with the premium credits and the number of burst workflows for the selected period.

​
API behavior

With burst on, POST /v3/videos and POST /v3/video-translations each accept requests up to included + extra concurrent workflows of their own type, so a +30 cap allows up to 50 avatar renders and up to 50 translations at once. Requests beyond that total return 429 Too Many Requests with a Retry-After header, the same as any concurrency limit. Batch endpoints such as POST /v3/videos/batch queue their items through the same slots.