Get Started

    Limits and Pricing for Render Workflows

    Render bills for the following components of workflows:

    BillableDescription

    Compute usage

    Render bills for each based on its and duration.

    See details.

    Retention of task state

    Render temporarily retains the input arguments and return value of each to support retries and debugging.

    See details.

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

    Compute plans

    Each executes on one of the following , which determines its specs and pricing:

    Compute PlanSpecs
    Price

    flex

    Up to 1 CPU
    Up to 4 GB RAM

    Varies with CPU/RAM usage (see details)

    starter

    		0.5 CPU
    512 MB RAM    		$0.05 / hour

    standard (default)

    		1 CPU
    2 GB RAM    		$0.20 / hour

    2c-4g
    (Formerly pro)

    		2 CPU
    4 GB RAM    		$0.40 / hour

    2c-8g

    		2 CPU
    8 GB RAM    		$0.70 / hour

    4c-8g
    (Formerly pro_plus)

    		4 CPU
    8 GB RAM    		$1.00 / hour

    4c-16g
    (Formerly pro_max)

    		4 CPU
    16 GB RAM    		$1.50 / hour
    • Billing for compute usage is prorated by the second.
      • If a 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.

    The flex compute plan

    The flex compute plan is special: it's billed based on the CPU and RAM a 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:

    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 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 CPUAvg 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 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 concurrent compute in total and per minute:

    LimitDescription

    Total concurrent compute

    In total, a workflow service's concurrent can use up to 10,000 CPU and 40,000 GB RAM in combined instance specs.

    Per-minute provisioning

    Each workflow service can spin up a maximum amount of new compute per minute. This amount depends on your workspace plan:

    Workspace PlanCPU per minuteRAM per minute
    Hobby16 CPU64 GB
    Pro or higher32 CPU128 GB

    The flex compute plan only counts actual CPU and RAM usage against these limits.

    This means that if you're spinning up "lightweight" flex runs, you can create many more of them per minute than implied by the plan's max specs (1 CPU, 4 GB RAM).

    Compute plans besides flex always count against these limits based on their fixed specs.

    Any triggered in excess of an above limit is queued as usual. Render spins up queued runs in order as resources become available.

    Additional limits

    LimitDescription

    API rate limit

    The Render API's Run task endpoint limits each Render user to 100 requests per minute. Triggering a run through the Render SDK also uses the Render API and therefore counts against this limit.

    Whenever an API request to trigger a run is rate limited, Render returns a 429 error. In this case, Render does not queue the run.

    does not use the Render API, so chained runs do not count against this limit.

    Run duration

    By default, time out after 2 hours. You can extend this to up to 24 hours on a per-task basis.

    Argument size

    The total size of all arguments passed to a single cannot exceed 4 MB.

    Task definitions

    A single workflow service can register a maximum of 500 different .