A · leads
sim
97.9
30,151 stars · Apache-2.0
Workflow Automation
sim leads by 11.8 · clear
A · leads
97.9
30,151 stars · Apache-2.0
B
86.1
19,463 stars · Apache-2.0
sim versus taipy is a Workflow Automation comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. sim is written mainly in TypeScript; taipy is written mainly in Python. The composite score is 97.9 for sim and 86.1 for taipy.
sim has 30,151 GitHub stars to taipy's 19,463, a gap of 10,688 (1.55×). Forks are 3,915 for sim and 1,996 for taipy. On the log scale used inside this pair, adoption is 100 versus 96, and the fork community is 100 versus 92.
Push history: sim was last pushed on 17 November 2026 (0 days ago), and taipy was last pushed on 10 August 2026 (99 days ago). Open issues stand at 330 for sim (0.011 per star) and 233 for taipy (0.012 per star). Issue-health scores are 84 and 84; activity scores are 100 and 58.
Both sim and taipy are listed as Apache-2.0. A permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. The license score is therefore level at 96 versus 96, and the decision moves to adoption, activity, and hosting. This is a procurement signal, not legal advice.
In Workflow Automation, both sim (30,151 stars) and taipy (19,463 stars) are marked self-hostable. Deploy scores are 100 and 100. Running either one means you own upgrades, backups, and the license duties that follow a modified copy. Pricing labels on file: sim is open source, taipy is open source.
sim is ahead on every scored dimension that is not level. Level dimensions: issue health, license flexibility, self-hosting. The widest gap is recent activity at 42 points (100 vs 58), and the tightest is self-hosting at 0 points (100 vs 100).
sim finishes ahead at 97.9 against taipy at 86.1, a 11.8 point clear margin under the published weights.
Scores are computed inside this pair only. Method and weights.
Bars are scaled within the row. Higher is stronger. Open issues are a raw count, so that row has no bar.
| Signal | sim | taipy |
|---|---|---|
| GitHub stars | 30,151 | 19,463 |
| Forks | 3,915 | 1,996 |
| Open issues | 330 | 233 |
| Adoption | 100 | 96 |
| Activity | 100 | 58 |
| Community | 100 | 92 |
| Issue health | 84 | 84 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 97.9 | 86.1 |
Sim is the collaborative workspace to build, deploy, and monitor AI agents and workflows. Used by 100,000+ builders.
Turns Data and AI algorithms into production-ready web applications in no time.
sim has more GitHub stars: 30,151 versus 19,463 for taipy. The gap is 10,688 stars.
sim was pushed more recently: 17 November 2026 versus 10 August 2026 for taipy. That is 99 days apart.
Yes. This catalog marks both sim and taipy as self-hostable. Confirm each project's deploy docs before you plan a migration.
sim is listed as Apache-2.0, which this catalog treats as a permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. taipy is listed as Apache-2.0, which this catalog treats as a permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
sim scores 97.9 and taipy scores 86.1. This page calls that a clear lead for sim.