Getting Started
Clients & Domains
How Infraova organizes the infrastructure you are responsible for — organizations, clients, domains, and operational history.
The data model
Everything in Infraova is organized around a simple hierarchy. Your organization contains clients. Each client contains domains. Each domain contains the infrastructure Infraova monitors and operates. This structure mirrors how agencies actually work — you manage infrastructure on behalf of clients, and each client has one or more domains.
What is an organization
Your organization is the top-level account in Infraova. It contains everything — all clients, all domains, all connections, all team members, and all reports. If you are an agency, your organization represents the agency. All billing, settings, and API access are managed at the organization level.
What is a client
A client represents one of the businesses or accounts you manage infrastructure for. Clients are the primary way Infraova groups domains — every domain belongs to a client. A client has a name, and optionally contact information used for white-label reporting. The client record is the unit you report against when you send domain health or operational reports.
What is a domain
A domain is the core unit of monitoring in Infraova. When you add a domain, Infraova begins watching it — checking its DNS records, email authentication configuration, SSL certificates, and reputation signals. A domain belongs to exactly one client. All issues, proposals, remediations, and verifications are associated with the domain they affect.
Domain health
Every domain in Infraova has a health score. The health score reflects the current state of the domain's infrastructure — DNS configuration, authentication records, SSL status, and reputation. A domain with no issues has a healthy score. A domain with critical issues has a degraded score. Health scores roll up to the client level and the portfolio level so you can see the overall state of everything you manage.
Operational history
Every action Infraova takes on a domain is recorded. The domain's operational history shows every detection, every proposal, every approval, every remediation, and every verification — with timestamps and actors. This is the audit trail for the domain. If a client asks what changed and when, the operational history is the answer.
How domains are associated with infrastructure
When you add a domain, Infraova checks your connected providers for matching infrastructure. If the domain is on a connected DNS provider, Infraova maps the DNS zone automatically. If email infrastructure is connected for the same domain, Infraova links the sending context. The more infrastructure you connect, the more complete the picture Infraova builds for each domain.
Note
A domain can have infrastructure spread across multiple connected providers — DNS on Cloudflare, email on HubSpot, sending on Instantly. Infraova tracks all of it under the same domain record.
Archiving and removing domains
If you stop managing a domain, you can archive it. Archived domains are removed from active monitoring but their operational history is preserved. If you remove a domain entirely, its history is deleted. Archiving is recommended when a client relationship ends — it preserves the record without continuing to monitor infrastructure you are no longer responsible for.