# Orkes

> Orkes is the enterprise platform for building highly reliable applications and AI agents on Conductor — a battle-tested, open-source durable workflow engine, available fully managed (Orkes Cloud) or self-hosted.

Orkes Conductor orchestrates production workflows, distributed applications, microservices, APIs, human approvals, and AI agents with durable execution, determinism, and full operational visibility. It is the enterprise version of Conductor OSS, the actively maintained open-source durable workflow engine.

## Product

- [Orkes Platform](https://orkes.io/platform): One platform for building and running both AI agents and durable workflows.
- [Orkes Cloud](https://orkes.io/cloud): Fully managed Conductor — dedicated clusters on AWS, Azure, or GCP, or in your own environment.
- [What is Conductor?](https://orkes.io/what-is-conductor): Overview of Conductor, the open-source (Apache 2.0) durable workflow orchestration engine.
- [Orkes vs. Conductor OSS](https://orkes.io/platform/conductor-oss-vs-orkes): How enterprise Orkes Conductor extends the open-source Conductor project.
- [Pricing](https://orkes.io/pricing): Orkes Cloud plans, including the enterprise free trial.
- [Get Started](https://orkes.io/get-started): Start building with Orkes Cloud or the free Conductor Developer Edition.

## Capabilities

- [Conductor Use Cases](https://orkes.io/use-cases): Company workflows built with Conductor across 249 organizations.
- [Agentic Workflows](https://orkes.io/use-cases/agentic-workflows): Build production AI agents with durable execution, guardrails, and human-in-the-loop.
- [AI & LLM Chaining](https://orkes.io/use-cases/ai-and-llm-chaining): Orchestrate multi-step LLM pipelines and tool calls reliably.
- [Microservices Orchestration](https://orkes.io/use-cases/microservices-orchestration): Coordinate distributed microservices with durable, observable workflows.
- [Realtime API Orchestration](https://orkes.io/use-cases/api-orchestration): Compose and orchestrate APIs into reliable end-to-end flows.
- [Event-Driven Architecture](https://orkes.io/use-cases/event-driven-architecture): Durable workflows driven by events and message queues.
- [Human Workflow Orchestration](https://orkes.io/use-cases/human-workflow-orchestration): Insert human approvals and tasks into automated workflows.
- [Process Orchestration](https://orkes.io/use-cases/process-orchestration): Model and monitor end-to-end business processes across people, systems, and services.

## By Industry

- [Financial Services](https://orkes.io/industries/financial-services): Secure, compliant workflow orchestration for financial services.
- [Media & Entertainment](https://orkes.io/industries/media-and-entertainment): Enterprise orchestration for media pipelines.
- [Telecommunications](https://orkes.io/industries/telecommunications): Workflow orchestration for telecom provisioning and billing.
- [Healthcare](https://orkes.io/industries/healthcare): Expedite patient care with durable healthcare workflows.
- [Shipping & Logistics](https://orkes.io/industries/shipping-and-logistics): Long-running, durable workflows for inventory and logistics.

## Compare

- [Orkes vs. Temporal](https://orkes.io/compare/orkes-conductor-vs-temporal): How Orkes Conductor compares to Temporal.
- [Orkes vs. Camunda / BPMN](https://orkes.io/compare/orkes-conductor-vs-camunda-bpmn): How Orkes Conductor compares to Camunda and BPMN engines.
- [Orkes vs. LangChain](https://orkes.io/compare/orkes-conductor-vs-langchain): How Orkes Conductor compares to LangChain for agent orchestration.
- [Orkes vs. n8n](https://orkes.io/compare/orkes-conductor-vs-n8n): How Orkes Conductor compares to n8n.

## Resources

- [Documentation](https://orkes.io/content/): Full Orkes Conductor documentation.
- [Documentation — LLM index](https://orkes.io/content/llms.txt): Machine-readable index of the documentation.
- [Documentation — full text dump](https://orkes.io/content/llms-full.txt): Complete documentation as a single machine-readable file.
- [Developers](https://orkes.io/developers): SDKs, guides, and developer resources.
- [Blog](https://orkes.io/blog): Tutorials and insights on workflow orchestration and AI agents.
- [Whitepapers](https://orkes.io/whitepapers): In-depth technical and strategic whitepapers.
- [Customers](https://orkes.io/customers): Case studies from companies building on Orkes.
- [Events](https://orkes.io/events): Webinars, meetups, and upcoming events.

## Company

- [About Us](https://orkes.io/about-us): About Orkes.
- [In the News](https://orkes.io/in-the-news): Press and media coverage.
- [Security](https://orkes.io/security): Security and compliance posture.
- [Legal Hub](https://orkes.io/legal): Legal, privacy, and terms.

## Recent blog posts

- [How Agents and Workflows Call Each Other in Conductor](https://orkes.io/blog/how-agents-and-workflows-call-each-other-in-conductor): Agents reason, workflows execute. Here's exactly how to wire a workflow behind an agent's tool calls, and an agent into a workflow's own tasks, with worked examples of both.
- [Everything you need to build workflows as code in Conductor](https://orkes.io/blog/building-your-workflows-as-code): Your Guide to Building, Running, and Observing Conductor Workflows as Code
- [Testing With Live Agent Runtimes in Conductor](https://orkes.io/blog/testing-with-live-agent-runtimes): Mocks catch what you scripted. Live evals catch what you didn't.
- [Introducing the AGENT task: Calling AI Agents from Your Conductor Workflows](https://orkes.io/blog/introducing-agent-task): Learn how the AGENT task lets you call AI agents from Conductor workflows with built-in retries, durability, and support for multi-turn conversations.
- [Conductor Now Runs Agents Alongside Your Workflows, on the Same Durable Engine](https://orkes.io/blog/conductor-now-runs-agents-alongside-your-workflows): Agents and workflows now run on the same durable engine so agents inherit everything that's made Conductor workflows reliable in production for years.
- [Testing Workflow Routing and Agent Behavior in Conductor](https://orkes.io/blog/testing-workflow-routing-agent-behavior-conductor): Debugging agent output sucks. Testing agent logic rocks.
- [Agents on Conductor — Architecture for Production AI](https://orkes.io/blog/agents-on-conductor-architecture-for-production-ai): Separating Brain from Execution.
- [Turn Any Function Into a Workflow Step: Build Your First Orkes Conductor Worker](https://orkes.io/blog/build-first-orkes-conductor-worker): A step-by-step tutorial for building an Orkes Conductor worker: register a task definition, write the worker, and wire it into a complete workflow with branching.
- [What Are Workers in Orkes Conductor? How Your Own Code Fits Into a Workflow](https://orkes.io/blog/what-are-workers-orkes-conductor): What is a worker in Orkes Conductor? Learn how workers let you run your own code as a step in a workflow, how polling works, and when to write one.
- [How to Build a UI Screenshot-to-Code AI Agent](https://orkes.io/blog/how-to-build-a-screenshot-to-react-ai-agent): Build an AI agent that turns UI screenshots into working React + TypeScript components. Drop in a design, get back clean, Tailwind-styled code in seconds.
- [What Is Loop Engineering?](https://orkes.io/blog/what-is-loop-engineering): Loop engineering is building a loop around your agent so the agent can reprompt itself without you needing to do it. but you still need to keep yourself in the picture.
- [Building Durable Loops with Conductor, Part 1: Why Agentic Loops, and Why Now?](https://orkes.io/blog/building-durable-loops-with-conductor-part-1): Part one of a series on durable loops. Why agentic systems are loops, why naive loops fail as tasks get longer, and what makes a loop durable, grounded in a working Conductor OSS example.
- [How to Reuse Workflows Inside Other Workflows in Orkes Conductor](https://orkes.io/blog/how-to-reuse-workflows-inside-other-workflows-in-orkes-conductor): Every time you copy workflow logic into a new workflow, you create a maintenance problem. Here's how the Sub Workflow task solves it.
- [How to Connect an MCP Server to Your AI Agent (Without Leaking API Keys)](https://orkes.io/blog/how-to-connect-an-mcp-server-to-your-ai-agent): Wiring an MCP server into an agent usually means scattering API keys across every process that runs it. How to connect MCP tools with Conductor and keep the credentials on the server.
- [How to Process a List of Items in Parallel in Orkes Conductor](https://orkes.io/blog/how-to-process-a-list-of-items-in-parallel-in-orkes-conductor): You have a workflow that needs to process a list of items and doing them one by one is too slow. Here's how the DYNAMIC_FORK task solves it.