Conductor OSS website screenshot

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.

Conductor OSS publishes 4 APIs on the APIs.io network, including Events API, Metadata API, Tasks API, and 1 more. Tagged areas include Agentic AI, Durable Execution, Event-Driven, Microservices, and Netflix.

Conductor OSS’s developer surface includes documentation, getting-started guide, GitHub presence, engineering blog, YouTube channel, pricing, developer portal, and 18 more developer resources.

31.8/100 thin ▬ flat Agent 19/100 agent aware Full breakdown ↓
scored 2026-07-28 · rubric v0.6
5 APIs 7 Features 6 Use Cases
Agentic AIDurable ExecutionEvent-DrivenMicroservicesNetflixOpen SourceOrchestrationWorkflow EngineWorkflows

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-07-28 · rubric v0.6
Composite quality — 31.8/100 · thin
Contract Quality 12.1 / 25
Developer Ergonomics 10.4 / 20
Commercial Clarity 2.1 / 20
Operational Transparency 0.7 / 13
Governance 0.0 / 12
Discoverability 6.5 / 10
Agent readiness — 19/100 · agent aware
Machine-Readable Contract 18 / 18
Agentic Access Contract 10 / 10
MCP Server 0 / 12
Machine-Readable Auth 0 / 10
Idempotency 0 / 9
Stable Error Semantics 0 / 8
Request/Response Examples 0 / 7
Rate-Limit Signaling 0 / 7
Typed Event Surface 0 / 6
Agent Skills 0 / 5
Well-Known Catalog 0 / 4
Consent & Bot Identity 0 / 3
A2A Agent Card 0 / 8
Dry-Run / Simulate Mode 0 / 4
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. This rating is computed from github.com/api-evangelist/conductor-oss: open an issue to ask a question, or submit a pull request to add artifacts. Want it done for you? Prioritized profiling — $2,500 →

APIs 5

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 API collections (OpenAPI-derived and Bruno).

Conductor OSS REST API

OPEN COLLECTION

Features 7

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 for all 7

Security Posture 1

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Conductor Oss Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Agentic Access 1

Recommended x-agentic-access execution contracts for AI agents.

Conductor Oss Agentic Access

26 operations · 15 acting · 1 human-in-the-loop

26 operations · 15 acting

AGENTIC

Use Cases 6

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 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 for all 9

Solutions 3

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

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 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

Source (apis.yml)

apis.yml Raw ↑
aid: conductor-oss
name: Conductor OSS
description: 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.
type: Index
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  source: []
  generated: '2026-07-22'
  method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/conductor-oss.png
tags:
- Agentic AI
- Durable Execution
- Event-Driven
- Microservices
- Netflix
- Open Source
- Orchestration
- Workflow Engine
- Workflows
url: https://raw.githubusercontent.com/api-evangelist/conductor-oss/refs/heads/main/apis.yml
created: '2026-05-25'
modified: '2026-05-25'
specificationVersion: '0.19'
apis:
- aid: conductor-oss:conductor-mcp
  name: Conductor MCP Server
  description: 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 LLMs and AI agents can orchestrate Conductor workflows directly.
  humanURL: https://github.com/conductor-oss/conductor-mcp
  tags:
  - Agentic AI
  - MCP
  - Open Source
  - Orchestration
  - Tools
  properties:
  - type: GitHubRepository
    url: https://github.com/conductor-oss/conductor-mcp
  - type: Documentation
    url: https://docs.conductor-oss.org/ai-cookbook
- aid: conductor-oss:conductor-oss-events-api
  name: Conductor OSS Events API
  description: The Events API from Conductor OSS — 1 operation(s) for events.
  humanURL: https://docs.conductor-oss.org/
  baseURL: http://localhost:8080/api
  tags:
  - Events
  properties:
  - type: OpenAPI
    url: openapi/conductor-oss-events-api-openapi.yml
  - type: Documentation
    url: https://docs.conductor-oss.org/
  - type: APIReference
    url: https://docs.conductor-oss.org/reference
  - type: GettingStarted
    url: https://docs.conductor-oss.org/getting-started
  - type: Authentication
    url: https://docs.conductor-oss.org/devguide/running/configuration/security
