head to head · open source

one-api vs dev-proxy

one-api has 36,932 GitHub stars, 6,867 forks, 1,036 open issues and last shipped 8 months ago. dev-proxy has 831 stars, 89 forks, 36 open issues and last shipped yesterday. one-api leads on adoption by 4,344% (36,932 vs 831 stars). one-api is written in JavaScript under MIT; dev-proxy is written in C# under MIT. one-api has attracted 19% as many forks as stars, dev-proxy 11%. dev-proxy was the more recently maintained of the two, and both are self-hostable with no licence fee.

Two open source projects, one decision. Both are free and self-hostable — the differences are community size, license terms, language stack and release pace.

one-api ★ 37K dev-proxy ★ 831 category Developer Tools

← all 8884 open source comparisons

Side by side

one-api dev-proxy
GitHub stars ★ 37K ★ 831
License MIT MIT
Written in JavaScript C#
Last push 2026-01-09 2026-09-17
Forks ⑂ 6.9K ⑂ 89
Self-hosting Yes Yes
Data ownership Your server Your server

pick one-api if

  • You weight community size — 37K stars and counting
  • You want the MIT license terms
  • Your stack matches JavaScript
  • You value the larger contributor base for long-term maintenance

full one-api profile →

pick dev-proxy if

  • You want the dev-proxy feature set and don't need the biggest community
  • You prefer the MIT license terms
  • Your stack matches C#
  • You evaluated both and dev-proxy fits your workflow better

full dev-proxy profile →

About one-api

One API is a self hosted LLM API management and key redistribution system that exposes many model providers through the standard OpenAI API format, aimed at developers, teams and operators who want a single endpoint, a single key model and a single quota surface across providers.

read the full one-api overview →

About dev-proxy

Dev Proxy is an open source, command line API simulator maintained under the .NET Foundation and written in C . It intercepts network requests, which means it works with any type of application and any technology stack rather than being tied to one language or framework. It is free to use and licensed under MIT, with the source living in the developer tools and API testing corner of the .NET ecosystem.

read the full dev-proxy overview →

More in Developer Tools

OpenCode ★ 208K Langflow ★ 155K Supabase ★ 110K pi ★ 107K fastapi ★ 102K Neovim ★ 102K

Related comparisons

fastapi vs one-api fastapi vs hoppscotch fastapi vs bruno fastapi vs insomnia fastapi vs openapi-specification fastapi vs openapi-generator fastapi vs redoc hoppscotch vs bruno opencode vs pi opencode vs openhands opencode vs paperclip opencode vs orca opencode vs cline opencode vs aider opencode vs continue opencode vs tabby opencode vs neovim opencode vs zed langflow vs neovim langflow vs zed opencode vs kilocode opencode vs codeedit neovim vs zed langflow vs kilocode

More API Development & Testing projects

Compare either of these against the rest of the API Development & Testing field.

one-api vs fastapi one-api vs Hoppscotch one-api vs Bruno one-api vs Insomnia one-api vs OpenAPI-Specification one-api vs openapi-generator one-api vs redoc one-api vs SafeLine one-api vs Mobile-Security-Framework-MobSF one-api vs grpc-gateway one-api vs Yaak one-api vs hurl

Frequently asked questions

Is one-api or dev-proxy more popular?

one-api has 36,932 GitHub stars and dev-proxy has 831. one-api has the larger community by that measure.

Are one-api and dev-proxy free?

Both are open source. one-api is licensed under MIT and dev-proxy under MIT. Neither carries a licence fee.

What is the difference between one-api and dev-proxy?

one-api is written in JavaScript and dev-proxy in C#. The practical differences are community size, licence terms, language stack and release cadence — all compared in the table above.

Which should I choose, one-api or dev-proxy?

Choose one-api if you want the larger community (36,932 stars) or its MIT licence terms. Choose dev-proxy if its feature set, stack or MIT licence fits better. Both are self-hostable.