태세, 운영, 그리고 다음으로 주목해야 할 사항을 위한 하나의 표면입니다.
The Zof home is not a marketing dashboard. It is the operational surface engineering, QA, and SRE teams use every day: quality posture, in-flight runs, coverage by module, and the actions a leader should look at next.
운영 KPI
- 실행
- 커버리지
- 리스크
출시하는 모든 환경에서 실시간으로 제공됩니다.
작업 중추
- 사양
- 테스트
- 일정
사양에서 예약된 회귀 테스트까지.
가드레일
- RBAC
- SSO
- 감사
모든 작업은 이름이 명시된 사람에게 귀속됩니다.

- 01 · RUNS · 24H
94% pass
12 runs across staging
- 02 · COVERAGE
84%
Across four modules
- 03 · ACTIVE RUNS
3 running
Live on this branch
- 04 · NEXT ACTIONS
Recommended
Triage gaps, new spec
Start Here
Orient to the platform and core concepts before diving into workflows.
What is Zof Console?
The Zof Console is the central control surface for autonomous reliability infrastructure.
Quickstart
Complete your first project workflow in under 30 minutes.
Key Concepts
Core terminology and mental models for projects, agents, runs, and governance.
Console Tour
Navigate the Console: Home, Operate, Quality, Automation, Governance, and Platform.
Console Workflows
Operate projects, tests, runs, agents, and reliability governance from the Console.
Create your first project
Create a project, connect an application, and prepare for test generation.
Test execution
Run validation through the Console, schedules, and Agent Console.
Agents overview
Specialized AI testing agents orchestrated under enterprise policy.
Remediation
Governed remediation with policy-driven approval and audit trails.
Developers
Integrate Zof into pipelines and applications with API, SDK, and CLI references.
API Reference
REST API for programmatic access to projects, runs, agents, and reports.
SDKs
Official client libraries for Node.js, Python, Go, and Java.
CLI
Command-line interface for execution, configuration, and pipeline integration.
CI/CD integration
Trigger governed validation from GitHub Actions, GitLab CI, Jenkins, and more.
Reference
Guides, troubleshooting, FAQ, and canonical terminology.
무엇이 변경되었는지 파악하고, 무엇을 테스트해야 할지 파악하세요.
토폴로지를 인식하는 영향 분석이 서비스 변경을 영향받는 워크플로에 연결하고, 시스템 의존성을 기반으로 검증 계획을 추천합니다.
시스템 컨텍스트를 활용해 검증 우선순위를 정하세요.