Switching clouds? Get up to $10K in credits + hands-on help.

Apply now

Blog / Product

Upcoming changes to Workflows pricing

August 10, 2026

· Azzam Aijazi

When we launched Render Workflows in beta, we expected to learn and adjust. Your feedback showed that pricing was too high for many workloads, and workspace-wide concurrency limits made it hard to scale.

On September 1, as part of making Workflows generally available, we're updating our pricing to address that feedback. We’re introducing a new workflow-specific compute plan, Flex, that bills only for the resources your tasks actively use. We’re also replacing the workspace-wide concurrency limit with dramatically higher per-workflow resource limits and introducing billing for temporary task state retention.

Based on our data, the vast majority of workloads will cost less under the new model.

Pricing based on active compute

A new workflow-specific compute plan, Flex, will replace both Starter and Standard. The Flex plan will provide up to 1 CPU and 4 GB RAM per task (double the RAM of Standard), and will bill only for the resources your task actively uses:

  • $0.20 per active CPU-hour
  • $0.05 per active GB-hour

Each task run will be billed at a minimum of just one second at 0.1 CPU and 0.1 GB RAM.

Tasks that spend significant time waiting on LLMs or external APIs should cost up to 70% less under Flex.

Larger compute plans (Pro and higher) will remain available and keep their fixed billing model. We’re also adding a 2 CPU / 8 GB plan and lowering prices for the existing Pro Max (4 CPU / 16 GB) and Pro Ultra (8 CPU / 32 GB) plans.

Per-workflow concurrency with dramatically higher limits

Per-workflow resource limits will replace the current workspace-wide concurrency limit. This means your different workflows will no longer compete over a shared resource pool.

With a Pro workspace or higher, a workflow can add up to 32 CPU and 128 GB RAM per minute (16 CPU / 64 GB with a Hobby workspace). All of a single workflow’s concurrent task runs can use up to a total of 10,000 CPU and 40,000 GB of RAM.

If you currently pay for a concurrency add-on, we’ll remove it automatically on September 1, and you won’t be charged for it going forward. For teams running more than one workflow service, the new model makes it easier to isolate workloads and scale them independently.

Billing for task state retention

The input arguments and return values of your workflow tasks are temporarily retained to help you retry or debug the run. We will begin billing for this task state retention at a monthly rate of $0.25 per GB.

What happens next

If you currently use Workflows, no action is required at this time. On September 1, workflow tasks that run on the Starter or Standard compute plans will automatically move to Flex, and your September invoice will reflect these changes.

If you have questions about how the pricing changes apply to your workloads, you can reach out to Render Support at any time.

Thank you for helping shape Render Workflows during beta. Your feedback directly informed these changes, and we’re excited to continue building with you as Workflows enters general availability.