head to head · open source
one-api vs microcks
one-api has 36,932 GitHub stars, 6,867 forks, 1,036 open issues and last shipped 8 months ago. microcks has 2,044 stars, 367 forks, 58 open issues and last shipped yesterday. one-api leads on adoption by 1,707% (36,932 vs 2,044 stars). one-api is written in JavaScript under MIT; microcks is written in Java under Apache-2.0. one-api has attracted 19% as many forks as stars, microcks 18%. microcks was the more recently maintained of the two, and both are self-hostable with no licence fee. The two share 1 topic tag (api), so they are genuine substitutes rather than adjacent tools.
Two open source projects, one decision. Both are free and self-hostable — the differences are community size, license terms, language stack and release pace.
← all 8884 open source comparisons
Side by side
| one-api | microcks | |
|---|---|---|
| GitHub stars | ★ 37K | ★ 2.0K |
| License | MIT | Apache-2.0 |
| Written in | JavaScript | Java |
| Last push | 2026-01-09 | 2026-09-17 |
| Forks | ⑂ 6.9K | ⑂ 367 |
| 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
pick microcks if
- You want the microcks feature set and don't need the biggest community
- You prefer the Apache-2.0 license terms
- Your stack matches Java
- You evaluated both and microcks fits your workflow better
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 microcks
Microcks is an open source, cloud native API mocking and testing tool and a Cloud Native Computing Foundation incubating project. It lives in the developer tools and API development ecosystem, where teams need to exercise service contracts before implementations are ready or before changes are trusted. The project turns existing API and microservice assets, including OpenAPI specs, AsyncAPI specs, gRPC protobuf, GraphQL schema, Postman collections, and SoapUI projects, into live mocks for applications, testers, and integration pipelines.
read the full microcks overview →
More in Developer Tools
Related comparisons
More API Development & Testing projects
Compare either of these against the rest of the API Development & Testing field.
Frequently asked questions
Is one-api or microcks more popular?
one-api has 36,932 GitHub stars and microcks has 2,044. one-api has the larger community by that measure.
Are one-api and microcks free?
Both are open source. one-api is licensed under MIT and microcks under Apache-2.0. Neither carries a licence fee.
What is the difference between one-api and microcks?
one-api is written in JavaScript and microcks in Java. 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 microcks?
Choose one-api if you want the larger community (36,932 stars) or its MIT licence terms. Choose microcks if its feature set, stack or Apache-2.0 licence fits better. Both are self-hostable.