Microcks vs Mocki
Microcks
microcks.ioMocki
mocki.ioSide by side
| Figure | Microcks | Mocki |
|---|---|---|
| Price from | Free | $15/mo |
| Free plan | Yes | — |
| Free trial | — | Yes |
| Open source | — | — |
| Web | Yes | Yes |
| Windows | Yes | — |
| macOS | Yes | — |
| Linux | Yes | — |
| API | Yes | Yes |
| Self-hosted | Yes | Yes |
| Plans published | 1 | 1 |
| Spec score · API Mocking Tools | 8.9 (#3) | 8.0 (#9) |
| Local use | The Uber distribution is designed for laptop and unit-test use and uses in-memory MongoDB for ephemeral usage. | The Mocki CLI can run mock services locally, including offline, and is installed from npm. |
| Purpose | Microcks is a tool for mocking and testing APIs and microservices. | Mocki lets users create, run, and deploy mock APIs for development and testing. |
| Security | Microcks uses Keycloak for identity, authentication, permissions, and API endpoint protection, with OpenID Connect for user authentication. | Mocki's privacy policy says it uses commercially acceptable means to protect personal information but cannot guarantee absolute security. |
Plans
In their own words
Microcks
Microcks is an open-source tool for mocking and testing APIs and microservices. It works with OpenAPI, AsyncAPI, gRPC/Protobuf, GraphQL schemas, and SOAP, and can build mock responses from examples, generate realistic data, or alter mock data and responses dynamically. It also checks provider and consumer contracts against live implementations and specification versions, and automates checks in CI/CD pipelines with integrations for GitHub Actions, Jenkins, GitLab CI, and Tekton. Containerized deployment supports on-premises, cloud, and developer-laptop use; its Uber distribution is intended for laptop work and unit tests, using ephemeral in-memory MongoDB. The free, community marketplace for API mocks and test suites is enabled by default. Microcks is a CNCF incubating project, with a listed price of free. The public demo is read-only and cannot import APIs or change artifacts. Documentation cautions against production use of the all-managed Kubernetes setup because its single Keycloak and MongoDB instances are not tuned for scalability or security best practices.