A · leads
dashy
94.3
27,013 stars · MIT
Self-Hosted
dashy leads by 3.1 · narrow
A · leads
94.3
27,013 stars · MIT
B
91.2
52,087 stars · AGPL-3.0
dashy 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. dashy is written mainly in Vue; new-api is written mainly in Go. The composite score is 94.3 for dashy and 91.2 for new-api.
new-api has 52,087 GitHub stars to dashy's 27,013, a gap of 25,074 (1.93×). Forks are 1,969 for dashy and 12,719 for new-api. On the log scale used inside this pair, adoption is 94 versus 100, and the fork community is 80 versus 100.
Push history: dashy was last pushed on 16 November 2026 (1 day ago), and new-api was last pushed on 17 November 2026 (0 days ago). Open issues stand at 15 for dashy (0.001 per star) and 1,474 for new-api (0.028 per star). Issue-health scores are 96 and 70; activity scores are 100 and 100.
dashy 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 dashy and 52 for new-api. This is a procurement signal, not legal advice.
In Self-Hosted, both dashy (27,013 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: dashy is open source, new-api is open source.
The lead is split. dashy is furthest ahead on license flexibility (96 to 52), while new-api is furthest ahead on fork community (100 to 80). Choose the dimension a rollout cannot compromise on.
dashy finishes ahead at 94.3 against new-api at 91.2, a 3.1 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 | dashy | new-api |
|---|---|---|
| GitHub stars | 27,013 | 52,087 |
| Forks | 1,969 | 12,719 |
| Open issues | 15 | 1,474 |
| Adoption | 94 | 100 |
| Activity | 100 | 100 |
| Community | 80 | 100 |
| Issue health | 96 | 70 |
| License | 96 | 52 |
| Self-hosting | 100 | 100 |
| Composite | 94.3 | 91.2 |
🚀 A self-hostable personal dashboard built for you. Includes status-checking, widgets, themes, icon packs, a UI editor and tons more!
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 27,013 for dashy. The gap is 25,074 stars.
new-api was pushed more recently: 17 November 2026 versus 16 November 2026 for dashy. That is 1 days apart.
Yes. This catalog marks both dashy and new-api as self-hostable. Confirm each project's deploy docs before you plan a migration.
dashy 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.
dashy scores 94.3 and new-api scores 91.2. This page calls that a narrow lead for dashy.