Getting Started
How Infraova works
The complete operating model — how Infraova turns connected infrastructure into a controlled operational workflow.
The operating model
Infraova operates in a continuous loop across eight stages. Every action Infraova takes — every detection, every proposal, every executed change — belongs to one of these stages. Understanding the loop is the foundation for understanding every other part of the documentation.
Note
Stage 06 — Approve — is the only stage where a human must act. Every other stage is handled by Infraova. The approval boundary is enforced for every infrastructure change.
Connect — infrastructure enters Infraova
The loop begins when you connect a provider. Infraova connects to DNS providers, email platforms, and sending infrastructure through API integrations. A connection gives Infraova read access to monitor the infrastructure and, where approved, write access to execute remediation. Nothing is monitored or operated until a connection exists.
Monitor — continuous observation
Once infrastructure is connected, Infraova monitors it continuously. It checks DNS records, email authentication configuration (SPF, DKIM, DMARC), SSL certificates, domain reputation, and domain state on a regular schedule. Monitoring runs in the background at all times — you do not need to trigger it manually.
Detect — something changes
When monitoring finds something unexpected — a DNS record that changed, an authentication record that is misconfigured, a certificate that is expiring — Infraova creates a detection event. The detection event captures what changed, when it changed, and what the expected state should have been. Not every change is a problem, but every significant change is recorded.
Prioritize — not every problem is equal
Detection events are evaluated for severity and impact. Infraova assigns a severity level — critical or warning — based on the type of problem and its potential impact on deliverability, domain health, and client operations. A missing DMARC record is treated differently from a broken SPF record that is actively causing delivery failures. The prioritization layer tells you what to deal with first.
Propose — Infraova recommends what should happen
For actionable issues, Infraova generates a proposal. A proposal is a specific, concrete recommendation — the exact DNS record change, the precise configuration update — along with an explanation of why it is needed and what the expected outcome is. Infraova does not just tell you something is wrong. It tells you exactly what should change and why.
Approve — you decide
Every proposal that would result in an infrastructure change requires your approval. Infraova presents the proposal for review — what will change, what provider it affects, what the expected outcome is. You can approve it, reject it, or leave it pending. Infraova does not proceed without an explicit approval from an authorized operator.
Remediate — Infraova executes the approved change
Once approved, Infraova executes the change against the connected provider. For DNS changes, it writes the record directly through the provider API. Infraova tracks the execution status — initiated, in progress, completed, or failed — and records every action taken.
Verify — the change is confirmed
After execution, Infraova does not assume the change worked. It runs a verification pass — checking DNS propagation, re-running the affected monitoring checks, and confirming the infrastructure reached the expected state. If verification fails, Infraova surfaces a verification failure so you can investigate.
Report — the operational record
Every detection, proposal, approval, execution, and verification is recorded in the audit trail. Infraova generates reports — domain health, portfolio health, operational summaries — that can be shared with clients as white-label branded documents. The report is the proof that the work happened.
What Infraova does vs what you do
Infraova handles the observation, detection, diagnosis, execution, and verification. You handle the decision. The operating model is designed so that Infraova does everything it can do autonomously — and stops at the approval boundary to let you stay in control of every change that affects client infrastructure.