Microcks
7.2#4 in api mocking toolsFree planFree planWebAPIExtensionLinux
VisitMicrocks vs Pact
What both publish
| Fact | Microcks | Pact |
|---|---|---|
| CI/CD | It provides integrations for GitHub Actions, Jenkins, GitLab CI, and Tekton pipelines. | The Pact Broker supports CI/CD workflows, including compatibility checks that indicate whether application versions can be deployed together. |
| Integrations | Official automation integrations include GitHub Actions, Jenkins, GitLab CI and Tekton Pipelines. | PactFlow's Bi-Directional Contract Testing integrates with OpenAPI and lists Cypress, Postman and Wiremock as tools for writing contracts. |
| Purpose | Microcks is a tool for mocking and testing APIs and microservices. | Pact is a code-first tool for testing HTTP and message integrations with contract tests. |
| Security | Microcks uses Keycloak for identity, authentication, permissions, and API endpoint protection, with OpenID Connect for user authentication. | PactFlow says it encrypts data at rest with AES-256, enforces TLS 1.2 or higher, and stores data and backups in AWS Sydney. |
Microcks plans
- Microcks (open-source distribution)Free
Pact plans
- PactFlow StarterFree
- Pact open-source toolingFree
- PactFlow Team (yearly)$115.42 a month
- PactFlow Team (monthly)$127 a month
- PactFlow EnterprisePriced on request
Pick Microcks if…
Microcks suits API owners, developers, quality assurance teams and platform engineers who need API mocks or contract checks. Teams can choose laptop, cloud or on-premises deployment.
Pick Pact if…
Pact suits development teams that control both the consumer and provider applications and want to test their integration contracts independently. It is generally implemented by developers.