Limits and Pricing for Render Workflows
Render bills for the following components of workflows:
| Billable | Description |
|---|---|
|
Compute usage |
Render bills for each task run based on its instance type and duration. |
|
Retention of task state |
Render temporarily retains the input arguments and return value of each task run to support retries and debugging. |
If your task runs send network requests over the public internet, that traffic contributes to your workspace's usage of outbound bandwidth.
Instance types (compute specs)
Each task run executes on one of the following instance types, which determines its compute specs and pricing:
| Instance Type | Specs | Price |
|---|---|---|
|
| 1 CPU 4 GB RAM |
Varies with CPU/RAM usage (see details) |
|
| 0.5 CPU 512 MB RAM | $0.05 / hour |
|
| 1 CPU 2 GB RAM | $0.20 / hour |
|
| 2 CPU 4 GB RAM | $0.40 / hour |
|
| 4 CPU 8 GB RAM | $1.00 / hour |
|
| 4 CPU 16 GB RAM | $2.00 / hour |
- Billing for compute usage is prorated by the second.
- If a task run executes on the
proinstance type for a half-hour, Render bills you $0.20, not $0.40.
- If a task run executes on the
- You can specify which instance type to use for each task in your workflow. Learn how.
The flex instance type
The flex instance type is special: it's billed based on the CPU and RAM a task run actually uses, not the instance's full specs (1 CPU, 4 GB RAM). All other instance types are billed at a fixed rate based on specs.
Pricing for flex is as follows:
| Resource | Price | Notes |
|---|---|---|
|
CPU | $0.20 / CPU-hour |
Measured as cumulative virtual CPU time over the task run's full duration |
|
RAM |
$0.05 / GB-hour |
Sampled multiple times per second |
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:
| Avg CPU | Avg RAM | Flex price |
|---|---|---|
|
0.1 |
0.2 GB |
$0.02 + $0.01 = $0.03 / hour |
|
1 |
1 GB |
$0.20 + $0.05 = $0.25 / hour |
|
1 |
4 GB |
$0.20 + $0.20 = $0.40 / hour (Full usage) |
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.
Provisioning limits
Each workflow service can provision up to a maximum amount of compute per minute and in total:
| Limit | Description |
|---|---|
|
Per-minute provisioning |
The amount of compute each workflow service can provision per minute depends on your workspace plan:
You can spin up any combination of task runs that total at most the limits above. Task runs on the This means that if you're spinning up "lightweight" Instance types besides |
|
Total provisioning |
Regardless of your workspace plan, a workflow service's active runs cannot exceed 10,000 CPU or 40,000 GB RAM in total instance specs. |
Any task run triggered in excess of a provisioning limit is queued as usual. Render spins up queued runs in order as resources become available.
Additional limits
| Limit | Description |
|---|---|
|
Argument size |
The total size of all arguments passed to a single task run cannot exceed 4 MB. |
|
Run duration |
By default, task runs time out after 2 hours. You can extend this to up to 24 hours on a per-task basis. |
|
Task definitions |
A single workflow service can register a maximum of 500 different tasks. |
