# Zof

> Zof is the independent verification and control layer between AI and production. It maps what a change can affect, verifies behavior, records evidence, and enforces whether an action may proceed.

Zof is the primary brand name. Zof AI is an alternate name for the same company and product. Official website: https://zof.ai.

Zof is designed for engineering, platform, reliability, security, and compliance teams responsible for critical enterprise systems. Its architecture combines System Graph, Verification Engine, evidence, and Control Plane. Human approvals apply where policy requires them.

## Start here

- [About Zof](https://zof.ai/about): Company identity, architecture, audience, and the limits of verification.
- [Product overview](https://zof.ai/product): The independent verification and control platform.
- [How it works](https://zof.ai/product/how-it-works): The change, verification, evidence, and authorization workflow.
## Evaluate Zof

- [Reliability Sprint](https://zof.ai/sprint): A scoped engagement on one critical system; deliverables and scope are agreed with the team.
- [Pricing](https://zof.ai/pricing): Current commercial information and a route to discuss an engagement.
- [Trust](https://zof.ai/trust): Security, governance, and deployment information for evaluation.
- [Contact](https://zof.ai/contact): Contact Zof about scope, deployment requirements, and available evidence.
## Architecture and documentation

- [System Graph](https://zof.ai/product/system-graph): Dependencies, ownership, and context for change impact.
- [Verification](https://zof.ai/product/testing-fleets): Verification capabilities and evidence from checks.
- [Integrations](https://zof.ai/product/integrations): Connections with existing engineering systems.
- [Documentation](https://zof.ai/docs): Product concepts, setup, operations, and references.
- [Quickstart](https://zof.ai/docs/getting-started/quickstart): Getting started with a project and verification workflow.
- [System Graph documentation](https://zof.ai/docs/system-graph): How system context is represented and used.
## Published evidence and perspectives

- [Prove It](https://zof.ai/prove-it): Published experiments; each conclusion is limited to its documented setup and evidence.
- [The Reliability Thesis](https://zof.ai/reliability-thesis): Authored perspectives on verification and autonomous software.
- [Blog](https://zof.ai/blog): Technical articles and product perspectives with individual attribution.
- [Brand assets](https://zof.ai/brand): Official logos, brand guidance, and company boilerplate.

## Questions about Zof

### What is Zof, and is it the same as Zof AI?

Zof is the independent verification and control layer between AI and production. Understand changes, verify behavior, collect evidence, and control production risk. Zof AI is an alternate name for the same company and product. The official website is https://zof.ai.

### How does Zof work?

Zof combines four parts: a System Graph maps services, dependencies, ownership, and policies; a Verification Engine determines and runs the checks a change requires; evidence records what was checked and its outcome; and a Control Plane applies policy decisions such as allow, deny, require more evidence, or require human approval.

### Who is Zof designed for?

Zof is designed for engineering, platform, reliability, security, and compliance teams responsible for critical enterprise systems. It addresses changes proposed by people, coding agents, and automation, where teams need to understand impact and justify a production decision with evidence.

### Why does independent verification matter?

A proposed change and a claim that it works are different things. Independent verification checks the behavior and evidence required by policy before an action proceeds. Zof separates proposing a change from deciding whether the available evidence and approvals are sufficient.

### What are the limits of verification?

A passing check supports a conclusion about the scope, environment, inputs, and criteria that were tested. It does not prove that a system is free of every defect or safe under every future condition. Coverage, permissions, deployment constraints, and approval requirements need to be agreed for each engagement.

## Official profiles

- [github](https://github.com/Zof-AI)
- [linkedin](https://www.linkedin.com/company/zofai)
- [twitter](https://x.com/zof_ai)
- [instagram](https://www.instagram.com/zof.ai_/)
- [youtube](https://www.youtube.com/@zofai)

## Scope and evidence

A successful verification run supports a conclusion about its tested scope, environment, inputs, and criteria. It is not a guarantee that every defect or future failure has been ruled out. Product availability, deployment requirements, and commercial terms depend on the agreed engagement. The linked pages and their cited evidence provide the context for individual claims.

## More resources

- [Summary reading guide](https://zof.ai/llms.txt): Key evaluation pages.
- [Sitemap](https://zof.ai/sitemap.xml): Public URL discovery.
- [Crawler preferences](https://zof.ai/robots.txt): Published crawl rules.