Skip to content

Deployment

Run Zof where your software needs to be tested.

Compare where Zof can run and what each option needs. On-prem deployment is available as a scoped proof of concept.

  • Data flows and test execution are reviewed before any deployment

Data flow review before deployment

Where tests execute is agreed up front

An evidence record stored for each run

Human approval for governed remediation

Deployment models

Cloud today. Other placements scoped per engagement.

Cloud is one path. Other placements are reviewed with you and scoped per engagement.

  • Zof Cloud today. Dedicated private cloud: scoped per engagement
  • Customer VPC/VNet execution: scoped per engagement
  • Hybrid setups: scoped per engagement
  • Execution at branch or site level: not available today
  • Execution inside segmented networks: not available today
  • Private Kubernetes execution: scoped per engagement
Reference architecture

One core. Placement agreed per deployment.

The Zof Core is the same everywhere. Where each component runs, and what data leaves it, is agreed for each deployment.

Intelligence Plane

Governed test intelligence

Planning, generation, and prioritization. Where this runs is agreed for each deployment.

  • -System Graph and workflow understanding
  • -Risk prioritization and test generation
  • -Test planning for each change
  • -Remediation planning where permitted
  • -Where tests execute is agreed per deployment

Control Plane

Approvals and policy

The layer for approvals, policy, and audit records.

  • -Human approval workflows
  • -Policy enforcement
  • -Evidence records for test runs
  • -Role-based access and SSO integration
  • -Audit-ready records for every action

Execution Plane

Test execution

Where tests run, and what evidence leaves that environment, is agreed during a data flow review.

  • -Test runs against your applications
  • -Browser and API validation. Desktop is scoped per engagement.
  • -An evidence record stored for each run
  • -Data handling agreed during scoping
  • -Model providers reviewed during scoping
The Zof Core

Eight components.

Every deployment model runs the same core. Where each component runs is agreed per deployment.

  1. 01

    System Graph

    Machine-readable understanding of the enterprise and the consequence of change.

  2. 02

    Verification Engine

    Decides what must be proven for each change, then proves it.

  3. 03

    Evidence

    Durable, attributable proof of what happened and why it can be trusted.

  4. 04

    Policy Engine

    Your enterprise policies, versioned and evaluated against every action.

  5. 05

    Model Gateway

    Interchangeable reasoning providers.

  6. 06

    Control Plane

    Turns change, context, risk, evidence, and policy into enforceable decisions.

  7. 07

    Execution integrations

    GitHub today. Decisions are enforced on merge.

  8. 08

    Console

    Zof Console, hosted wherever the deployment model places it.

Model Gateway

Models are reasoning providers, not the architecture.

Model providers are a configuration choice, not the architecture. Which providers an engagement uses, and where their calls go, is agreed during a data flow review.

Compare deployment models

Zof Cloud runs today. On-prem is available as a scoped proof of concept. Every other model is scoped per engagement or not available today.

Deployment modelWhere AI planning runsWhere execution runsInternet requirementData egress modelIdeal use caseSales motionPricing
Zof CloudZof CloudZof-managedStandard outboundCustomer-configuredCloud-native teams, lower-friction pilotsSelf-serve to enterprisePublished tiers + enterprise
Zof Private Cloud (scoped per engagement)Scoped per engagementScoped per engagementScoped per engagementScoped per engagementScoped per engagementScoped per engagementCustom, contact sales
Secure enclave (not available today)Not available todayNot available todayNot available todayNot available todayNot available todayNot available todayNot available today
On-prem (scoped proof of concept)Scoped per engagementCustomer infrastructureScoped per engagementScoped per engagementStrict residency, internal governanceArchitecture review requiredCustom, contact sales
Edge runner (not available today)Not available todayNot available todayNot available todayNot available todayNot available todayNot available todayNot available today
Customer VPC / VNet (scoped per engagement)Scoped per engagementScoped per engagementScoped per engagementScoped per engagementScoped per engagementScoped per engagementCustom, contact sales
Private Kubernetes execution (scoped per engagement)Scoped per engagementScoped per engagementScoped per engagementScoped per engagementScoped per engagementScoped per engagementCustom, contact sales
Endpoint agents (scoped per engagement)Scoped per engagementScoped per engagementScoped per engagementScoped per engagementScoped per engagementScoped per engagementCustom, contact sales

Secure deployment pricing depends on model, footprint, and implementation scope. View enterprise deployment pricing

Enterprise governance

