Pact JVM
JVM implementation of Pact consumer-driven contract testing, produces and verifies contracts between services written in Java, Kotlin, Scala or Groovy.
Our Verdict
The standard JVM choice for consumer-driven contract testing, worth the complexity at microservice scale.
Pros
- Mature consumer-driven contract testing for JVM
- Supports Java, Kotlin, Scala, and Groovy
- Integrates with JUnit 4/5 and Spock
- Generates machine-verifiable pact files
Cons
- Steep learning curve for contract testing concepts
- Requires Pact Broker for team workflows
- Async messaging support less polished than HTTP
Best for: JVM teams with 5+ microservices needing reliable API compatibility checks
Not for: Small teams or monoliths where integration tests suffice
When to Use Pact JVM
Good fit if you need
- Consumer-driven contract testing for JVM microservices
- Generate pact files from consumer test expectations
- Verify provider implementations against pact contracts
- Prevent breaking API changes in microservice deployments
Lock-in Assessment
High 5/5
Lock-in Score 5/5
Pricing
Price wrong?Pact JVM Pricing
- Pricing Model
- free
- Free Tier
- Yes
- Entry Price
- —
- Enterprise Available
- No
- Transparency Score
- —
Beta — estimates may differ from actual pricing
1,000
1001K10K100K1M
Estimated Monthly Cost
$25
Estimated Annual Cost
$300
Estimates are approximate and may not reflect current pricing. Always check the official pricing page.
Project Health
A
Health Score
1.1k 486
Bus Factor
10
Last Commit
today
Release Freq
16d
Open Issues
381
Issue Response
0d
License
Apache-2.0
Last checked: 2026-04-21
Community Discussion
Comments powered by Giscus (GitHub Discussions). You need a GitHub account to comment.