Limits and Pricing for Render Workflows

Render bills for the following components of workflows:

If your task runs send network requests over the public internet, that traffic contributes to your workspace's usage of outbound bandwidth.

Compute plans

Each task run executes on one of the following compute plans, which determines its specs and pricing:

Where are starter and standard?

The starter and standard compute plans from the Render Workflows beta have been discontinued in favor of flex.

• The flex plan is now the default for any task that doesn't specify a different plan.
• Any task that sets its plan to starter or standard now automatically uses flex instead.
• The flex plan is billed according to your task run's actual RAM and CPU usage. This results in lower costs for most tasks that previously used starter or standard.
• The flex plan provides up to the same CPU as standard and double the RAM.

• Billing for compute usage is prorated by the second.
  • If a task run executes on the 2c-4g compute plan for a half-hour, Render bills you $0.20, not $0.40.
• You can specify which compute plan to use for each task in your workflow. Learn how.

Need larger workflow compute plans?

Reach out with details about your use case:

Talk to our team

The flex compute plan

The flex compute plan is special: it's billed based on the CPU and RAM a task run actually uses, not the plan's maximum specs (1 CPU, 4 GB RAM). All other compute plans are billed at a fixed rate based on specs.

Pricing for flex is as follows:

If a flex run constantly uses the entirety of its available CPU and RAM, it's billed at the maximum rate of $0.40 / hour. But for tasks that use fewer resources, the rate can be dramatically lower:

Render applies a minimum charge to extremely small flex runs, equivalent to one second of execution at 0.1 CPU and 0.1 GB RAM.

Task state retention

Render temporarily retains the input arguments and return value of each task run to support retries, debugging, and observability. This task state is retained for 30 days.

Retention of task state is billed monthly at $0.25 per GB. Render bills for each task run's state only once (even though task state is often retained across multiple billing periods).

For example, if the combined size of all your task run inputs and return values in a billing period is 200 MB, Render bills you $0.05.

Compute limits

A workflow service has a maximum amount of CPU and RAM it can provision in total and per minute for its task runs:

If a new task run would exceed a compute limit, Render queues it as usual. Queued runs spin up in order as resources become available.

Need to increase these workflow limits?

Reach out with details about your use case:

Talk to our team

Additional limits