Watch: There is no self-serve paid tier between free and...
Orkes
Orkes is the enterprise platform built on Netflix's open-source Conductor engine, providing durable workflow and agent orchestration underneath frameworks like...
MonthlyFree Developer EditionAnnualEnterprise custom (contact sales)
Best plan
Free Developer Edition
Risk: There is no self-serve paid tier between free and...
Editorial · no paid placements
Should you use it?
Orkes is the enterprise platform built on Netflix's open-source Conductor engine, providing durable workflow and agent orchestration underneath frameworks like LangGraph and CrewAI rather than competing with them. Conductor core is open source and free; Orkes' own pricing is free Developer Edition (non-production) or custom-quoted Enterprise, verified July 2, 2026. Pick it when you need durable execution, human-in-the-loop approvals, and governance at production scale. Skip it if you want a published self-serve price or a no-code-first builder.
- Buy ifEngineering teams running Netflix Conductor OSS who want managed hosting and enterprise governance
- PickFree Developer Edition; Enterprise custom (contact sales)
- Skip ifSolo developers or small teams wanting a self-serve paid tier with a published price
Plan guidance
What to buy
Free / Custom
There is no self-serve paid tier between free and...
Current pricing source: Source
Fit
Use it for this, skip it for that
Best for
- Engineering teams running Netflix Conductor OSS who want managed hosting and enterprise governance
- Durable execution underneath agent frameworks like LangGraph, CrewAI, or OpenAI Agents SDK
- Regulated or mission-critical workflows needing human-in-the-loop approvals and audit trails
- Polyglot teams needing Java, Python, Go, JS/TS, or C# SDKs against one orchestration engine
Avoid if
- Solo developers or small teams wanting a self-serve paid tier with a published price
- No-code builders who want a visual canvas as the primary interface (n8n fits better)
- Teams that want a single opinionated agent framework rather than an execution layer underneath one
- Watch out
- There is no self-serve paid tier between free and Enterprise: teams that outgrow the non-production Developer Edition go straight to a sales-quoted contract with no published floor price. Budget for a sales cycle, not a credit-card checkout.
Recent changes
Only what affects the decision
- Developer Edition / Enterprise
Initial verification. No published dollar tiers exist between the free, non-production Developer Edition and custom-quoted Enterprise. 14-day Enterprise trial available
Source - Series B
Led by AVP with Prosperity7 Ventures joining; Nexus Venture Partners, Battery Ventures, and Vertex Ventures US returned. Follows a 2024 Series A ($20M) and 2022 seed ($9.3M)
Source
Alternatives
Best swaps
Microsoft's open-source agentic AI engine, merging Semantic Kernel and AutoGen, now sitting beside the Work IQ, Foundry, Copilot
Free (open source) · 9/10LangfuseOpen-source LLM engineering platform for observability, prompt management, evals, datasets, and OpenTelemetry tracing. ClickHous
$0 free / $29 Core / $199 Pro / $2,499 Enterprise · 8.8/10LangGraphLangChain's low-level orchestration runtime for long-running, stateful AI agents. MIT-licensed Python and JavaScript libraries;
$0 library / $39 Plus / LCU/LSU usage meters · 8.8/10Proof and score mathVerified Jul 2
Proof
Why this recommendation is trusted
- Source
- Registered source
- Freshness
- Review due
- Confidence
- Low confidence
- Verified
- Review
- Volatility
- Volatile
Stale source orkes-pricing.
Editorial score
Unweighted average of 4 axes · confidence high
- Utility8/10
How much real work it can do for a competent operator, end to end.
- Value6/10
What you get for the dollar relative to the closest alternative.
- Moat7/10
How hard it would be for a competitor to replicate the underlying advantage.
- Longevity8/10
How likely the product is to still be best-in-class 24 months out.
Verified facts
- Best ForBest for engineering teams that need durable, code-first execution underneath AI agents and business workflows, especially teams already running or considering Netflix's open-source Conductor and wanting enterprise governance, observability, and SLAs on top of it.
- Pricing AnchorNo public dollar tiers. Developer Edition is free and feature-rich (all Conductor OSS features plus enterprise features, pre-built templates, community support) but explicitly not for production: no SLA, limited scalability, rate limits. Enterprise is custom-quoted with up to 99.99% availability SLA, dedicated Technical Account Manager, and Orkes-hosted or customer-hosted (AWS, Azure, GCP, on-prem) deployment. A 14-day Enterprise trial is available via signup.
- Watch Out ForThere is no self-serve paid tier between free and Enterprise: teams that outgrow the non-production Developer Edition go straight to a sales-quoted contract with no published floor price. Budget for a sales cycle, not a credit-card checkout.
- FundingOrkes closed a $60M Series B in April 2026, led by AVP with new investor Prosperity7 Ventures and existing investors Nexus Venture Partners, Battery Ventures, and Vertex Ventures US. That follows a $20M Series A (2024) and a $9.3M seed/stealth round (2022), putting cumulative disclosed funding near $90M.
Full review notesLong-form details, FAQ, and source history
Orkes is the commercial platform built by the original creators of Netflix’s Conductor, the open-source workflow orchestration engine Netflix released in 2016. The founding team (Jeu George, Viren Baraiya, Boney Sekh, and Dilip Lukose) left Netflix, reunited in 2021, and launched Orkes out of stealth in February 2022 to offer a managed and enterprise-hardened version of the same engine.
In 2026 Orkes repositions Conductor as “the operating system for AI agents and workflows”: a durable, code-first execution layer that sits underneath agent frameworks like LangGraph, CrewAI, OpenAI Agents SDK, and Google ADK rather than competing with them. Teams keep their agent framework of choice for reasoning and tool calls, and route the actual execution, retries, state, and human approvals through Conductor.
System Verdict
Pick Orkes if you’re already running (or seriously considering) Conductor and need production governance on top. Durable execution, human-in-the-loop pauses, event-driven triggers, and audit trails are the core value, backed by SDKs in Java, Python, Go, JavaScript/TypeScript, and C#.
Skip it if you want a published self-serve price or a no-code-first canvas. There is no dollar figure between the free, non-production Developer Edition and a custom-quoted Enterprise contract. Teams that want to swipe a card and scale should look at n8n or stay inside a single agent framework’s own hosted layer.
Commercial reality: Conductor itself is open source and free to self-host from GitHub. Orkes’ own value-add, managed hosting plus enterprise features, is free only in the non-production Developer Edition; every production deployment goes through a sales-quoted Enterprise agreement. Orkes raised a $60M Series B in April 2026, so expect continued platform investment rather than an imminent shutdown risk.
Key Facts
| Company | Orkes, Inc., founded 2021, launched from stealth February 2022 |
| Founders | Jeu George (CEO), Viren Baraiya (co-CTO), Boney Sekh (co-CTO), Dilip Lukose (CPO), all original Netflix Conductor architects |
| Core engine | Conductor, open source, originally created at Netflix (2016) |
| Latest funding | $60M Series B, April 2026, led by AVP; ~$90M raised cumulatively since 2022 |
| SDKs | Java, Python, Go, JavaScript/TypeScript, C# |
| Positioning | Durable execution layer underneath agent frameworks (LangGraph, CrewAI, OpenAI Agents SDK, Google ADK), not a replacement for them |
| Deployment | Orkes-hosted (cloud) or customer-hosted (AWS, Azure, GCP, on-prem, dedicated VPC/VNet) |
| Free tier | Developer Edition: all Conductor OSS + enterprise features, no SLA, not for production |
| Paid tier | Enterprise only, custom-quoted, up to 99.99% SLA, dedicated TAM |
| Named customers | Twilio, LinkedIn, Quest Diagnostics, United Wholesale Mortgage, Woodside Energy, per company materials |
What it actually is
Conductor is a workflow orchestration engine: you define workflows as JSON/code, and Conductor tracks state, retries failed steps, persists progress across restarts, and resumes long-running processes that can span minutes, hours, or days. Netflix built it internally to coordinate microservices and open-sourced it in 2016; it has since become one of the more widely deployed workflow engines outside the big cloud vendors’ native offerings.
Orkes is the company, not a fork: it maintains the open-source Conductor project and layers a hosted/enterprise product on top, adding governance, security, observability, SLAs, and support that the raw OSS project doesn’t provide on its own.
For 2026’s AI wave, Orkes repositions the same durable-execution primitives for agents specifically: pausing a workflow for human approval before an agent takes a risky action, retrying a failed tool call without losing state, and giving compliance teams an audit trail of what an agent actually did. The pitch is explicitly “bring your own agent framework”: LangGraph, CrewAI, OpenAI Agents SDK, or Google ADK handle the reasoning and tool-calling; Conductor/Orkes handles the durable, governed execution around it.
When to pick Orkes
- You’re already on Conductor OSS. Orkes is the natural upgrade path from self-hosted Conductor to managed hosting with enterprise support, without a rewrite.
- Durable execution across long-running or failure-prone workflows. Multi-step agent chains that must survive restarts, retries, and partial failures fit Conductor’s core design better than a stateless framework loop.
- Human-in-the-loop governance is a requirement, not a nice-to-have. Regulated industries (finance, healthcare, energy) need pause-for-approval steps and audit trails before an agent acts.
- Polyglot engineering org. Native SDKs in Java, Python, Go, JavaScript/TypeScript, and C# mean teams aren’t locked into a single language’s agent ecosystem.
- You want the orchestration layer decoupled from the agent framework. If the team expects to swap LangGraph for CrewAI (or vice versa) later, keeping execution in Conductor avoids re-platforming the durability layer too.
When to pick something else
- Self-serve pricing with a published dollar figure: n8n. Community self-host is free, hosted plans start around published Starter/Pro pricing, no sales call required to get started.
- A single opinionated Python/JS agent framework without a separate execution engine: LangGraph for stateful graph-based agents, or CrewAI for role-based agent crews.
- No-code-first visual automation for smaller teams: n8n again, or Zapier-class tools, where the canvas is the product rather than a code-first SDK.
- You want to avoid any sales-quoted pricing entirely. Orkes has no self-serve paid tier; if that’s a dealbreaker, an open-source-only, self-hosted Conductor deployment (unsupported) or a framework with transparent usage-based billing is a better fit.
Pricing
Verified 2026-07-02 via orkes.io/pricing:
| Plan | Price | What’s included | Who it’s for |
|---|---|---|---|
| Developer Edition | Free | All Conductor OSS features plus enterprise features, pre-built workflow templates, early access to new features, community support | Prototyping, evaluation, non-production use only |
| Enterprise | Custom (contact sales) | Full platform, up to 99.99% availability SLA, SLA-backed response times, multi-channel support (email, portal, Slack, Teams), dedicated Technical Account Manager, expert architectural guidance | Production workloads, teams needing governance and support contracts |
There is no published tier between these two. Enterprise deployment can be Orkes-hosted (fully managed) or customer-hosted (AWS, Azure, Google Cloud, on-premises, dedicated VPC/VNet, cross-region backup and failover). A 14-day Enterprise trial is offered at signup.
Separately, the underlying Conductor engine is open source and can be self-hosted for free without any Orkes contract; you lose managed hosting, enterprise features, and support in that path.
Against the alternatives
| Orkes | LangGraph | CrewAI | n8n | |
|---|---|---|---|---|
| Core model | Durable execution engine (Conductor), framework-agnostic | Low-level stateful graph runtime | Role-based multi-agent crews | Visual + code-first workflow automation |
| Pricing | Free Developer Edition (non-prod) / Enterprise custom | Free library; LangSmith from $0-$39/seat/mo | Open source; CrewAI Enterprise custom | Free self-host; hosted plans from published rates |
| Primary language | Java, Python, Go, JS/TS, C# | Python, JavaScript/TypeScript | Python | Node.js (visual canvas, code nodes) |
| Relationship to agent frameworks | Sits underneath them (bring your own) | Is one itself | Is one itself | Has its own AI Agent node |
| Self-serve checkout | No | Yes (LangSmith) | Partial | Yes |
| Best viewed as | Governed execution layer for agents at scale | Stateful agent orchestration library | Fast multi-agent prototyping | No-code-friendly automation with AI nodes |
Recent developments
- April 2026: $60M Series B. Led by AVP, with new investor Prosperity7 Ventures and returning investors Nexus Venture Partners, Battery Ventures, and Vertex Ventures US. Orkes says it has tripled its customer base since the 2024 Series A and now counts hundreds of thousands of developers and millions of installs across its open-source and commercial user base.
- AI-agent repositioning. Orkes now markets Conductor explicitly as infrastructure for AI agents, adding “Orkes Agentic Workflows” and an “Agentspan” observability product aimed at giving teams explainability into agent decision-making, alongside the pre-existing workflow-orchestration core.
- Framework-agnostic messaging. Marketing and docs increasingly emphasize “bring your own agent framework” (LangGraph, OpenAI Agents SDK, Google ADK, CrewAI), positioning Orkes as infrastructure rather than a competing agent framework.
System verdict
Orkes is infrastructure, not a finished agent product: teams still choose and build their own agents in LangGraph, CrewAI, or another framework, then route execution through Conductor for durability and governance. That makes it a strong fit for engineering-led organizations that already value Conductor’s failure-recovery model, and a poor fit for teams that want a single self-serve subscription with a visible price tag. The lack of a published paid tier below Enterprise is the single biggest buying friction: budget for a sales conversation, not a checkout page.
FAQ
Is Orkes free?
Partially. The underlying Conductor engine is open source and free to self-host. Orkes' own Developer Edition is also free but explicitly not for production (no SLA, rate limits, variable performance). Production use requires a custom-quoted Enterprise agreement.What is the difference between Conductor and Orkes?
Conductor is the open-source workflow orchestration engine, originally created at Netflix and released in 2016. Orkes, Inc. is the company founded in 2021 by Conductor's original architects; it maintains the open-source project and sells a managed, enterprise-hardened version on top of it.Does Orkes replace LangGraph or CrewAI?
No. Orkes positions itself as complementary infrastructure that sits underneath agent frameworks like LangGraph, CrewAI, OpenAI Agents SDK, and Google ADK. Teams keep their chosen framework for agent reasoning and route execution, retries, and human-approval steps through Orkes/Conductor.How much does Orkes Enterprise cost?
There is no published price. Enterprise is quote-based after a sales conversation, and a 14-day trial is available through the Orkes signup flow. Verified July 2, 2026 against the official pricing page.Who founded Orkes?
Jeu George (CEO), Viren Baraiya and Boney Sekh (co-CTOs), and Dilip Lukose (CPO), all of whom built Conductor while at Netflix. They founded Orkes in 2021 and launched publicly in February 2022.What languages does Orkes support?
Native SDKs are available for Java, Python, Go, JavaScript/TypeScript, and C#.Sources
Reader reviews
Embed this score on your siteFree. Links back.
<a href="https://aipedia.wiki/tools/orkes/" target="_blank" rel="noopener"><img src="https://aipedia.wiki/badges/orkes.svg" alt="Orkes on aipedia.wiki" width="260" height="72" /></a>[](https://aipedia.wiki/tools/orkes/)Badge value auto-updates if the editorial score changes. Attribution via the link is required.
Cite this pageFor journalists, researchers, and bloggers
According to aipedia.wiki Editorial at aipedia.wiki (https://aipedia.wiki/tools/orkes/)aipedia.wiki Editorial. (2026). Orkes: Editorial Review. aipedia.wiki. Retrieved August 2, 2026, from https://aipedia.wiki/tools/orkes/aipedia.wiki Editorial. "Orkes: Editorial Review." aipedia.wiki, 2026, https://aipedia.wiki/tools/orkes/. Accessed August 2, 2026.aipedia.wiki Editorial. 2026. "Orkes: Editorial Review." aipedia.wiki. https://aipedia.wiki/tools/orkes/.@misc{orkes-editorial-review-2026,
author = {{aipedia.wiki Editorial}},
title = {Orkes: Editorial Review},
year = {2026},
publisher = {aipedia.wiki},
url = {https://aipedia.wiki/tools/orkes/},
note = {Accessed: 2026-08-02}
}Spotted an error or want to share your experience with Orkes?
Every tool page is re-verified on a recurring cycle, and corrections land faster when readers flag them directly. If you spot a stale fact, a missing capability, or have used Orkes and want to share what worked or didn't, the editorial desk reviews every message sent through this form.
Email editorial@aipedia.wiki