Infrastructure
Connections
How infrastructure enters Infraova — connecting providers, the access model, and what becomes operable after a connection is made.
What a connection is
A connection is an authorized link between Infraova and an external infrastructure provider. When you connect a provider, Infraova is granted access to that provider's API — either through an API key you provide or through OAuth authorization. The connection is the foundation for everything else. Without a connection, Infraova cannot monitor or operate the infrastructure on that provider.
What connections enable
A connection does two things. First, it gives Infraova read access — the ability to pull infrastructure data, map DNS zones, read authentication records, and receive health signals. Second, where you have granted write access, it gives Infraova the ability to execute approved remediations against that provider. Read access is always required. Write access is required for remediation.
Types of connections
Infraova supports three categories of connections. DNS provider connections give Infraova access to DNS zones and records — these are the primary connections for monitoring and remediation. Email infrastructure connections give Infraova context about the email platforms behind a domain — these are used for monitoring and health scoring but not for DNS remediation. Sending platform connections give Infraova access to sending metrics and deliverability signals.
How credentials are stored
API keys and OAuth tokens are encrypted at rest and never exposed after they are saved. Infraova stores only what it needs to maintain the connection. You can revoke a connection at any time from the Integrations settings — revoking removes Infraova's access immediately.
Note
Revoking a connection stops monitoring and remediation for all domains on that provider. Issues detected before revocation remain in the record.
Connection status
Every connection has a status. A healthy connection is actively pulling data. A degraded connection is experiencing API errors or rate limit issues. A broken connection has lost authorization — the API key may have been rotated or the OAuth token may have expired. Infraova surfaces connection health in the Integrations dashboard so you can catch broken connections before they create monitoring gaps.
Multiple connections of the same type
You can connect multiple providers of the same type. If your clients have domains spread across Cloudflare and GoDaddy, you connect both. Infraova manages them independently and maps each domain to the provider where its infrastructure lives.
What happens after you connect
After a connection is established, Infraova runs an initial discovery pass. It maps the zones and records available through the connection and links them to any matching domains in your account. Monitoring begins for those domains automatically. The first monitoring results appear within minutes of a successful connection.