Conductor OSS
Conductor OSS is the Netflix-founded, Orkes-stewarded open source workflow and agentic AI orchestration platform. It provides a durable, event-driven workflow engine for coordinating microservices, long-running tasks, human approvals, and LLM-powered agents across any language or cloud, with first class support for HTTP, gRPC, Kafka, AMQP, SQS, and MCP-based tool calling.
Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.
API Evangelist profiles Conductor OSS the way a machine reads it — 33 machine-readable artifacts across 5 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Conductor OSS scores 34.6/100 (thin), with a separate agent-readiness read of 32/100 (agent aware). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Conductor OSS
Each block below is one kind of artifact we hold for Conductor OSS. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 5
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Conductor MCP Server
Conductor MCP is an official Model Context Protocol server for Orkes Conductor that exposes workflow execution, task management, and metadata operations as MCP tools so that LLM...
Conductor OSS Events API
The Events API from Conductor OSS — 1 operation(s) for events.
Conductor OSS Metadata API
The Metadata API from Conductor OSS — 4 operation(s) for metadata.
Conductor OSS Tasks API
The Tasks API from Conductor OSS — 5 operation(s) for tasks.
Conductor OSS Workflow API
The Workflow API from Conductor OSS — 9 operation(s) for workflow.
Open Collections 1
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
Conductor OSS REST API
OPEN COLLECTIONFeatures 7
The notable capabilities this provider advertises, captured as structured features so they can be searched and compared instead of read one landing page at a time.
Notable capabilities this provider offers.
Durable Workflow Execution
Workflow state is persisted at every step so executions survive worker restarts, server failover, and long human-in-the-loop waits.
Polyglot Workers
Tasks are executed by language-agnostic workers that poll the server, with official SDKs in Java, Python, Go, JavaScript / TypeScript, C#, Clojure, Ruby, and Rust.
System Tasks and Operators
Built-in HTTP, Kafka, JQ, wait, human approval, sub-workflow, fork, join, switch, do-while, and dynamic-fork operators compose workflows without writing code.
Agentic AI and LLM Orchestration
Native LLM tasks for 14+ providers, vector database integrations for RAG, MCP tool calling, and human-in-the-loop checkpoints make Conductor a runtime for agentic AI applications.
Event-Driven Triggers
Event handlers consume from Kafka, AMQP, SQS, NATS, and webhook sources to start workflows or complete tasks from external systems.
Horizontal Scalability
Stateless API servers and worker pools scale horizontally, with pluggable persistence (PostgreSQL, MySQL, Cassandra, Redis) and indexing (OpenSearch / Elasticsearch).
Operational Observability
Built-in metrics, structured logs, distributed tracing, and a Swagger UI on every server expose the workflow surface for operators.
Scroll within the panel for all 7 ·
Security Posture 1
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Use Cases 6
What developers actually build with this provider — captured so the catalogue answers 'what is this for', not just 'what does this expose'.
What developers build with this provider.
Microservices Orchestration
Coordinate sagas, compensations, retries, and timeouts across distributed microservices without bespoke orchestration code.
AI Agent Orchestration
Run production-grade agentic workflows with reasoning loops, tool calling, MCP integration, RAG retrieval, and human approvals.
Payment and Order Processing
Reliable long-running flows for payments, fulfillment, KYC, and onboarding — the reference example workload shipped by Conductor.
Data and ML Pipelines
Schedule and orchestrate ETL, model training, and inference pipelines with durable retries and conditional branching.
Human-in-the-Loop Approvals
Pause workflows on human tasks, capture approvals via UI or API, and resume execution deterministically.
Event-Driven Integration
Bridge message brokers and SaaS webhooks into deterministic workflows across the enterprise.
Integrations 9
Pre-built integrations with other platforms tell you where this provider already fits in a stack.
Pre-built integrations with other platforms and tools.
Apache Kafka
System task and event-handler integration for Kafka topics.
AMQP / RabbitMQ
Built-in AMQP system task and event source.
AWS SQS
Native SQS event queue and system task module.
NATS
NATS event queue integration for triggering workflows.
PostgreSQL / MySQL / Cassandra / Redis
Pluggable persistence backends for workflow and task state.
OpenSearch / Elasticsearch
Pluggable indexing backends powering search and history.
AWS S3 / Azure Blob
External payload storage for large workflow inputs and outputs.
Model Context Protocol (MCP)
Official MCP server exposes Conductor to AI agents as tools.
gRPC
gRPC API surface alongside the REST API for high-performance clients.
Scroll within the panel for all 9 ·
Solutions 3
Packaged solutions the provider offers on top of the raw API surface.
Packaged solutions this provider offers.
Conductor OSS
Apache 2.0 open source workflow engine, self-hosted via Docker, Helm, or source build.
Orkes Developer Edition
Free hosted Conductor sandbox by Orkes with all enterprise features enabled for prototyping and learning.
Orkes Enterprise / Cloud
Fully managed Conductor on AWS, Azure, GCP, or on-prem with SOC2, RBAC, SSO, audit logs, and up to 99.99% availability SLA.
Resources
Every other property we hold for Conductor OSS — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 3
Portal, sign-up, and the first successful call
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Build 12
SDKs, sample code, and the tooling you integrate with
Scroll within the panel for all 12 ·
Access & Security 1
Authentication, authorization, and security posture
Learn 2
Tutorials, courses, talks, and written guidance
Operate 1
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/conductor-oss · machine-readable index on apis.io