Conductor OSS alternatives from the people who built Conductor.
Conductor OSS is free software you host yourself, so you run the persistence layer, the message brokers, scaling, and patching. Its API and UI also have no built-in authentication, RBAC, or SSO, so access control is yours to add.
Unmeshed comes from Netflix Conductor's original creators and keeps the concepts you already know. It runs as a managed cloud or self-hosted, with RBAC, built-in cron scheduling, and a free tier that never expires.
Trusted by teams at leading organisations
Overview
Two ways to run a workflow.
About Unmeshed
Unmeshed is a workflow orchestration platform built by the team behind Netflix Conductor. You define workflows in JSON or YAML, with code-based workers in Java, Go, TypeScript, or Python. Agents run as steps next to plain code, API calls, and human approvals, and the engine keeps state, retries failed steps, and records every run.
About Conductor OSS
Conductor OSS is an open-source workflow and agent orchestration engine, originally created at Netflix and licensed under Apache 2.0. Workers poll for tasks and run in the language you choose, with SDKs for Python, Java, TypeScript, .NET, Go, Ruby, and Rust. You self-host it with your choice of persistence backend and message broker.
Comparison
Unmeshed vs Conductor OSS.
| Unmeshed | Conductor OSS | |
|---|---|---|
| Platform | ||
| Built for | Workflows, APIs, batch jobs, and AI agents | Durable workflow and agent orchestration |
| Workflow definitions | JSON, YAML, or code | JSON definitions with code workers |
| Worker languages | Java, Go, TypeScript, Python | Python, Java, TypeScript, .NET, Go, Ruby, Rust |
| Managed cloud option | Included | Not included |
| Resiliency and operations | ||
| Durable state that survives failures | Included | Included |
| Built-in retries and error handling | Included | Included |
| Human-in-the-loop approvals | Included | Included |
| Built-in cron scheduling, down to one minute | Included | |
| Pricing | ||
| Cost to start | Free tier, no credit card | Free, Apache 2.0 |
| Pricing model | Flat, predictable plans | No license fee; you pay for infrastructure and engineering time |
| Paid plan with support | Included | Not included |
| Upgrade without a sales call | Included | Not included |
| Security, compliance, and governance | ||
| Role-based access control | Included | Not included |
| SSO / SAML | Not included | |
| Authentication on the API and UI | Included | Not included |
| Self-hosted / on-premises deployment | Included | Included |
Keep the concepts. Drop the operations.
Run the workflows you know from Conductor on a managed cloud, with a free tier you sign up for yourself.
Pricing
Conductor OSS costs nothing to download. Running it still costs something.
Conductor OSS is free, and that is a real advantage. What it leaves out is everything you would otherwise buy: hosting, a database, message brokers, scaling, patching, access control, and support.
Unmeshed lists three plans with prices on the page and covers those pieces for you. You can move from free to paid yourself.
Free forever
For solo builders exploring workflow orchestration.
$0/month
No credit card required
Get Started Free- 2,000 workflow executions a month
- Unlimited steps per workflow
- Community support
Premium
For individuals and small teams ready to orchestrate at scale.
$20/month
Billed monthly. Annual billing available, saves 2 months
Get Started- 10,000 workflow executions a month
- Batch job scheduling
- Email support
Enterprise
For organizations with scale, compliance, and infrastructure requirements.
Custom pricing
Tailored to your scale and compliance requirements
Contact Sales- Unlimited executions, workflows, and seats
- SSO/SAML and role-based access control
- Dedicated support with SLAs
Conductor OSS cost, for reference
Conductor OSS is free under the Apache 2.0 license, and we found no paid plans from the open-source project itself. You pay for your own infrastructure, including a persistence backend such as Postgres or Redis with OpenSearch and a message broker, plus the engineering time to scale, patch, and secure it. Support comes through the community on GitHub and Slack.
Agentic AI
Agents on the same engine as your workflows
Conductor OSS
Conductor OSS now positions itself for AI agents too. You can build agents natively or bring agents from other frameworks, and run them on the same durable engine as your workflows.
Unmeshed
Unmeshed does the same, with agents running as steps inside durable workflows next to your APIs, batch jobs, decisions, and human approvals, and with MCP tools supported natively. The difference is where it runs. Unmeshed gives you a managed cloud, and Conductor OSS leaves hosting to you.
Cost and infrastructure
Free software. You run everything under it.
Conductor OSS
Conductor OSS runs anywhere Docker or a JVM runs, and it gives you a choice of persistence backends and message brokers. That flexibility is real, and it comes with the work of operating all of it.
Unmeshed
Unmeshed self-hosts the whole platform on your own VM or Kubernetes cluster, or you can use Unmeshed Cloud, and you choose without a sales call first.
Feature comparison
Conductor OSS makes you plan for this. Unmeshed already did.
The stuff you won't have to build yourself.
Hosting and operations
A managed cloud, not just a download.
Unmeshed
Use Unmeshed Cloud, or self-host the same platform on your own VM or Kubernetes cluster.
Conductor OSS
Self-hosted only, so you operate the database, brokers, scaling, and upgrades.
Pricing
A flat plan, not a project estimate.
Unmeshed
Lists plans with prices on the page, a free tier, and a $20 a month Premium plan you can buy yourself.
Conductor OSS
No license fee, and the real cost is infrastructure and engineering time.
Scheduling
Cron is built in.
Unmeshed
Standard 5-field cron scheduling down to one-minute intervals, plus event triggers.
Conductor OSS
Scheduling takes more setup and depends on how you tune and deploy it.
Migration
Same concepts, shorter names.
Unmeshed
Workflow becomes Process, Task becomes Step, and Decision becomes Switch Case, with a documented mapping and familiar SDKs.
Conductor OSS
The platform most teams are migrating from, so there is nothing to map.
Developer experience
Plain functions. The same worker model.
Workers are plain functions. Register them against a step name, start a process, and the platform handles state and retries, the same poll-and-execute model you already use.
Retries, state, and scheduling come built in, so there's no extra worker setup to hand roll.
Conductor OSS
from conductor.client.automator.task_handler import TaskHandler
from conductor.client.configuration.configuration import Configuration
from conductor.client.worker.worker_task import worker_task
@worker_task(task_definition_name="charge-order")
def charge_order(order_id: str) -> dict:
# your business logic
return {"status": "CHARGED", "order_id": order_id}
task_handler = TaskHandler(configuration=Configuration())
task_handler.start_processes()Unmeshed
from unmeshed.sdk.configs.client_config import ClientConfig
from unmeshed.sdk.unmeshed_client import UnmeshedClient
from unmeshed.sdk.apis.workers.worker import Worker
def charge_order(input: dict) -> dict:
# same business logic, same poll-and-execute model
return {"status": "CHARGED", "order_id": input["order_id"]}
client = UnmeshedClient(ClientConfig())
client.register_worker(
Worker(execution_method=charge_order, name="charge-order")
)
client.start()Frequently asked questions
Still have questions? Talk to us.