Durable Workflow Cloud
Managed durable execution
Pay for capacity, not workflow semantics.
Retries, timers, signals, queries, and activity attempts are not separate billing events.
Choose the runtime capacity and availability your application needs.
An isolated place to build and test.
$50/month cap
$0.075/hour while provisioned
Request accessHigh availability for production workflows.
$300/month cap
$0.45/hour while provisioned
Request access$400/month cap
$0.6/hour while provisioned
Request accessMore capacity for growing workloads.
$1500/month cap
$2.25/hour while provisioned
Request access$2000/month cap
$3/hour while provisioned
Request accessUSD, before applicable taxes. Prices are per provisioned runtime. CPU and memory cover Cloud-operated components; your application workers run separately. Cloud Dev remains single-host in either view.
Enterprise and custom plans
Larger dedicated runtimes, memory-intensive workloads, custom regions, SSO, and principal-engineer on-call support. We scope the deployment, availability, and support agreement with you.
Included in every plan
Understand your bill
Choose the capacity you need. No separate workflow-action charges or storage overages.
| Plan | Runtime rate | Monthly cap | Minimum | Included storage |
|---|---|---|---|---|
| Cloud Dev | $0.075/hour | $50 | $2 per active month | 5 GB |
| Cloud Standard | $0.45/hour | $300 | $10 per active month | 25 GB |
| Cloud Multi-Region | $0.6/hour | $400 | $15 per active month | 25 GB |
| Cloud Business | $2.25/hour | $1500 | $50 per active month | 100 GB |
| Cloud Business Multi-Region | $3/hour | $2000 | $75 per active month | 100 GB |
Hourly runtime usage is metered by the minute. Caps and active-month minimums apply per runtime purchase in a UTC calendar month; a month with no provisioned time has no runtime charge. Stripe invoices accrued usage monthly, not your card every hour. Workflow actions have no separate charge. Network is measured but not currently billed; this is not unlimited bandwidth.
Public egress is a per-host rate limit, not a guaranteed throughput or a pooled customer allowance. It includes runtime responses and cross-region replication. Dev backups share this limit; HA plans have a separate managed-backup transfer limit. There is no automatic network overage charge.
Storage is fixed at the included allocation for each plan. There are no paid storage add-ons, automatic storage increases, or storage overage charges. Need more space? Upgrade the entire runtime to a plan with more included storage. Contact us to arrange a plan upgrade or a larger custom runtime; changing regions alone does not increase storage.
Encrypted backups run every six hours, retaining 28 recovery sets. After deprovisioning, recovery copies remain for seven days at no additional charge, then are scheduled for deletion. This is operator-managed disaster recovery, not a pause or self-service restore feature.
Availability
A single isolated host with persistent state and backups. Maintenance and recovery can interrupt service. No uptime SLA.
Three replicated hosts with automatic primary failover. The uptime SLA is 99.99%; a whole-region outage is outside its coverage.
Three regions with replicated state and automatic primary failover. The 99.99% SLA includes loss or isolation of one configured region.
SLA availability is measured at the runtime endpoint over a UTC calendar month. Planned maintenance is not excluded. Customer-hosted worker availability is outside the managed runtime allocation.
Questions
Creating an account or namespace definition does not provision paid capacity. Add a payment method through Stripe, choose a plan, then provision the runtime. Capacity billing begins when the runtime is activated.
No. You run your PHP, Python, or Rust workers on your own infrastructure. The plan covers the managed orchestration runtime, persistence, scheduling, and Cloud-operated services.
Yes. Capacity remains provisioned even when no workflows are running. Deprovisioning stops capacity billing and removes active runtime data and credentials; it is not a pause button. Separately retained disaster-recovery backups do not extend your bill.
Choose a larger runtime plan with more included storage. Storage cannot be purchased separately and never grows automatically. Contact us before reaching your limit to arrange the capacity change; an upgrade requires a real runtime/storage migration, not only a billing change.
SLA plans receive automatic account credits: 10% below 99.99% through 99.9%, 25% below 99.9% through 99.0%, and 100% below 99.0% monthly availability. Cash refunds require review and approval. Cloud Dev has no SLA.
It depends on the workflow, payload size, timers, and activities. Our published benchmark defines a standard workflow so throughput has a concrete meaning. A monthly workflow-action estimate is a capacity comparison, not a billing quota.
Yes. Durable Workflow Server and the SDKs are open source. You operate Server, storage, and Waterline; Cloud plans pay for managed infrastructure and operations.