Developer tools · API release engineering

Know what your API breaks before your customers do.

Catch breaking OpenAPI changes on pull requests. Require explicit, expiry-bound exceptions. Leave behind a clear release record your team can inspect.

Get the free GitHub Action → Managed setup · $149

Runs in your CI · No source upload · Read-only GitHub access

Explore the private evidence viewer →

How to catch breaking OpenAPI changes in GitHub Actions →

CONTRACT-GUARD / CI EVIDENCE
$ node cli.mjs --base old.yaml --head new.yaml
● BLOCKED — 2 breaking changes

ERR GET /payments
    request parameter "page"
    became required

ERR GET /payments
    response status enum gained
    the value "chargeback"

EVIDENCE
  SHA-256 base + revision + policy
  report.json / summary.md

exit code: 1

CONTRACT GUARD / PRODUCT

Use the Action free. Commission setup only when you need it.

Action available now
Who it serves

API and platform teams reviewing OpenAPI changes in GitHub pull requests.

What you get

A runnable GitHub Action, reviewable breaking-change findings and expiry-bound exception evidence in your own CI.

Price and access

Free self-hosted Action. Managed one-repository setup is offered at $149, subject to a written scope and seller/payment checks.

Get the free GitHub Action Request managed setup

The free software and the managed configuration service are separate. Repository access, quote and payment steps are agreed before any paid work.

Built on oasdiff. Open-source comparison engine, not a proprietary replacement.

Paid work is optional. You can use the Action without a subscription.

Verified examples from the actual CLI:Breaking change — 2 blockers ↗Safe change — 0 blockers ↗See successful CI verification ↗
How it works

Clear decisions. Reviewable evidence.

The release gate answers three operational questions: did the contract break, was an exception explicitly approved, and which exact inputs produced the decision?

Compatibility gate

Compare OpenAPI 3.x YAML or JSON. Block breaking changes with a failing CI step while allowing safe additions.

Expiring exceptions

Grant a temporary exception only for an exact finding fingerprint, with a documented reason and expiry date.

Local release evidence

Export JSON findings and a human-readable summary with SHA-256 hashes of inputs and policy. Inspect a report locally →

Self-serve integration

Start with one pull request.

Add the Action to your workflow and point it at your baseline and revised spec files. Use your own GitHub runner; no ForgeFrame account is required.

Installation instructions and complete workflow → 
uses: reflectme-source/forgeframe-contract-guard@47857973aeba8bf5bb6b034544bddaa2be6c8ad5 # v0.1.3
with:
  base: baseline.yaml
  head: openapi.yaml
  policy: guard.policy.json
  upload-evidence: 'false'
Fixed scope · Async delivery

Prefer to have it configured for you?

We'll integrate the same open-source gate into your engineering workflow, define appropriate review policy, validate a breaking and non-breaking fixture, and hand over the setup with evidence artifacts.

No sales call and no subscription required. We qualify the existing spec and CI before accepting a paid setup. The Action remains free for teams that prefer self-service.

  1. 01 — Request a scope checkUse our local-only intake page to prepare an email with the spec path, version, runner and expected delivery window. Do not send credentials or API source files.
  2. 02 — Receive written acceptanceWe confirm eligibility, what is included, the legal seller and a delivery date before asking for payment.
  3. 03 — Pay securely via StripeAfter written acceptance, receive a unique one-order Stripe link by email. Only confirmed payments start an installation; we never collect card details.
  4. 04 — Install, verify, hand overGrant least-privilege access, approve the CI Pull Request, review passing and blocking examples, and receive your evidence report and closure confirmation.
Contract Guard Setup
$149

One-time fee for one GitHub repository with an existing OpenAPI 3.x contract.

  • Baseline and pull-request CI configuration
  • Policy and time-bound exception workflow
  • Breaking and safe change verification
  • JSON/Markdown evidence handover
Request setup — qualify your repo ↗

Confirm repository scope and delivery schedule before paying. The service covers one qualifying repository. Read the service terms, cancellation and refund information.

Payment process: we send a unique, one-order Stripe payment link only after confirming your technical scope, legal seller and delivery timeline. There is no public instant checkout or recurring subscription.

Questions

Before you install

Does this upload our API specification?

No. The comparison happens on your own machine or CI runner. Installing the Action downloads a checksum-verified engine binary from GitHub Releases. You choose whether the resulting evidence is stored in GitHub Actions artifacts.

Is this a runtime contract test?

No. It checks changes in OpenAPI specifications. It cannot detect undocumented runtime behavior, deployment drift or actual consumer impact without additional tests.

Does the report certify audit compliance?

No. The SHA-256 hashes help reviewers match evidence to the original specifications, but do not constitute a digital signature or formal certification.

Why pay for setup when the Action is free?

You pay for an implemented, verified workflow and handover in your repository — not for access to the open-source detector. The self-hosted tool remains free to use.

What is not included in the $149 fixed scope?

It does not include custom API development, multi-repository migration, runtime contract testing, a hosted dashboard or continuous monitoring. Additional work requires a separate proposal.

Can I pay before you confirm the scope?

No. The public website does not contain an immediately usable checkout. After written agreement, we issue a unique payment link for your order. You will not be charged simply for requesting a scope assessment.

What if my repository does not qualify, or I need to cancel?

We verify eligibility and timing before payment. If setup cannot be delivered as agreed, contact support; the service terms explain cancellation, refunds and statutory rights.