A · leads
meetily
94.6
32,765 stars · MIT
Self-Hosted
meetily leads by 3.4 · narrow
A · leads
94.6
32,765 stars · MIT
B
91.2
52,087 stars · AGPL-3.0
meetily versus new-api is a Self-Hosted comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. meetily is written mainly in Rust; new-api is written mainly in Go. The composite score is 94.6 for meetily and 91.2 for new-api.
new-api has 52,087 GitHub stars to meetily's 32,765, a gap of 19,322 (1.59×). Forks are 3,640 for meetily and 12,719 for new-api. On the log scale used inside this pair, adoption is 96 versus 100, and the fork community is 87 versus 100.
Push history: meetily was last pushed on 14 November 2026 (3 days ago), and new-api was last pushed on 17 November 2026 (0 days ago). Open issues stand at 412 for meetily (0.013 per star) and 1,474 for new-api (0.028 per star). Issue-health scores are 84 and 70; activity scores are 100 and 100.
meetily 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. new-api is listed as AGPL-3.0, which this catalog treats as a network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. License scores in this pair are 96 for meetily and 52 for new-api. This is a procurement signal, not legal advice.
In Self-Hosted, both meetily (32,765 stars) and new-api (52,087 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: meetily is open source, new-api is open source.
The lead is split. meetily is furthest ahead on license flexibility (96 to 52), while new-api is furthest ahead on fork community (100 to 87). Choose the dimension a rollout cannot compromise on.
meetily finishes ahead at 94.6 against new-api at 91.2, a 3.4 point narrow 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 | meetily | new-api |
|---|---|---|
| GitHub stars | 32,765 | 52,087 |
| Forks | 3,640 | 12,719 |
| Open issues | 412 | 1,474 |
| Adoption | 96 | 100 |
| Activity | 100 | 100 |
| Community | 87 | 100 |
| Issue health | 84 | 70 |
| License | 96 | 52 |
| Self-hosting | 100 | 100 |
| Composite | 94.6 | 91.2 |
Privacy-first AI meeting note taker for Windows, macOS and Linux. Free, open source (MIT). On-device Whisper/Parakeet transcription and speaker diarization, no meeting bot. Open-source alternative to Granola, Otter and Fireflies. https://meetily.ai
Open-source AI gateway. Self-hosted LLM gateway with OpenAI-, Claude- and Gemini-compatible APIs, model routing, access control, usage tracking and cost accounting.
new-api has more GitHub stars: 52,087 versus 32,765 for meetily. The gap is 19,322 stars.
new-api was pushed more recently: 17 November 2026 versus 14 November 2026 for meetily. That is 3 days apart.
Yes. This catalog marks both meetily and new-api as self-hostable. Confirm each project's deploy docs before you plan a migration.
meetily 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. new-api is listed as AGPL-3.0, which this catalog treats as a network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
meetily scores 94.6 and new-api scores 91.2. This page calls that a narrow lead for meetily.