What changed
Render says Workflows will become generally available on September 1, 2026. On that date, Starter and Standard workflow task plans will automatically move to a new Flex tier priced at $0.20 per active CPU-hour and $0.05 per active GB-hour, with one-second minimum billing at 0.1 CPU and 0.1 GB. Workspace-wide paid concurrency add-ons will disappear in favor of much higher per-workflow resource limits. Render will also begin billing retained workflow task arguments and return values at $0.25 per GB-month.
Why it matters
The change alters both the cost model and the scaling model for developers using Render Workflows as an orchestration layer for background jobs, data pipelines and agents. Waiting on LLMs or external APIs should no longer incur the same fixed-resource charge as active compute on Flex, while teams running multiple workflows no longer have those services competing for one shared paid concurrency pool. The trade-off is a new storage-like charge for retained task state, so workflow debugging and retry data now has an explicit economic footprint.
Flex prices active resources instead of a fixed task size
The new Flex plan gives each task access to as much as 1 CPU and 4 GB of RAM but bills only the CPU and memory the task actively uses. Render says tasks dominated by LLM or external-API waiting can cost up to 70% less under this model. Tasks that need larger predictable allocations can stay on Pro and higher fixed plans, and Render is adding a 2 CPU / 8 GB tier while lowering prices on some larger plans.
Concurrency stops being a workspace-wide paid pool
Today, Workflows uses workspace-wide concurrency limits and sells additional concurrent runs. On September 1, Render will remove those add-ons and replace the model with per-workflow resource limits. Pro workspaces and above can add up to 32 CPU and 128 GB RAM per minute to a workflow, while Hobby gets lower limits. Existing concurrency add-ons are removed automatically and no longer billed.
Task-state retention becomes billable
Render temporarily retains task inputs and return values to support retries and debugging. That retained state will cost $0.25 per GB-month from September 1. This is small for lightweight workflows but becomes relevant when tasks pass large documents, model outputs or structured payloads between steps. Builders should treat payload size and retention as part of workflow design rather than invisible implementation detail.
The migration is automatic, but cost behavior is not identical
Existing Starter and Standard tasks move to Flex automatically. Render says most workloads in its data will cost less, but teams should still model real traces: CPU-heavy tasks may not see the same savings as I/O-heavy agent jobs, and retained-state billing can offset some gains. The useful comparison is total cost per completed workflow, including retries and stored payloads.