head to head · open source

conductor vs Slickflow

conductor has 32,207 GitHub stars, 1,009 forks, 253 open issues and last shipped today. Slickflow has 920 stars, 264 forks, 11 open issues and last shipped 3 months ago. conductor leads on adoption by 3,401% (32,207 vs 920 stars). conductor is written in Java under Apache-2.0; Slickflow is written in C# under MIT. conductor has attracted 3% as many forks as stars, Slickflow 29%. conductor was the more recently maintained of the two, and both are self-hostable with no licence fee. The two share 1 topic tag (workflow-engine), so they are genuine substitutes rather than adjacent tools.

Two open source projects, one decision. Both are free and self-hostable — the differences are community size, license terms, language stack and release pace.

conductor ★ 32K Slickflow ★ 920 category Infrastructure & Operations

← all 8884 open source comparisons

Side by side

conductor Slickflow
GitHub stars ★ 32K ★ 920
License Apache-2.0 MIT
Written in Java C#
Last push 2026-09-18 2026-06-24
Forks ⑂ 1.0K ⑂ 264
Self-hosting Yes Yes
Data ownership Your server Your server

pick conductor if

  • You weight community size — 32K stars and counting
  • You want the Apache-2.0 license terms
  • Your stack matches Java
  • You value the larger contributor base for long-term maintenance

full conductor profile →

pick Slickflow if

  • You want the Slickflow feature set and don't need the biggest community
  • You prefer the MIT license terms
  • Your stack matches C#
  • You evaluated both and Slickflow fits your workflow better

full Slickflow profile →

About conductor

Conductor is an Apache 2.0 licensed, event driven agentic workflow engine written in Java that provides durable and highly resilient execution for applications and AI agents, aimed at teams running microservices, AI agents, and adaptive workflow graphs that need orchestration they can version, inspect, and recover.

read the full conductor overview →

About Slickflow

Slickflow Current Version: NET8 1. 🤖 AI Powered Workflow Automation SlickFlow: Intelligent Workflow Automation with Large Language Models Slickflow integrates cutting edge Large Language Model (LLM) nodes directly into BPMN workflows, enabling advanced conversational reasoning, RAG (Retrieval Augmented Generation), image understanding and other AI capabilities as first class workflow steps . This transforms traditional workflow systems into dynamic, AI driven orchestration platforms. 1.1 Native LLM Node Integration Add LLM / RAG / Agent nodes into your process diagrams as easily as traditional service tasks. Orc…

read the full Slickflow overview →

More in Infrastructure & Operations

Immich ★ 114K Uptime Kuma ★ 91K worldmonitor ★ 87K mall ★ 85K NetData ★ 81K Elasticsearch ★ 78K

Related comparisons

compose vs conductor conductor vs xxl-job compose vs xxl-job compose vs gitleaks compose vs kestra compose vs haystack compose vs rancher compose vs prefect uptime-kuma vs worldmonitor uptime-kuma vs netdata uptime-kuma vs grafana worldmonitor vs netdata worldmonitor vs grafana netdata vs grafana uptime-kuma vs huginn worldmonitor vs huginn immich vs paperless-ngx immich vs ceph immich vs filestash immich vs garage immich vs storj immich vs alarik immich vs spinifex paperless-ngx vs ceph

More Orchestration & Scheduling projects

Compare either of these against the rest of the Orchestration & Scheduling field.

conductor vs compose conductor vs xxl-job conductor vs gitleaks conductor vs Kestra conductor vs haystack conductor vs rancher conductor vs Prefect conductor vs Archon conductor vs Temporal conductor vs rowboat conductor vs Trigger conductor vs dolphinscheduler

Frequently asked questions

Is conductor or Slickflow more popular?

conductor has 32,207 GitHub stars and Slickflow has 920. conductor has the larger community by that measure.

Are conductor and Slickflow free?

Both are open source. conductor is licensed under Apache-2.0 and Slickflow under MIT. Neither carries a licence fee.

What is the difference between conductor and Slickflow?

conductor is written in Java and Slickflow in C#. The practical differences are community size, licence terms, language stack and release cadence — all compared in the table above.

Which should I choose, conductor or Slickflow?

Choose conductor if you want the larger community (32,207 stars) or its Apache-2.0 licence terms. Choose Slickflow if its feature set, stack or MIT licence fits better. Both are self-hostable.