head to head · open source
workflow-core vs Juggle
workflow-core has 5,940 GitHub stars, 1,260 forks, 133 open issues and last shipped 2 days ago. Juggle has 1,165 stars, 203 forks, 7 open issues and last shipped 2 months ago. workflow-core leads on adoption by 410% (5,940 vs 1,165 stars). workflow-core is written in C# under MIT; Juggle is written in Java under GPL-3.0. workflow-core has attracted 21% as many forks as stars, Juggle 17%. workflow-core 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.
← all 20902 open source comparisons
Side by side
| workflow-core | Juggle | |
|---|---|---|
| GitHub stars | ★ 5.9K | ★ 1.2K |
| License | MIT | GPL-3.0 |
| Written in | C# | Java |
| Last push | 2026-11-03 | 2026-09-14 |
| Forks | ⑂ 1.3K | ⑂ 203 |
| Self-hosting | Yes | Yes |
| Data ownership | Your server | Your server |
pick workflow-core if
- You weight community size — 5.9K stars and counting
- You want the MIT license terms
- Your stack matches C#
- You value the larger contributor base for long-term maintenance
pick Juggle if
- You want the Juggle feature set and don't need the biggest community
- You prefer the GPL-3.0 license terms
- Your stack matches Java
- You evaluated both and Juggle fits your workflow better
About workflow-core
Workflow Core Workflow Core is a light weight embeddable workflow engine targeting .NET Standard. Think: long running processes with multiple tasks that need to track state. It supports pluggable persistence and concurrency providers to allow for multi node clusters. Announcements New related project: Conductor Conductor is a stand alone workflow server as opposed to a library that uses Workflow Core internally. It exposes an API that allows you to store workflow definitions, track running workflows, manage events and define custom steps and scripts for usage in your workflows. Documentation See Tutorial here…
read the full workflow-core overview →
About Juggle
Juggle 项目介绍 Juggle是一个接口编排的低代码工具，通过它可以快速将简单的API编排成一个复杂的接口，编排的接口可以直接给前端使用，极大的提高开发效率，减轻开发成本。 演示环境 Juggle官方文档地址: Juggle演示环境地址: (演示环境可以使用gitee或github登录体验) 什么时候需要Juggle 1.适合已有基础服务能力，通过Juggle进行微服务接口编排快速搭建一个新产品。 2.系统需要与第三方系统进行对接，通过Juggle直接进行编排，无需任何开发就可以完成对接。 3.适合做前端的适配层（即BFF），可以用Juggle替代常见的通过Nodejs来实现BFF层的能力。 4.适合需要面向私有化或大量定制开发的产品，通过Juggle编排定制化接口，避免对标准代码的污染。 功能特性 1.流程多版本管理，天然支持流程灰度能力 2.支持字符串，布尔，整数，小数，日期，时间，列表，对象等数据结构，满足绝大数数据定义场景 3.内置方法节点，判断节点，代码节点，赋值节点，MySql节点，并行节点，缓存节点等多种节点，能灵活设计流程 4.支持Groovy,JavaScript,Python,Java等多种脚本语言来增强流程 5.支持Http,Dubbo,WebService等协议的接口调用
read the full Juggle overview →
More in Infrastructure & Operations
Related comparisons
More Orchestration & Scheduling projects
Compare either of these against the rest of the Orchestration & Scheduling field.
Frequently asked questions
Is workflow-core or Juggle more popular?
workflow-core has 5,940 GitHub stars and Juggle has 1,165. workflow-core has the larger community by that measure.
Are workflow-core and Juggle free?
Both are open source. workflow-core is licensed under MIT and Juggle under GPL-3.0. Neither carries a licence fee.
What is the difference between workflow-core and Juggle?
workflow-core is written in C# and Juggle in Java. The practical differences are community size, licence terms, language stack and release cadence — all compared in the table above.
Which should I choose, workflow-core or Juggle?
Choose workflow-core if you want the larger community (5,940 stars) or its MIT licence terms. Choose Juggle if its feature set, stack or GPL-3.0 licence fits better. Both are self-hostable.