A · leads
appsmith
92.6
41,261 stars · Apache-2.0
Self-Hosted
appsmith leads by 1.4 · narrow
A · leads
92.6
41,261 stars · Apache-2.0
B
91.2
52,087 stars · AGPL-3.0
appsmith 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. appsmith is written mainly in TypeScript; new-api is written mainly in Go. The composite score is 92.6 for appsmith and 91.2 for new-api.
new-api has 52,087 GitHub stars to appsmith's 41,261, a gap of 10,826 (1.26×). Forks are 4,847 for appsmith and 12,719 for new-api. On the log scale used inside this pair, adoption is 98 versus 100, and the fork community is 90 versus 100.
Push history: appsmith was last pushed on 17 November 2026 (0 days ago), and new-api was last pushed on 17 November 2026 (0 days ago). Open issues stand at 4,520 for appsmith (0.110 per star) and 1,474 for new-api (0.028 per star). Issue-health scores are 52 and 70; activity scores are 100 and 100.
appsmith 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. 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 appsmith and 52 for new-api. This is a procurement signal, not legal advice.
In Self-Hosted, both appsmith (41,261 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: appsmith is open source, new-api is open source.
The lead is split. appsmith is furthest ahead on license flexibility (96 to 52), while new-api is furthest ahead on issue health (70 to 52). Choose the dimension a rollout cannot compromise on.
appsmith finishes ahead at 92.6 against new-api at 91.2, a 1.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 | appsmith | new-api |
|---|---|---|
| GitHub stars | 41,261 | 52,087 |
| Forks | 4,847 | 12,719 |
| Open issues | 4,520 | 1,474 |
| Adoption | 98 | 100 |
| Activity | 100 | 100 |
| Community | 90 | 100 |
| Issue health | 52 | 70 |
| License | 96 | 52 |
| Self-hosting | 100 | 100 |
| Composite | 92.6 | 91.2 |
Platform to build admin panels, internal tools, and dashboards. Integrates with 25+ databases and any API.
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 41,261 for appsmith. The gap is 10,826 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both appsmith and new-api as self-hostable. Confirm each project's deploy docs before you plan a migration.
appsmith 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. 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.
appsmith scores 92.6 and new-api scores 91.2. This page calls that a narrow lead for appsmith.