For engineering teams building on GitHub

Catch missing requirements. Before you merge.

ProofCI connects a pull request’s requirements to code changes, tests, and GitHub checks. See the evidence gaps in one report, while the change is still easy to fix.

See how it works See an example report

Source links
Clear evidence gaps
In GitHub Checks

Illustrative report · fictional example Review needed

CI passed. One requested behavior still needs verification.This constructed example shows the report structure. Real reports link to captured source in your GitHub pull request.

Example change · Account recovery

Expire password reset links

2Supported

1Partially supported

0Unsupported

0Unknown

0Out of scope

0Warnings

Requirement 02 of 03 · PR description

Reject password reset links after 30 minutes.

The change adds expiration logic, but the test only covers a valid link. Expired links still need direct verification.

PARTIALLY SUPPORTED

Implementation evidenceAn expiration check was addedFound

Direct test evidenceNo direct test for an expired tokenMissing

CI evidencePassing CI does not verify this requirementNot mapped

Evidence gapsAdd a test that rejects an expired link

The next step is clear: verify the missing behavior, then review the updated evidence.

Requirements

→

Implementation

→

Tests

→

CI checks

A clearer review decision.

01 / The problem

A PR can pass CI and still fail its promise.

A green build cannot tell you whether every requested behavior was covered. ProofCI helps reviewers check the acceptance criteria against the evidence in the change.

SUPPORTED

The required evidence is present.

Implementation, test coverage, and required checks support the stated requirement.

PARTIALLY SUPPORTED

Something is still missing.

Some evidence exists, but the full requirement is not demonstrated by the change.

UNSUPPORTED

The claim outruns the proof.

No trustworthy evidence connects the requirement to implementation and validation.

02 / The proof chain

Three steps to your first report.

01
Connect selected repositories
We confirm your CI setup, agree a pilot, and help you install the GitHub App on the repositories you choose.
Set up
02
Open a PR with clear requirements
Put acceptance criteria in the PR description or a linked issue. ProofCI connects them to evidence in the captured change.
Evidence
03
Review the gaps in GitHub
Open the ProofCI check for a requirement-by-requirement assessment. Follow the source links and decide what needs attention.
Decision

03 / Built for trust

Start small. Stay in control.

A focused pilot, an agreed allowance, and a named contact. Learn whether ProofCI helps your team before making a bigger commitment.

Assisted setup

We qualify your workflow and confirm activation after your pilot agreement is in place.

Repository-level control

Enable only the repositories approved for your pilot or rollout.

A clear usage allowance

Track completed analyses and remaining allowance in your customer workspace. No automatic overage charges.

Stop new analyses

Remove repository access in GitHub or ask us to pause. An analysis already running may finish.

04 / Planned pilot

Start with a focused pilot.

$299 for a 30-day pilot

For GitHub teams that want clearer review of acceptance criteria, including AI-assisted changes. We confirm fit before payment or access.

One organization · up to 2 qualified repositories
50 completed analyses · another PR revision may use another
Assisted setup and one review of your findings
Access ends after 30 days · renewal agreed separately

Preparing for the first teamsComing soon

Pilot requests are closed

Pilot requests aren’t open yet.

We’re getting ready to onboard the first teams. For now, explore the example report and see how ProofCI connects requirements to evidence.

Explore the example

No signup is being collected. Privacy notice · Pilot details

05 / A few useful answers

Know what you’re getting.

What does one analysis include?

One completed report for one pull request revision. A subsequent analyzed revision may consume another analysis. Internal failures do not count toward the completed allowance. Daily safeguards and the agreed pilot allowance can pause new work; there are no automatic paid overages.

Which repositories and CI setups work best?

Start with a GitHub repository that has explicit acceptance criteria and direct tests in the change. We qualify your workflow during setup. CI mapping is deliberately conservative: unsupported, filtered, or conditional test workflows can leave an evidence gap. Existing tests outside the captured change may not be recognized as direct evidence.

Does this replace a code review or guarantee correctness?

No. ProofCI is an aid to human review. It can miss requirements or abstain when evidence is incomplete. A supported verdict means the required evidence was found under the report’s rules; it is not a guarantee that the code is correct or secure.

What access does the GitHub App need?

Read access to selected repository contents, pull requests, issues, metadata, and checks, plus permission to publish the ProofCI check. It does not edit code or merge pull requests. Relevant source and requirement context are sent to an AI provider for analysis. Read the data handling overview before connecting a private repository.

Will the report change when CI finishes?

Reports currently reflect the PR revision and CI captured during analysis. A later CI result does not automatically refresh an existing report. Your pilot contact can help arrange a fresh assessment after checks finish.

How do I get help, cancel, or renew?

Use your private customer workspace or email contact@proofci.com. The pilot ends at its agreed date. Renewal, any early cancellation terms, and data deletion arrangements are confirmed in your written pilot agreement.