Infraova Documentation
Everything you need to operate client infrastructure with Infraova.
Learn how Infraova connects to client infrastructure, continuously monitors it, detects and prioritizes problems, proposes remediation, executes approved changes, verifies results, and records every operational outcome.
The operating model
Every article in this documentation belongs to one stage of the operating model. The sidebar follows the same structure.
Learn how Infraova turns connected infrastructure into a controlled operational workflow.
DNS Providers
Email Infrastructure
Communication
Monitoring
Monitoring frequency
Authentication checks
DNS checks
Reputation monitoring
SSL and certificates
Detection
Detection events
Domain issues
Authentication failures
DNS changes
Detection status
Prioritization
Issue severity
Health scores
Portfolio health
Critical vs warning issues
Proposals
What is a proposal?
How proposals are generated
Reviewing proposed DNS changes
Proposal status
Approvals
Reviewing a proposal
Approving a change
Rejecting a proposal
Approval history
Remediation
How remediation works
DNS remediation
Provider execution
Failed remediation
Verification
How verification works
DNS verification
Post-remediation checks
Verification failures
Reports
Weekly reports
White-label reports
Operations timeline
Sharing with clients
White-label Reports
Custom branding
Logo and colors
Client-facing PDF
Report delivery
Approval boundary
Infraova does not bypass the approval boundary for infrastructure changes.
The operator decides whether the proposed remediation should proceed. Every change that affects connected client infrastructure requires an explicit decision before Infraova executes it.
Documentation explains how Infraova works. Guides show you how to accomplish a specific job — preparing domains for cold email, fixing SPF problems, moving from monitoring to automated remediation.
Explore Guides →Elsewhere in the docs