A
bytechef
64.8
1,063 stars · license n/a
Workflow Automation
paperclip leads by 29.9 · decisive
A
64.8
1,063 stars · license n/a
B · leads
94.7
114,484 stars · MIT
bytechef versus paperclip is a Workflow Automation comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. bytechef is written mainly in Java; paperclip is written mainly in TypeScript. The composite score is 64.8 for bytechef and 94.7 for paperclip.
paperclip has 114,484 GitHub stars to bytechef's 1,063, a gap of 113,421 (107.70×). Forks are 184 for bytechef and 18,987 for paperclip. On the log scale used inside this pair, adoption is 60 versus 100, and the fork community is 53 versus 100.
Push history: bytechef was last pushed on 17 November 2026 (0 days ago), and paperclip was last pushed on 17 November 2026 (0 days ago). Open issues stand at 491 for bytechef (0.462 per star) and 6,806 for paperclip (0.059 per star). Issue-health scores are 34 and 52; activity scores are 100 and 100.
bytechef is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. paperclip is listed as MIT, 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. License scores in this pair are 30 for bytechef and 96 for paperclip. This is a procurement signal, not legal advice.
In Workflow Automation, both bytechef (1,063 stars) and paperclip (114,484 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: bytechef is unpriced in this catalog, paperclip is open source.
paperclip is ahead on every scored dimension that is not level. Level dimensions: recent activity, self-hosting. The widest gap is license flexibility at 66 points (30 vs 96), and the tightest is self-hosting at 0 points (100 vs 100).
paperclip finishes ahead at 94.7 against bytechef at 64.8, a 29.9 point decisive 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 | bytechef | paperclip |
|---|---|---|
| GitHub stars | 1,063 | 114,484 |
| Forks | 184 | 18,987 |
| Open issues | 491 | 6,806 |
| Adoption | 60 | 100 |
| Activity | 100 | 100 |
| Community | 53 | 100 |
| Issue health | 34 | 52 |
| License | 30 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 64.8 | 94.7 |
Open-source AI agents and workflow automation. Self-host or embed in your SaaS. Apache 2.0 alternative to n8n and Zapier.
The open-source app everyone uses to manage agents at work
paperclip has more GitHub stars: 114,484 versus 1,063 for bytechef. The gap is 113,421 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both bytechef and paperclip as self-hostable. Confirm each project's deploy docs before you plan a migration.
bytechef is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. paperclip is listed as MIT, 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.
paperclip scores 94.7 and bytechef scores 64.8. This page calls that a decisive lead for paperclip.