Skip to content
DevUtils Online

Self-Hosted

glance vs new-api

new-api leads by 4.4 · narrow

A

glance

86.8

38,270 stars · AGPL-3.0

B · leads

new-api

91.2

52,087 stars · AGPL-3.0

glance 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. Both projects are written mainly in Go. The composite score is 86.8 for glance and 91.2 for new-api.

new-api has 52,087 GitHub stars to glance's 38,270, a gap of 13,817 (1.36×). Forks are 1,524 for glance and 12,719 for new-api. On the log scale used inside this pair, adoption is 97 versus 100, and the fork community is 78 versus 100.

Push history: glance was last pushed on 07 November 2026 (10 days ago), and new-api was last pushed on 17 November 2026 (0 days ago). Open issues stand at 323 for glance (0.008 per star) and 1,474 for new-api (0.028 per star). Issue-health scores are 84 and 70; activity scores are 92 and 100.

Both glance and new-api are listed as AGPL-3.0. A network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. The license score is therefore level at 52 versus 52, and the decision moves to adoption, activity, and hosting. This is a procurement signal, not legal advice.

In Self-Hosted, both glance (38,270 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: glance is open source, new-api is open source.

The lead is split. glance is furthest ahead on issue health (84 to 70), while new-api is furthest ahead on fork community (100 to 78). Choose the dimension a rollout cannot compromise on.

new-api finishes ahead at 91.2 against glance at 86.8, a 4.4 point narrow margin under the published weights.

Scores are computed inside this pair only. Method and weights.

Where they separate

The numbers

Bars are scaled within the row. Higher is stronger. Open issues are a raw count, so that row has no bar.

glance versus new-api metrics
Signal glance new-api
GitHub stars 38,270 52,087
Forks 1,524 12,719
Open issues 323 1,474
Adoption 97 100
Activity 92 100
Community 78 100
Issue health 84 70
License 52 52
Self-hosting 100 100
Composite 86.8 91.2

new-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.

Project site · GitHub · Full profile

Questions this page answers

Which has more GitHub stars, glance or new-api?

new-api has more GitHub stars: 52,087 versus 38,270 for glance. The gap is 13,817 stars.

Which was updated more recently, glance or new-api?

new-api was pushed more recently: 17 November 2026 versus 07 November 2026 for glance. That is 10 days apart.

Can I self-host both glance and new-api?

Yes. This catalog marks both glance and new-api as self-hostable. Confirm each project's deploy docs before you plan a migration.

Which license is easier to embed in a commercial product, glance or new-api?

glance 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. 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.

Who wins the glance vs new-api score?

new-api scores 91.2 and glance scores 86.8. This page calls that a narrow lead for new-api.

Related comparisons