A
InstaPy
81.6
18,414 stars · GPL-3.0
Workflow Automation
puppeteer leads by 17.5 · decisive
A
81.6
18,414 stars · GPL-3.0
B · leads
99.1
95,849 stars · Apache-2.0
InstaPy versus puppeteer is a Workflow Automation comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. InstaPy is written mainly in Python; puppeteer is written mainly in TypeScript. The composite score is 81.6 for InstaPy and 99.1 for puppeteer.
puppeteer has 95,849 GitHub stars to InstaPy's 18,414, a gap of 77,435 (5.21×). Forks are 3,896 for InstaPy and 9,607 for puppeteer. On the log scale used inside this pair, adoption is 86 versus 100, and the fork community is 90 versus 100.
Push history: InstaPy was last pushed on 26 October 2026 (21 days ago), and puppeteer was last pushed on 17 November 2026 (0 days ago). Open issues stand at 586 for InstaPy (0.032 per star) and 201 for puppeteer (0.002 per star). Issue-health scores are 70 and 96; activity scores are 78 and 100.
InstaPy is listed as GPL-3.0, which this catalog treats as a strong copyleft grant. Distributing a modified binary typically means offering the corresponding source of that program. puppeteer 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. License scores in this pair are 64 for InstaPy and 96 for puppeteer. This is a procurement signal, not legal advice.
In Workflow Automation, both InstaPy (18,414 stars) and puppeteer (95,849 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: InstaPy is open source, puppeteer is open source.
puppeteer is ahead on every scored dimension that is not level. Level dimensions: self-hosting. The widest gap is license flexibility at 32 points (64 vs 96), and the tightest is self-hosting at 0 points (100 vs 100).
puppeteer finishes ahead at 99.1 against InstaPy at 81.6, a 17.5 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 | InstaPy | puppeteer |
|---|---|---|
| GitHub stars | 18,414 | 95,849 |
| Forks | 3,896 | 9,607 |
| Open issues | 586 | 201 |
| Adoption | 86 | 100 |
| Activity | 78 | 100 |
| Community | 90 | 100 |
| Issue health | 70 | 96 |
| License | 64 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 81.6 | 99.1 |
📷 Instagram Bot - Tool for automated Instagram interactions
JavaScript API for Chrome and Firefox
puppeteer has more GitHub stars: 95,849 versus 18,414 for InstaPy. The gap is 77,435 stars.
puppeteer was pushed more recently: 17 November 2026 versus 26 October 2026 for InstaPy. That is 21 days apart.
Yes. This catalog marks both InstaPy and puppeteer as self-hostable. Confirm each project's deploy docs before you plan a migration.
InstaPy is listed as GPL-3.0, which this catalog treats as a strong copyleft grant. Distributing a modified binary typically means offering the corresponding source of that program. puppeteer 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.
puppeteer scores 99.1 and InstaPy scores 81.6. This page calls that a decisive lead for puppeteer.