- aid: conductor-oss:conductor-oss-metadata-api
  name: Conductor OSS Metadata API
  description: The Metadata API from Conductor OSS — 4 operation(s) for metadata.
  humanURL: https://docs.conductor-oss.org/
  baseURL: http://localhost:8080/api
  tags:
  - Metadata
  properties:
  - type: OpenAPI
    url: openapi/conductor-oss-metadata-api-openapi.yml
  - type: Documentation
    url: https://docs.conductor-oss.org/
  - type: APIReference
    url: https://docs.conductor-oss.org/reference
  - type: GettingStarted
    url: https://docs.conductor-oss.org/getting-started
  - type: Authentication
    url: https://docs.conductor-oss.org/devguide/running/configuration/security
- aid: conductor-oss:conductor-oss-tasks-api
  name: Conductor OSS Tasks API
  description: The Tasks API from Conductor OSS — 5 operation(s) for tasks.
  humanURL: https://docs.conductor-oss.org/
  baseURL: http://localhost:8080/api
  tags:
  - Tasks
  properties:
  - type: OpenAPI
    url: openapi/conductor-oss-tasks-api-openapi.yml
  - type: Documentation
    url: https://docs.conductor-oss.org/
  - type: APIReference
    url: https://docs.conductor-oss.org/reference
  - type: GettingStarted
    url: https://docs.conductor-oss.org/getting-started
  - type: Authentication
    url: https://docs.conductor-oss.org/devguide/running/configuration/security
- aid: conductor-oss:conductor-oss-workflow-api
  name: Conductor OSS Workflow API
  description: The Workflow API from Conductor OSS — 9 operation(s) for workflow.
  humanURL: https://docs.conductor-oss.org/
  baseURL: http://localhost:8080/api
  tags:
  - Workflow
  properties:
  - type: OpenAPI
    url: openapi/conductor-oss-workflow-api-openapi.yml
  - type: Documentation
    url: https://docs.conductor-oss.org/
  - type: APIReference
    url: https://docs.conductor-oss.org/reference
  - type: GettingStarted
    url: https://docs.conductor-oss.org/getting-started
  - type: Authentication
    url: https://docs.conductor-oss.org/devguide/running/configuration/security
common:
- type: AgenticAccess
  url: agentic-access/conductor-oss-agentic-access.yml
- type: DomainSecurity
  url: security/conductor-oss-domain-security.yml
- type: Website
  url: https://conductor-oss.org/
- type: Documentation
  url: https://docs.conductor-oss.org/
- type: GettingStarted
  url: https://docs.conductor-oss.org/getting-started
- type: GitHub
  url: https://github.com/conductor-oss
- type: GitHubOrganization
  url: https://github.com/conductor-oss
- type: GitHubRepository
  url: https://github.com/conductor-oss/conductor
- type: Blog
  url: https://orkes.io/blog/
- type: Slack
  url: https://join.slack.com/t/orkes-conductor/shared_invite/zt-3dpcskdyd-W895bJDm8psAV7viYG3jFA
- type: YouTube
  url: https://www.youtube.com/@orkesio
- type: License
  url: https://github.com/conductor-oss/conductor/blob/main/LICENSE
- type: Pricing
  url: https://orkes.io/pricing
- type: Portal
  url: https://cloud.orkes.io/
- type: Signup
  url: https://cloud.orkes.io/signup
- type: Training
  url: https://orkes.io/academy/
- type: SDKs
  url: https://github.com/conductor-oss/java-sdk
- type: SDKs
  url: https://github.com/conductor-oss/python-sdk
