Watching one domain is a scheduling problem. Watching thirty clients' domains is a bookkeeping problem, and that is the one this solves.
Create an organization for each client, add their domains and their IP ranges, and set the cadence once. Efflux runs the captures, surveys, permutation checks, and scans from there, and keeps the history on each link.
Built for the people who do this for a living
If you are an MSSP, a consultancy, or an internal team covering several business units, the work is the same every week and the reporting has to stay separate. Organizations give you that separation without maintaining a schedule per domain per job type.
A reasonable starting point for a new client looks like weekly captures and surveys, monthly permutation checks, and a weekly scan of their ranges. Then you adjust per client instead of per host.
Everything in one place when you need it
Because the history lives on the link, you can open a client and see what their surface looked like last month next to what it looks like now. That is the view you want when you are writing a report, onboarding a new domain, or answering why something changed.
You can also add ports to the scan on an IP range when a client runs something on a port the defaults do not cover.
Where to go next
Monitoring covers organizations, domain links, IP links, and history. Certificates are a separate watch: see Certificate Monitoring.