Control planes, approval workflows, and audit evidence

Human approval, least-privilege access, and an evidence record for each run.

Remediation approval workflow

Governed path from detection to verified fix.

DetectProposeApproveApplyVerifyAudit
  • Role-based access, SSO, and separation of duties
  • Human approval before governed remediation in production paths
  • Evidence handling agreed per deployment
  • Audit trails for planning, execution, approvals, and administrative actions
Examples

Example deployment topologies

Examples only. Every placement other than Zof Cloud is scoped per engagement. Your architecture review would define the exact placement of each plane.

Cloud-managed architecture

Zof-managed control plane and execution.

Zof Cloud (customer tenant)Control planePolicies & approvalsOrchestrationExecutionManaged runnersEvidence store

Customer VPC execution (scoped per engagement)

An example only. Execution in your VPC is scoped per engagement.

Customer VPC / VNetCustomer networkControlIntelligenceTransfer gatewayExecution agentApplications

Hybrid execution (scoped per engagement)

An example only. Hybrid setups are scoped per engagement.

Cloud / private cloudCustomer execution estateControlIntelligenceVPC runnerCustomer siteEndpointData center

Endpoint agent (scoped per engagement)

An example only. Desktop and endpoint testing are scoped per engagement.

Control planeOrchestrationEndpoint agentDesktop / VDILocal evidence

Private Kubernetes execution (scoped per engagement)

An example only. Execution in clusters you manage is scoped per engagement.

Control plane (customer or Zof)Customer Kubernetes clusterControl planeApproveNamespaceExecution agentWorkloadsSecretsArtifactsTelemetry boundary

Distributed runners (scoped per engagement)

An example only. Runners across sites are scoped per engagement.

Control planeSite ASite BSite CSite D

Remediation approval workflow

Governed path from detection to verified fix.

DetectProposeApproveApplyVerifyAudit

Telemetry flow (scoped per engagement)

An example only. What telemetry may leave is agreed during a data flow review.

RunnerLocal storeRedactionApproved egress

Evidence routing (scoped per engagement)

An example only. What evidence may leave is agreed during a data flow review.

CaptureLocal onlySanitizedMetadata only

In practice

Choose an environment by the work it must support

Deployment planning starts with the target applications, permitted data flows and operational responsibilities. Managed cloud is the starting option; on-premises work is a scoped proof of concept, and other private arrangements require engagement-specific review. Confirm feasibility before treating a configuration as available.

  1. 01

    Describe the execution needs

    List the repositories, application targets and verification types in scope. Identify required network access, dependencies, credentials and external services. A network diagram alone does not establish that the checks can execute.

  2. 02

    Review data and administration

    Specify what source, test data and artifacts may be processed and retained. Identify who manages access, updates and incident handling. Review any permitted external model or service use explicitly.

  3. 03

    Prove the agreed configuration

    Run a representative workflow in the proposed environment. Verify access, execution, result retrieval and failure reporting. Document remaining dependencies and operating responsibilities before expanding the scope.

Illustrative scenario · not a customer result

A private staging application

The application is reachable only from the customer network. The evaluation must establish how authorized verification reaches it, which credentials it uses and how the reviewer receives results. Confirm that full path before choosing the deployment arrangement.

Questions to resolve before you begin

Does a deployment label define the data boundary?

No. The boundary depends on the actual services, network paths, model use and storage configuration. Review the proposed data flow and operating agreement.

Can every verification type run in every environment?

Execution dependencies vary. Confirm the required capabilities against the proposed network and infrastructure, including how unavailable dependencies are reported.

Next step

Plan your deployment with Zof

Walk through architecture, evidence controls, and a conservative pilot path with our deployment specialists.

01Zof Console

One surface for posture, operations, and what needs attention next.

The authenticated home that engineering, QA, and SRE teams open every day: quality posture, in-flight runs, coverage by module, and what needs attention next.

OPERATIONAL KPIs

  • Runs
  • Coverage
  • Risk

Live across every environment you ship to.

WORK SPINE

  • Specs
  • Tests
  • Schedules

From specification to scheduled regression.

GUARDRAILS

  • RBAC
  • SSO
  • audit

Every action attributable to a named human.

LIVE/console
Zof home command center showing 12 runs at 94% pass, 3 open critical issues, 84% coverage, four module traceability bars, the specification pipeline, upcoming schedules, and recommended next actions with an active-runs sidebar.
Example console home · Checkout Service · Staging.