- type: SDKs
  url: https://github.com/conductor-oss/go-sdk
- type: SDKs
  url: https://github.com/conductor-oss/javascript-sdk
- type: SDKs
  url: https://github.com/conductor-oss/csharp-sdk
- type: SDKs
  url: https://github.com/conductor-oss/clojure-sdk
- type: SDKs
  url: https://github.com/conductor-oss/rust-sdk
- type: SDKs
  url: https://github.com/conductor-oss/ruby-sdk
- type: CLI
  url: https://github.com/conductor-oss/conductor-cli
- type: Features
  data:
  - name: Durable Workflow Execution
    description: Workflow state is persisted at every step so executions survive worker restarts, server failover, and long
      human-in-the-loop waits.
  - name: Polyglot Workers
    description: 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.
  - name: System Tasks and Operators
    description: Built-in HTTP, Kafka, JQ, wait, human approval, sub-workflow, fork, join, switch, do-while, and dynamic-fork
      operators compose workflows without writing code.
  - name: Agentic AI and LLM Orchestration
    description: 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.
  - name: Event-Driven Triggers
    description: Event handlers consume from Kafka, AMQP, SQS, NATS, and webhook sources to start workflows or complete tasks
      from external systems.
  - name: Horizontal Scalability
    description: Stateless API servers and worker pools scale horizontally, with pluggable persistence (PostgreSQL, MySQL,
      Cassandra, Redis) and indexing (OpenSearch / Elasticsearch).
  - name: Operational Observability
    description: Built-in metrics, structured logs, distributed tracing, and a Swagger UI on every server expose the workflow
      surface for operators.
- type: UseCases
  data:
  - name: Microservices Orchestration
    description: Coordinate sagas, compensations, retries, and timeouts across distributed microservices without bespoke orchestration
      code.
  - name: AI Agent Orchestration
    description: Run production-grade agentic workflows with reasoning loops, tool calling, MCP integration, RAG retrieval,
      and human approvals.
  - name: Payment and Order Processing
    description: Reliable long-running flows for payments, fulfillment, KYC, and onboarding — the reference example workload
      shipped by Conductor.
  - name: Data and ML Pipelines
    description: Schedule and orchestrate ETL, model training, and inference pipelines with durable retries and conditional
      branching.
  - name: Human-in-the-Loop Approvals
    description: Pause workflows on human tasks, capture approvals via UI or API, and resume execution deterministically.
  - name: Event-Driven Integration
    description: Bridge message brokers and SaaS webhooks into deterministic workflows across the enterprise.
- type: Integrations
  data:
  - name: Apache Kafka
    description: System task and event-handler integration for Kafka topics.
  - name: AMQP / RabbitMQ
    description: Built-in AMQP system task and event source.
  - name: AWS SQS
    description: Native SQS event queue and system task module.
  - name: NATS
    description: NATS event queue integration for triggering workflows.
  - name: PostgreSQL / MySQL / Cassandra / Redis
    description: Pluggable persistence backends for workflow and task state.
  - name: OpenSearch / Elasticsearch
    description: Pluggable indexing backends powering search and history.
  - name: AWS S3 / Azure Blob
    description: External payload storage for large workflow inputs and outputs.
  - name: Model Context Protocol (MCP)
    description: Official MCP server exposes Conductor to AI agents as tools.
  - name: gRPC
    description: gRPC API surface alongside the REST API for high-performance clients.
- type: Solutions
  data:
  - name: Conductor OSS
    description: Apache 2.0 open source workflow engine, self-hosted via Docker, Helm, or source build.
  - name: Orkes Developer Edition
    description: Free hosted Conductor sandbox by Orkes with all enterprise features enabled for prototyping and learning.
  - name: Orkes Enterprise / Cloud
    description: Fully managed Conductor on AWS, Azure, GCP, or on-prem with SOC2, RBAC, SSO, audit logs, and up to 99.99%
      availability SLA.
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com