Pact Broker

Pact Broker is a contract registry and CI companion for teams managing dependencies between service consumers and providers. It is best suited to organizations already adopting Pact and comfortable running infrastructure themselves. Choose it when deployment compatibility checks matter as much as storing contracts; choose a hosted plan when operations should not be your responsibility.

Overview

A normal workflow has consumer builds publish Pact contracts, provider builds retrieve and verify them, and consumers run can-i-deploy before release. The broker’s compatibility matrix maps consumer and provider versions, making unsafe pairings visible before they reach production. That turns contract testing into a release decision rather than a document repository.

Pact Broker is optimized for Pact’s HTTP and message interactions, while also accepting contracts that can be represented as JSON. It provides consumer and provider verification, a contract registry, GraphQL support, and a REST API for publishing and retrieving contracts. Teams can therefore integrate it into build automation instead of depending on manual uploads or a web-only workflow.

Key features

An embedded API browser, generated Pact documentation, service-network diagrams, verification results, and status badges make relationships and current contract state easier to inspect. Webhooks can react to pact changes by launching a provider build or sending a Slack notification, connecting a registry event to the next engineering action.

Docker deployment is documented alongside Terraform on AWS. PostgreSQL is suitable for a lasting installation, while SQLite is positioned for quick-start and CI use rather than long-term broker operation. Docker images target both linux/amd64 and linux/arm64. Configurable basic-auth users can receive read/write or read-only privileges. The Docker project reports bundler-audit, Trivy scans of published digests and weekly scans, and Renovate; these measures support maintenance but do not remove the team’s security duties.

Pricing

The free Starter (PactFlow) plan costs nothing and allows unlimited users, two integrations, and bi-directional contract testing. It is a sensible entry point for a small hosted setup, though two integrations can become restrictive as delivery pipelines multiply.

Pact Broker (self-hosted) is also free and includes the open-source broker. The trade-off is substantial: your organization supplies hosting, operations, security, maintenance, and upgrades. This is the economical option for teams with platform capacity, not a zero-effort service.

Team (yearly, PactFlow) costs $115.42 a month, billed yearly as $1,385, with 50 integrations, community support, and GitHub and Google login. Team (monthly, PactFlow) costs $127 a month, billed monthly, with the same 50 integrations and support and login options. The yearly term lowers the monthly rate but commits spending for the billing year. Enterprise (PactFlow) has custom pricing and adds SAML SSO, role-based access management, dedicated support, and SaaS or on-premise deployment.

Platforms

Pact Broker is available as an API, web application, Linux deployment, and self-hosted service. Docker’s multi-platform images cover linux/amd64 and linux/arm64, giving infrastructure teams practical options for those architectures.

Who it's for

It fits development and platform teams coordinating API changes across many consumers and providers, particularly those standardizing on Pact and embedding checks in CI. The REST API, webhooks, and command-line deployment gate suit automated pipelines. Teams without capacity to run databases, upgrades, authentication, and security controls should favor PactFlow instead of assuming the open-source price means no operational cost.

Pros and cons

• Pros: Compatibility checks and can-i-deploy connect verification directly to release safety.
• Pros: REST access, webhooks, diagrams, generated documentation, and status badges support both automation and review.
• Pros: MIT licensing and a zero-cost self-hosted option allow extensive control and customization.
• Cons: Self-hosting requires ongoing hosting, security, maintenance, and upgrades, with SQLite unsuitable for durable operation.
• Cons: The free PactFlow Starter tier is limited to two integrations, while Team pricing is materially higher once 50 integrations are needed.

Alternatives

See the Contract Testing Tools directory for broader comparisons. Choose Microcks instead if you want a 100% open-source, community-driven CNCF Incubating project across a wider range of platforms. oasdiff is a better fit for OpenAPI-focused breaking-change detection with an open-source CLI and GitHub Action. Pick Pact when you need the underlying open-source Pact tooling rather than a broker service. Specmatic suits teams working across OpenAPI, WSDL, or MCP with contract and resilience testing. Confluent Cloud is the alternative for managed Kafka infrastructure. Karate combines API testing with browser, desktop, and performance capabilities. Schemathesis focuses on generated tests from OpenAPI and GraphQL schemas. API Contract Tester is a web option with a free 100-execution monthly tier.

Verdict

Pact Broker is a strong choice for Pact-centered teams that need a registry, verification evidence, and a concrete pre-deployment compatibility gate. Its main reason to look elsewhere is operational ownership: if running the broker and its database is not desirable, PactFlow’s paid tiers or a different managed testing service will be a better fit.