← Templates · Dev Tools
PB
Pact Broker
CommunityThe source of truth for contract tests between services — publish Pact contracts and verification results from CI.
| Runs | pactfoundation/pact-broker:2.143.0-pactbroker2.121.0 |
|---|---|
| Stack | ruby |
| Provisioned for it | postgres |
| Verified | Not yet |
Why deploy on Railyard
Railyard provisions postgres alongside it automatically — zero-downtime deploys, automatic backups and scaling come from the same platform, on a server you already pay for.
Deploying Pact Broker is one piece of a bigger stack you can keep building — add a database, a worker, a cache, or another app, all on the same servers you already pay for.
Good for
- Central registry for consumer-driven contract tests across microservices
- Gating CI deploys on whether a service still satisfies its consumers' contracts
Good to know
- Postgres is wired up automatically
- No auth is enabled by default — set PACT_BROKER_BASIC_AUTH_* or PACT_BROKER_ALLOW_PUBLIC_READ_PERMISSIONS=false yourself before exposing it beyond CI