Pact
pact.io
- Free plan
- Windows
- macOS
- Linux
- API
- Self-hosted
What Pact is
Pact is a code-first tool for contract testing HTTP and message integrations. Automated consumer tests create contracts that capture concrete interactions between consumer and provider applications. Teams can test each side in isolation against that shared understanding, without deploying the full system. Pact implementations cover more than 10 languages, including JavaScript, Java, .NET, Go, Python, Ruby, Swift and Objective-C, Rust, Scala, PHP, and C++. Its CLI includes mock and stub servers, a provider verifier, a broker client, and a plugin CLI. The open-source Pact Broker shares contracts and verification results; teams can host and administer it themselves. It also supports CI/CD checks that indicate whether application versions can be deployed together. The verifier handles HTTP and asynchronous and synchronous messages, with plugins for gRPC, Avro, and CSV. Documentation includes recipes for GraphQL, Cypress, Jest, Mocha, Kafka, AWS Lambda, and API Gateway. Pact is free open-source tooling. PactFlow has separate plans, including a free Starter plan and Team plans at $115.42 a month billed yearly or $127 a month billed monthly.
Who it suits
Pact suits developers and teams that control development of both consumer and provider applications. It is not intended for load testing, provider functional testing, or APIs with many consumers who cannot maintain direct relationships with the provider team.
Good to know, and what to watch
- Tests consumer-provider integrations in isolation.
- Implementations cover more than 10 languages.
- Broker supports CI/CD compatibility checks.
- Verifier supports HTTP and message testing.
- Free open-source tooling is available.
- The free Pact Broker must be self-hosted.
- Broker operators handle security, maintenance, and upgrades.
- Not intended for performance or load testing.
- SSO, API tokens, audit trails, and secrets are PactFlow features.
Plans
Every plan and pricePactFlow Enterprise
PactFlow Starter
Pact open-source tooling
PactFlow Team (yearly)
Free plan
Getting started
- Open the Pact website and choose the open-source tooling or PactFlow option
- Select an implementation for your programming language
- Generate contracts from automated consumer tests
- Run provider verification with the Pact CLI
- Host and operate the open-source Pact Broker separately, or choose PactFlow
- Connect Broker checks to your CI/CD workflow
Limits to check
The open-source Pact Broker requires separate hosting and operation, leaving its operator responsible for security, maintenance, and upgrades. PactFlow Starter includes unlimited users and two integrations; Team plans include 50 integrations.
The Club's review
Overview
Pact is a code-first contract-testing tool for HTTP and message integrations, aimed chiefly at developers working across consumer and provider applications. It helps teams check compatibility while those applications can still be tested separately, but it depends on a workable relationship between the teams that own each side.
That makes Pact a strong fit for coordinated service development, especially where teams want integration checks in their CI/CD workflow. It is a poor fit for load testing, provider functional testing, or APIs with many consumers who cannot work directly with the provider team.
Key features
Automated consumer tests produce contracts that describe concrete interactions with providers. Teams can verify each application in isolation against those shared expectations, which can expose integration mismatches before deployment without requiring the whole system to run together. The approach is most useful when both sides can keep tests and verification aligned.
The CLI includes mock and stub servers, a provider verifier, a Broker client and a plugin CLI. Verification supports HTTP and synchronous or asynchronous messages; plugins extend the protocol options to gRPC, Avro and CSV. Message tests are independent of a particular queueing system, with documented examples for ActiveMQ, RabbitMQ, SNS, SQS, Kafka and Kinesis. Recipes also cover GraphQL, Cypress, Jest, Mocha, AWS Lambda and API Gateway.
Implementations span more than 10 languages, including JavaScript, Java and JVM languages, .NET, Go, Python, Swift and Objective-C, Ruby, PHP, C++, Rust and Scala. That breadth makes Pact practical across many development stacks, though it remains a developer-oriented tool rather than a general-purpose testing interface.
The Broker shares contracts and verification results, and can report which application versions are safe to deploy together. Those checks support CI/CD decisions for independently changing services. The open-source Broker is self-hosted, however, so the team running it is responsible for security, maintenance and upgrades.
Pricing
Pact open-source tooling: free. The tooling is open source, but shared contract workflows require a separately hosted and operated Pact Broker. This option suits teams willing to run that infrastructure themselves.
PactFlow Starter: free, with unlimited users, 2 integrations and Bi-Directional Contract Testing. The integration cap makes this the better fit for trying PactFlow or a small setup than for a growing portfolio.
PactFlow Team: $115.42 a month (billed yearly as $1,385) or $127 a month (billed monthly). Both include 50 integrations, community support, Bi-Directional Contract Testing, GitHub and Google Login, and a 14-day free trial. The yearly term lowers the monthly equivalent but commits the buyer to annual billing; the monthly option costs more per month and avoids that annual term.
PactFlow Enterprise: custom pricing, with advanced user and security management, dedicated support, and SaaS or on-premise deployment. Its Enterprise plan lists SAML single sign-on and role-based access management; PactFlow also describes SCIM support for automated user, group and role provisioning and deprovisioning. PactFlow says it encrypts data at rest with AES-256, enforces TLS 1.2 or higher, and stores data and backups in AWS Sydney. These are PactFlow capabilities, not core Pact features.
Platforms
Pact supports API workflows and runs across Linux, macOS and Windows, with self-hosted deployment available. The combination suits teams that want to incorporate contract checks into their existing development and CI/CD setup.
Who it's for
Pact is best for developers whose teams control both consumer and provider development and can coordinate around contracts. It is less suitable when consumers cannot maintain a direct relationship with the provider team. Documentation, a Slack community and partners provide support routes, while the community-support offer on PactFlow Team gives buyers a defined support tier.
Pros and cons
- Pros: Consumer-driven contracts let teams verify integrations in isolation, without deploying the entire system.
- Pros: Broad language, message and protocol support makes it adaptable to varied service stacks and queues.
- Pros: Broker compatibility checks can inform whether application versions are safe to deploy together.
- Cons: The free, open-source Broker requires the team to handle hosting, security, maintenance and upgrades.
- Cons: Pact's model depends on close consumer-provider coordination, limiting its fit for APIs with many disconnected consumers.
- Cons: Pact does not target performance, load or provider functional testing, so those needs require other tools.
Alternatives
For API design and broader API work, API Design Tools and API Testing Tools are useful directories to compare. Readers focused specifically on contract validation can browse Contract Testing Tools, while those comparing wider integration checks can use Integration Testing Tools.
Apidog is a freemium option with a time-unlimited free plan for 4 users; consider it when that user cap and its broader API platform fit better than Pact's code-first workflow.
Postman has a free plan with an API client, core tools, specs, mock servers, Native Git and Collection Runner; it may suit readers seeking that broader API toolkit.
oasdiff offers an open-source engine, CLI and GitHub Action under Apache 2.0; choose it when the task centers on OpenAPI specification differences.
WireMock offers a free tier capped at 1,000 calls per month, one user and three mock APIs; it suits a bounded API-mocking need rather than Pact's contract workflow.
GraphQL Hive has a free Hobby plan with 1M operations per month and unlimited seats, projects, organizations and schema pushes; consider it for GraphQL schema and usage work.
OpenAPI Studio is another option for readers comparing API tooling.
SwaggerHub offers free basic API design and documentation; it may suit readers focused on those tasks.
Assertible has a free Personal plan covering 2 web services, 10 tests per service and 1,000 results; consider it when those limits match a smaller web-service testing need.
Verdict
Choose Pact if developers on both sides of an integration can maintain shared contracts and you want isolated compatibility checks wired into CI/CD. Its language and protocol range is a clear strength; look elsewhere if you need load or provider functional testing, cannot coordinate consumer and provider teams, or do not want to operate the free Broker.
The verdict
Pact provides a focused approach to checking integrations through contracts, with broad language and protocol support. Teams should account for the operational work of running the free Broker and consider whether their consumer-provider relationships suit its model.
Questions people ask
Is Pact free?
Pact open-source tooling is listed as free, and PactFlow Starter is also free. PactFlow Team costs $115.42 a month billed yearly or $127 a month billed monthly; Enterprise pricing requires contacting sales.
Which languages and platforms are supported?
Implementations are listed for JavaScript, Java and JVM languages, .NET, Go, Python, Swift and Objective-C, Ruby, PHP, C++, Rust, and Scala. Platforms include API, Linux, macOS, Windows, and self-hosted deployments.
What does the Pact Broker do?
It shares consumer-driven contracts and verification results, and can report whether application versions are compatible for deployment. The open-source Broker is self-hosted.
Does Pact support messaging?
Yes. The verifier supports asynchronous and synchronous messages, and documentation covers ActiveMQ, RabbitMQ, SNS, SQS, Kafka, and Kinesis scenarios.
What integrations are documented?
Recipes cover GraphQL, Cypress, Jest, Mocha, Kafka, AWS Lambda, and API Gateway. Plugins include gRPC, Avro, and CSV support.
What is Pact not designed for?
Pact is not intended for performance or load testing, provider functional testing, or APIs whose many consumers cannot maintain direct relationships with the provider team.
What the maker publishes
- Broker
- The open-source Pact Broker shares contracts and verification results; it can be self-hosted and administered by the user. source
- Broker role
- The Pact Broker shares consumer-driven contracts and verification results, and can report which application versions can be deployed safely together. source
- CI/CD
- The Pact Broker supports CI/CD workflows, including compatibility checks that indicate whether application versions can be deployed together. source
- CLI tools
- The Pact CLI includes mock and stub servers, a provider verifier, a broker client and a plugin CLI. source
- How contracts work
- Pact contracts are generated by automated consumer tests and describe concrete interactions between consumer and provider applications. source
- Integrations
- Pact documentation provides recipes for scenarios and tools including GraphQL, Cypress, Jest, Mocha, Kafka, AWS Lambda, and API Gateway. source
- Integrations
- PactFlow's Bi-Directional Contract Testing integrates with OpenAPI and lists Cypress, Postman and Wiremock as tools for writing contracts. source
- Intended users
- Pact is most valuable when teams control development of both consumer and provider applications, and is generally implemented by developers. source
- Intended users
- PactFlow describes its service as supporting teams building microservices, messaging systems or cloud-native systems. source
- Languages
- The Pact site lists implementations for JavaScript, Java and JVM languages, .NET, Go, Python, Swift and Objective-C, Ruby, PHP, and C++. source
- Language support
- Pact implementations are available in more than 10 languages, including Java, Rust, JavaScript, .NET, Go, PHP, Python, Ruby, Swift/Objective-C, Scala and C++. source
- Messaging
- Pact abstracts message testing from the queueing technology and documents examples involving ActiveMQ, RabbitMQ, SNS, SQS, Kafka, and Kinesis. source
- Notable limit
- The free Pact Broker is self-hosted, so its operator is responsible for security, maintenance and upgrades. source
- Not suitable for
- Pact documentation says it is not intended for performance or load testing, provider functional testing, or APIs whose many consumers cannot maintain direct relationships with the provider team. source
- Platforms
- Pact CLI installation scripts support Linux, macOS and Windows on ARM64 and AMD64. source
- Protocol support
- The Pact verifier supports HTTP, asynchronous and synchronous messages, and Pact plugins; plugins include support for gRPC, Avro and CSV. source
- Purpose
- Pact is a code-first tool for testing HTTP and message integrations with contract tests. source
- Purpose
- Pact is a code-first tool for testing HTTP and message integrations with contract tests. source
- Security
- PactFlow says it encrypts data at rest with AES-256, enforces TLS 1.2 or higher, and stores data and backups in AWS Sydney. source
- Security administration
- PactFlow's Enterprise plan lists SAML single sign-on and role-based access management, and the security page describes SCIM support for automated user, group and role provisioning and deprovisioning. source
- Security distinction
- The Pact site describes SSO, API tokens, audit trails, and secrets as premium PactFlow features rather than core Pact features. source
- Support
- The Pact site links to documentation, a Slack community, and partners for support. source
- Support
- Pact's official site directs users to documentation, a Slack channel and partner support; PactFlow plans list email support for Team and dedicated account and customer care for Enterprise. source
- Testing model
- Pact contract tests check integrations in isolation against a shared understanding documented in a contract. source
Checked against the maker's pages on 4 Oct 2026.