Estimate AWS Step Functions costs for Standard and Express workflows.
Last verified: April 2026
Priced per state transition. Best for long-running, auditable workflows.
Number of state transitions in a single workflow execution.
Output will appear here...The Step Functions Cost Estimator calculates monthly costs for AWS Step Functions Standard and Express workflows. Standard workflows charge per state transition while Express workflows charge per execution, duration, and memory. The tool compares both workflow types side-by-side and helps you choose the right one based on execution volume, duration, and orchestration requirements.
Standard workflows charge $0.025 per 1,000 state transitions regardless of duration (up to 1 year). Express workflows charge per execution based on number of requests, duration, and memory consumed, similar to Lambda pricing. Express is cheaper for high-volume, short-lived workflows (under 5 minutes).
A state transition occurs each time Step Functions moves from one state to the next in a Standard workflow. This includes Task, Choice, Parallel, Map, Wait, Pass, and Succeed/Fail states. A workflow with 10 states running 1,000 times generates approximately 10,000 state transitions (actual count depends on Choice branches and Map iterations).
Yes. AWS offers 4,000 Standard workflow state transitions per month free, permanently. Express workflows include 1,000 free requests, 1,000 free GB-seconds, and the first 100 milliseconds of each execution free. This free tier is sufficient for development and low-volume production workloads.
Your team built an order fulfillment pipeline with 12 states that processes 50,000 orders per day. At 12 transitions per order, that is 600,000 daily transitions on Standard. You plug the numbers in and discover Express workflows would save 70% because each order completes in under 30 seconds. You migrate to Express and set up CloudWatch alarms for the 5-minute timeout edge case.
The estimator multiplies your expected state transition count by the per-transition price for Standard workflows. For Express workflows, it calculates cost from request count, duration in 100ms increments, and memory in 64MB increments, then subtracts the free tier allowance. The tool compares both workflow types at your specified volume to show the crossover point.
Express workflows are billed per execution, duration, and memory, but they cap at 5 minutes. If your workflow occasionally exceeds 5 minutes on retries, it silently fails. Always set a Step Functions alarm on ExecutionsFailed for Express workflows.
State transitions in Standard workflows include every Pass, Choice branch evaluation, and Map iteration. A Map state iterating over 1,000 items generates 1,000+ transitions. Use Express workflows for high-iteration Map states to avoid bill shock.
Combine Step Functions with EventBridge Pipes for event-driven orchestration instead of polling SQS from a Lambda step. This eliminates one state transition per poll cycle and reduces overall cost.
Was this tool helpful?
Disclaimer: This tool runs entirely in your browser. No data is sent to our servers. Always verify outputs before using them in production. AWS, Azure, and GCP are trademarks of their respective owners.