CONTROLWHAT SHIPS.
Understand what a change could affect, test critical workflows, and apply release requirements before deployment.
Demo data
- Change arrives: Run #129 starts for pull request #4831, an agent's change to payments/auth.ts, and Zof begins evaluating it.
- Impact mapped: Zof rates the change Critical and maps its impact: 5 services, one of them Tier 0, drawn outward from auth-service.
- Checks run: Unit tests and the smoke test pass, but the sign-in token check fails: an expired token still opens a session.
- Release blocked: The release is blocked. A failed required check can't be overridden, even for an agent's change.
- Fix proposed: Finding F-2207 opens with a four-line fix to payments/auth.ts proposed by the agent, awaiting review.
- Fix approved: A. Rivera, the owner, approves the plan for revision 9c41e07; approval alone doesn't clear the failed check.
- Re-run passes — ship: The sign-in token check re-runs on 9c41e07 and passes, the release policy is re-evaluated, and the change can ship.
- Evidence sealed: Release readiness for PR #4831 is generated: 3 of 3 requirements met and 12 pieces of evidence sealed.
Works with GitHub today. Your CI can run the Zof deploy gate, on request.
- GitHubGitHub App · Available today
- GitLab CIDeploy gate · On request
- JenkinsDeploy gate · On request
- CircleCIDeploy gate · On request
How it works
One change,through the loop.
Every change, from a developer, a coding agent or an automation, moves through one closed control loop before production.
01 / 04
A change arrives
Nothing is trusted yet.
A developer, a coding agent or an automation proposes a pull request, configuration edit, migration or deployment.
- From
- Developer · coding agent · automation
- Kind
- PR · config edit · migration · deploy
- Trust
- None until it is proven
02 / 04
The control loop
Four gates, in order.
The change is resolved against the System Graph, proven by the Verification Engine, recorded as Evidence and decided by Control.
- System Graph
- Blast radius: services, data, policies, owners, history
- Verification
- Decides what must be proven, then proves it
- Evidence
- Every check leaves a record
- Control
- Policy decides; a person approves where required
03 / 04
What flows through
Signals in, evidence out.
CI/CD events, pre-production gates, traces and policies feed the loop, and the results are sealed into one evidence bundle with provenance.
- Inputs
- Commits, pull requests, staging builds, release candidates
- Bundle
- Results, traces, policy evaluations, approvals
- Decision
- Allow · deny · require evidence · require approval
04 / 04
Your environment
Allowed lands. Denied holds.
The decision is enforced where the action happens, inside your perimeter: nothing leaves your environment.
- Deploy in
- Cloud, private cloud, and an on-prem proof of concept
- Allowed
- Lands, and is observed against the System Graph
- Denied
- Held on the siding, with its evidence
What you get
Four things Zof gives you.
Understand the impact, verify the behavior, review the evidence, and apply your release requirements.
System Graph
Understand what a change affects
Connect changes to the services and workflows that need attention.
Explore the System GraphVerification Engine
Test the behavior that matters
Run checks against relevant requirements and failure scenarios.
Explore verificationEvidence
Review the results behind the decision
See what ran, what happened, and the supporting records.
Explore evidenceControl
Apply your release requirements
Require the checks and approvals your team has defined.
Explore control
Who it's for
Built for the people who answer for production.
Assess release risks, verify critical workflows, and review the evidence before deployment.
What that means for
Engineering leaders
Assess release risks, verify critical workflows, and review the evidence before deployment.
Explore for engineering leadersSecurity and risk
Review the impact of a change and apply the access, verification, and approval requirements your team defines.
Explore for security teamsCompliance and audit
Review what was checked, what happened, and who approved the change, with records available for audit.
Explore for compliance teamsThe executive team
Understand release risks and the evidence supporting important production decisions.
Explore for technology leaders
By industry
Financial services
Independent verification and control for regulated financial systems.
Learn more: Zof for Financial servicesHealthcare
Continuous validation, policy-aware execution, and human approval, built into every change on patient workflows.
Learn more: Zof for HealthcareSaaS and B2B
Know which releases are safe across tenants, regions, and entitlements, before customers feel a regression.
Learn more: Zof for SaaS and B2BRegulated enterprise
Policies, approvals, and audit trails so AI-assisted testing fits compliance requirements.
Learn more: Zof for Regulated enterprise
Private deployment
Choose where it runs. Review what leaves your environment.
Zof runs as a managed cloud, with private deployment options scoped per engagement. Review data flows with Zof.
| Option | 01 Intelligence | 02 Control | 03 Execution | Details |
|---|---|---|---|---|
| Your cloudPolicy outbound | Zof cloud | Inside | Inside | A dedicated private cloud environment in a region you approve, with control and execution kept on your side. |
| VPCPrivate deployment, scoped per engagement | Zof cloud | Zof cloud | Inside | An example only. Execution in your VPC is scoped per engagement. |
| On-premOn-prem proof of concept | Inside | Inside | Inside | On-prem deployment is available as a scoped proof of concept. We agree the scope, the data flows, and where tests execute with your team first. |
| Air-gappedAir-gapped installation: not available today | Inside | Inside | Inside | A fully air-gapped Zof installation is not available today. |
Where Zof's three planes run in each option's design. What is offered today is under each option's name.
Your cloud
Policy outboundA dedicated private cloud environment in a region you approve, with control and execution kept on your side.
- Intelligence
- Zof cloud
- Control
- Inside
- Execution
- Inside
VPC
Private deployment, scoped per engagementAn example only. Execution in your VPC is scoped per engagement.
- Intelligence
- Zof cloud
- Control
- Zof cloud
- Execution
- Inside
On-prem
On-prem proof of conceptOn-prem deployment is available as a scoped proof of concept. We agree the scope, the data flows, and where tests execute with your team first.
- Intelligence
- Inside
- Control
- Inside
- Execution
- Inside
Air-gapped
Air-gapped installation: not available todayA fully air-gapped Zof installation is not available today.
- Intelligence
- Inside
- Control
- Inside
- Execution
- Inside
Private deployment supports local execution and local-only evidence, with a zero data retention option.
Deployment optionsTrust & governance
Built for the systems regulated industries depend on.
Identity, approvals, and reviewable evidence for critical systems.
Private deployment options are scoped per engagement; review data flows with Zof.
Identity-first.
Associate actions with named identities and defined access permissions.
Audit by default.
Review verification results, decisions, and approvals in an exportable record.
Data flows reviewed.
Review what data Zof touches and where tests execute with your team before you start.
Policy decides.
Apply your verification and approval requirements before a change proceeds.
Evidence
Every verification run, policy evaluation, approval, and outcome is recorded as durable evidence.
Zof in numbers
- stages in the control loop
- 7
- things Zof gives you
- 4
- published workflow evaluations
- 6
- day free trial, no card required
- 14
Workflow evaluations
See what it takes to trust a critical workflow.
This guide presents an evaluation method, not a report of a completed customer engagement.
Retail and payments
When a payment times out, can checkout safely retry?
The acceptance criterion
One intended capture for the agreed amount, connected to a defined order resolution.
Read the evaluation 6 minAudit, tax, and advisory software
Does an approved client workflow stay approved when its inputs change?
The acceptance criterion
A material amendment follows the agreed fresh review rule before delivery.
Read the evaluation 6 minDigital identity and trust services
A certificate is revoked. What does the relying party see?
The acceptance criterion
The application recognizes stale evidence and follows the configured disposition instead of treating it as current status.
Read the evaluation 6 minSystems integration
Reuse the acceptance method. Keep each client's evidence separate.
The acceptance criterion
The acceptance check follows the request to its final state and records the rejection. A receipt acknowledgment cannot produce a passing workflow result.
Read the evaluation 6 minManufacturing and plant software
After the plant connection returns, is the order still in the right state?
The acceptance criterion
The newer authoritative hold remains effective until an authorized quality decision removes it. Late arrival does not make the older release event current.
Read the evaluation 6 minCybersecurity software
A detection update should not change who can see the event.
The acceptance criterion
The record retains Tenant A ownership through processing. Missing context follows the agreed rejection rule, and Tenant B receives no protected content.
Read the evaluation 6 min
Integrations
Run tests where your team already works.
Zof works with GitHub today. Your CI can run the Zof deploy gate, on request. Other tools are not available today.
All integrationsAvailable today
- GitHubGitHub App · Available today
On request
- GitHub ActionsDeploy gate · On request
- GitLab CIDeploy gate · On request
- JenkinsDeploy gate · On request
- CircleCIDeploy gate · On request
- Any other CIDeploy gate image · On request
- Event Triggers
- Zof receives GitHub events to start checks.
- Status on GitHub
- Zof posts its check on the pull request.
- Notifications
- Results show on GitHub. Other notification tools are not available today.
Pricing
Pricing that matches how your team works.
Starter
$99.50/month
Or $82.92 / month · $995 a year by order form
Start validating your product with continuous verification.
- Code review and test generation included
- Core testing for applications and APIs
- Standard Zof Cloud execution
- GitHub integration and evidence reports
- 5 full-access users; viewers and approvers included
14 days free trial · no card required
Team
$499.50/month
Or $416.25 / month · $4,995 a year by order form
Add scheduled testing, CI/CD workflows, and team reporting.
- Code review and test generation included
- Scheduled UI, API, and integration testing
- CI/CD deploy gate on request and shared reporting
- Team dashboard and result history
- 20 full-access users; viewers and approvers included
14 days free trial · no card required
Business
$1,250/month
Or $1,041.67 / month · $12,500 a year by order form
Connect testing, release readiness, and remediation workflows.
- Code review and test generation included
- System Graph and release readiness
- Governed remediation and orchestration
- Audit logs and role-based access
- 50 full-access users; viewers and approvers included
14 days free trial · no card required
Prices as of
Reliability Sprint
Test one critical workflow.
Agree the scope. Exercise failure scenarios. Review prioritized findings and evidence.
Paid engagement. Scope and timeline agreed upfront.
Typically seven days
Zof does the testing. Your team sets the boundaries and keeps control throughout.
- Critical systemScope the system
- System GraphMap how it is built
- Failure scenariosGenerate failure scenarios
- ExecutionExecute and stress
- EvidenceCapture evidence
- RemediationPrioritize and recommend
30-minute demo
Your next release. Under control.
See Zof work with your stack, your team, and your rules.