Ways to start
Start with proof on your own code.
OrangePro checks, after merge and before release, whether your tests would fail if the code that just changed were wrong. There are three ways to try it. Two of them cost nothing, and none of them needs a long project or a contract to begin.
Choose how to start
Free report
Paste a public GitHub repository or your company website. OrangePro maps the public code, ranks the riskiest functions by how much test evidence they have, and suggests a starting test for the top one.
- We read public code only. We never run your code.
- It runs no test, so it shows where proof is missing, not proof itself.
- It does not check pull requests and is not a release gate.
Evaluate one pull request
Bring one repository, one real pull request and your existing test command. We run OrangePro on that change with you and return a test-only patch with a receipt for each test.
- The first call takes 30 minutes and is free.
- Pilot pricing on request, fixed and agreed before work starts.
- Starts with JavaScript repositories today.
Run the local engine
Run the MIT-licensed engine on your own machine. The map and the risk ranking need no model and no account. Optional test drafting uses the model provider you choose, with your key.
- Source stays on your machine.
- Works with Claude Code, Cursor, Codex and Copilot.
- Read every line on GitHub.
local engine, one command
$ npx -y @orangepro/mcp-server@latest start .
What happens on a pull request evaluation
- 1
Map
Find the functions a change touched and how much real test evidence each one has.
- 2
Rank
Put the riskiest unprotected behavior first, so effort goes where a bug would hurt.
- 3
Prove
Draft a focused test, then break the behavior on purpose. The test counts only if it passes on your code and fails on the broken copy.
- 4
Keep
Take the test-only patch and the receipts into your repository. They keep running in your own CI.
OrangePro is not a merge gate or a release gate, and it does not replace CI, code review or end-to-end testing. If it cannot run your tests, it reports the result as unknown and names the blocker. See how it fits next to other tools.
Pricing
A clear structure, with no surprise charges.
We show how pricing works, not a price list. Post-merge volume differs from team to team, so we size the plan with you before anything is billed.
Free report
Free
No account, no card
See where tests are missing for the riskiest functions in a public repository, ranked by how much test evidence each one has.
- Public code only. We never run your code.
- A ranked list and a suggested starting test.
- Shows where proof is missing. It is not proof itself.
Pilot
Pilot pricing on request
Small, fixed, agreed before work starts
Try OrangePro on your own repository and real pull requests after merge, with us alongside. One fixed fee and a set scope, so there is nothing to meter.
- Scope and fee agreed in writing before we start.
- A test-only patch your repository owns.
- A reviewable evidence report for each verification.
Team subscription
Per repository or workspace
Sized to your normal post-merge volume
A subscription for each repository or workspace, with a set number of verifications included. You choose what happens at the limit.
- Included verifications, sized to how often you merge.
- A soft cap, with usage you can see and alerts as you approach it.
- At the limit your admin chooses: pause, or allow overage up to a cap you set.
- Never a silent automatic top-up.
- No per-seat pricing. Add the whole team.
What counts as one verification
One completed, scoped verification of a merged change, with an evidence report you can review. Runs that fail or stop on an infrastructure problem do not count. Retries of the same verification within 14 days do not count.
What you will not pay for
- No per-seat pricing.
- No credits used up by automatic triggers.
- No pricing tied to outcomes. You pay for completed verifications and the evidence they produce.
The local engine is open source under the MIT license and free to run on your own machine.
What engineering leaders say
“One npx command and the engine was running on our own machine. No signup, and our code never left the building. What came back was a short list of risky functions, and new tests only counted once they failed on a deliberately broken copy.”
“A green build only tells you the tests you have passed. OrangePro showed us which changed functions no test would catch if they broke, and gave us tests we could keep in our own repo.”
“Even with high code coverage, gaps slipped through. OrangePro checks whether a test actually fails when the behavior is broken on purpose. That is the question coverage never answered for us.”
“We compared OrangePro with tools we already use. It did not replace them. It added a check after merge that our tests catch real faults, with a receipt for each test that we could show the team.”
Not sure where to begin?
The free report takes a minute and needs no account. Book the free 30-minute call when you want to try a real pull request.