Worker crash
Execution state persists. Tasks are retried.
Multi-region & multi-cloud resilience
Orkes Conductor orchestrates your AI agents, workflows and services with durable execution, monitors cluster health, and fails over automatically.
Orkes-hosted or customer-hosted. Your cloud accounts or ours.
Extending the reliability you already trust
Orkes already protects execution through worker failures and availability-zone outages. Multi-region resilience adds recovery in another region or cloud.
Execution state persists. Tasks are retried.
Multi-AZ deployment protects the cluster.
A replica in another region is ready to take over.
Execution can resume in another cloud.
Managed recovery
Orkes monitors cluster health continuously and automatically manages failover. Your agentic workflow resumes on the second cluster.
Illustrative multi-cloud deployment
Serves traffic and runs your agentic workflows.
Services · AI agents · Approvals
Continuously receives state. Ready to take over.
Execution state + configuration
Recovery can be much faster. These are recovery objectives, not guarantees.
Deployment choice
Run across AWS, Microsoft Azure and Google Cloud, in Orkes-hosted or customer-hosted deployments. Orkes manages replication and failover in either model.
Pair clusters in two regions of the same cloud provider.
Pair clusters across cloud providers for recovery beyond a single cloud.
Built for critical workloads
Replication is encrypted end to end between the clusters. Data is encrypted at rest in both locations, in the regions and cloud accounts selected for your deployment.
Multi-region resilience is designed to preserve core workflow performance. Orkes allocates the capacity required for replication and recovery.
Further detail
The agentic workflow resumes on the second cluster using its copy of the execution state. Some in-flight tasks may be retried. Business actions, such as issuing a payment, should handle retries without duplicating those actions.
Both clusters are running and monitored by Orkes. The primary serves traffic and executes workflows. The replica continuously receives execution state and configuration, ready to take over automatically. Orkes also restores an unhealthy replica to health.
Running execution state, workflow and task definitions, prompts, schedules, secrets, integrations, users and access configuration. Execution history and audit logs are replicated from the time the clusters are paired.
Applications and workers using Orkes’s multi-region endpoint keep the same address. Orkes updates routing to the active cluster.
Your workers and external dependencies need their own availability arrangements. Workers must be able to reach the active Orkes cluster, and services such as databases and model providers must remain accessible to your application.
The 99.99% uptime SLA applies to the paired deployment. A single multi-AZ cluster provides a 99.9% uptime SLA. Recovery time and data-loss objectives are separate targets.
The capability is available as an add-on for enterprise deployments. Contact Orkes for pricing and further information. See enterprise plans.
Build agentic workflows that connect AI agents, business services and human decisions. Run your agents and business workflows on the same durable execution platform.