Local proof workflow
Build from authorized source, initialize repository policy, verify the real working tree, and retain a redacted JSON proof.
PatchProof 0.1 · early access
Help shape the evidence layer before it becomes automatic.
PatchProof is usable today as a manual-first verification system. Early access is for developers and small teams willing to start with explicit local or self-hosted runs and give the proof model a demanding real-world test.
No waitlist form. Registration uses the existing PatchProof account flow.
What early access includes
The core loop, without pretending the roadmap already shipped.
Manual cloud workflow
Create a workspace and project, register a self-hosted runner, explicitly queue runs, and review centralized evidence.
Operator foundation
Use verified accounts, workspace roles, invitations, API tokens, runner visibility, artifacts, and production readiness checks.
Set expectations early
This is an evidence system in active development.
The safest way to evaluate PatchProof 0.1 is to begin with a repository and patch you understand. Compare the verdict and concerns with your own review, inspect what evidence is useful, and keep your existing merge and deployment safeguards in place.
PatchProof is an engineering aid. A safe verdict is not a guarantee that software is secure, correct, compliant, or ready for production.
01
Protect the runner
You control its operating system, Git and registry access, network, secrets, isolation, and backups.
02
Review the policy
Generated starter commands are suggestions. Confirm the repository contract before executing them.
03
Keep human judgment
Use the proof to focus review, not to eliminate responsibility for the merge decision.
Not in early access yet
Deliberately deferred capabilities.
- Repository event automationNo GitHub App or Gitea webhook-triggered run flow yet.
- Hosted executionNo PatchProof-managed runners; you provide and secure the runner host.
- Executable previewsPreview metadata exists, but Docker Compose boot, proxying, and cleanup are deferred.
- Generated interpretationNo AI-written report summaries; current conclusions are deterministic.
- Commercial plansNo billing or pricing workflow is part of this release.
- Visual policy editorEdit and review
.patchproof.ymlin the repository today.
Choose your first step
Start local, then add the shared control plane.
The source Quickstart is the smallest path to a proof. Registration opens the current self-serve workspace flow for the manual cloud experience.