Start Here
What is Zof Console?
The Zof Console is the central control surface for autonomous reliability infrastructure.
Overview
Zof AI delivers autonomous reliability infrastructure for modern engineering organizations. The Zof Console is the web-based control plane where platform, QA, SRE, and governance teams orchestrate the full reliability lifecycle, from requirements and test design through governed execution, analysis, remediation, and release decisions.
Unlike lightweight QA automation tools, the Console is built for enterprise scale: multi-team operations, policy-driven agent orchestration, audit trails, human approval gates, and integration with existing CI/CD and issue-tracking systems. Every action, test generation, run execution, remediation proposal, is traceable and scoped to your organization.
Most teams begin in the Console to connect applications, ingest requirements, review AI-assisted test output, execute validation runs, and report reliability posture to stakeholders. Developers extend the same capabilities through the REST API, SDKs, CLI, and pipeline integrations documented in the Developers section.
Who should read this
- Engineering leaders, platform teams, QA leads, SREs, security and compliance reviewers evaluating or operating Zof.
When to use this workflow
- Onboarding a new organization or business unit to Zof
- Explaining Zof to procurement, security, or executive stakeholders
- Distinguishing Zof Console from Agent Console, Zof Studio, and external integrations
Platform mental model
Platform mental model
How Console, agents, and integrations relate in a typical enterprise deployment
Step-by-step procedure
Confirm access
Verify organization membership and role permissions in Admin Center.
Confirm API key or SSO session is scoped to the correct tenant.
Apply this guidance
Follow Console navigation paths and API examples in this document.
Use staging project and environment IDs for first-time integration tests.
Verify outcomes
Check Operate → Runs, Quality areas, or API responses for expected results.
Update team runbooks when your stack requires environment-specific variations.
Key concepts
- Zof Console
- The product control plane for reliability operations, not a generic dashboard or chatbot interface.
- Agent Console
- An operational area inside the Console for cloud and endpoint execution fleets, not the product name.
- Topology
- The Console view of system dependencies (System Graph) used for impact and coverage analysis.
Best practices
- Validate changes in staging before applying release gates to production.
- Include run IDs and timestamps when escalating issues to support or auditors.
- Align internal runbook terminology with Zof Console UI labels for clarity.
Was this page helpful?