VERIFICATION FOR AGENT-WRITTEN CODE
Merge agent pull requests on evidence, not on a skim of the diff.
MergeProof agrees what “done” means before the agent starts, then independently verifies the running application against it and attaches signed evidence to the pull request.
Illustrative example.
01 · THE PROBLEM
Writing code became cheap. Trusting it did not.
Review is the new backlog
Agents open pull requests faster than people can read them, and senior engineers turn into full-time diff readers.
Passing tests are not proof
When the same agent writes the code and the tests, both inherit the same wrong assumption.
Done was never agreed
A one-line issue leaves edge cases to the agent’s judgment. You find out what it decided after the merge.
Escapes repeat
Last month’s production bug rarely becomes this month’s check, so the same class of mistake ships again.
02 · HOW IT WORKS
One gate between your agents and your main branch.
03 · WHY IT’S DIFFERENT
Review reads the change. MergeProof proves the behavior.
| Capability | AI code review | CI test suite | MergeProof |
|---|---|---|---|
| Checks against intent a person approved | No | Only if someone wrote the test | Yes |
| Exercises the running application | No, reads the diff | Partly | Yes, on the preview |
| Independent of the author | Yes | No, when the agent writes tests | Yes, separate sandbox |
| Evidence a reviewer can inspect | Comments | Pass or fail logs | Screenshots, traces, signed receipt |
| Learns from escaped bugs | No | Manual | Each escape becomes a criterion |
MergeProof works alongside review tools and CI. It doesn’t replace them.
04 · SECURITY AND GOVERNANCE
Built to run untrusted code safely.
Verification means executing changes nobody has reviewed yet. Isolation and provenance are the product, not an add-on.
Isolated runs
Every verification gets a fresh sandbox, destroyed when it finishes.
Scoped credentials
Short-lived secrets per run; network egress limited to your preview.
Signed evidence
Each report is hashed and signed against the commit. A new push invalidates it.
Full audit trail
Who approved which criteria, what ran, and who signed off.
SSO and roles · roadmap
SAML single sign-on and role-based approval policies.
Self-hosted runners · roadmap
Keep code and data inside your own cloud account.
05 · PRICING
Start as a design partner.
Open source
Free
Public repositories with a monthly allowance of verified pull requests.
Join the waitlistTeam
Free for design partners
Private repositories, required merge check, sign-offs, and an included pool of verified pull requests. Pricing set with our first partners.
Apply as a design partnerEnterprise
Custom
Volume pricing, SSO, approval policies, self-hosted runners and a dedicated contact as they ship.
Talk to us06 · QUESTIONS
What teams ask first.
Do you write code?
No. You keep your agents. MergeProof defines done and verifies the result, so it stays neutral across vendors.
What can it verify today?
Web applications and their APIs on per-PR preview deployments. Data migrations, queues and background services are next.
What if a criterion can’t be checked automatically?
It’s marked for human sign-off when the definition is drafted, not discovered at review time.
Which models does it use?
MergeProof is model-agnostic. Drafting and verification can run on the provider your organization approves.