Domain, DNS and uptime management for agenciesEvery client account, under one roof
You run your clients’ stacks, and the risk isn’t the work — it’s the one renewal nobody owned. InfraNest puts every client’s domains, DNS, servers and uptime in one shared workspace, so your team sees the whole roster at a glance.
Free plan · No credit card · Set up in minutes
- Made in Germany
- No migration needed
- Tokens encrypted at rest
- Export anytime, no lock-in
- koster-bouw.nlUp · all green
- northwind.ioSSL expires in 6 days
- studio-muller.deUp · 118 ms
- bakerst-clinic.co.ukDNS drift detected
- lumen-agency.nlUp · 96 ms
Every client account in one shared workspace.
The problem
A typical Monday at an agency
Monday starts with an email from a client: the contact form has stopped sending. Someone opens the hosting panel, then the registrar, then the DNS provider, and finds that the client’s IT contractor “tidied up” the SPF record on Friday. Nobody noticed, because nothing was watching.
By lunch the same problem has turned up in another form. A certificate on a site you launched two years ago expires in six days, and the reminder went to a developer who left in the spring. A domain renewal sits in a shared inbox, waiting for someone to decide it is theirs.
None of this is hard work. It is scattered work: client after client, spread across registrars and hosts, and nobody who sees all of it at once. InfraNest connects to the providers your clients already use and puts every domain, zone, certificate and monitor in one place the whole team can see. It watches what changes and tells you before the client does.
The old way
- A different login for every client account
- DNS set up slightly differently each time
- Renewals owned by whoever remembers
- Clients emailing to ask if they’re down
With InfraNest
- Every client in one shared workspace
- One DNS template applied across the roster
- Expiries owned by the team, not a person
- Branded status pages clients check themselves
How it works
How an agency runs on InfraNest
Every client’s domains in one list, wherever they are registered
Connect each registrar and DNS provider your clients use, with an API token from that account. Every domain it holds appears with its renewal date, renewal price, auto-renew and transfer lock. Tag domains by client and the list narrows to one client in a click. Switch auto-renew or change the contact on twenty domains at once instead of logging in twenty times. Nothing is transferred: each domain stays at its registrar, in the account it was in.
- Domains appear as soon as a registrar is connected, with nothing to import by hand
- Tags and custom fields on every object, so one filter shows one client’s whole setup
- Auto-renew, contacts and tags changed across many domains at once
- Export to CSV on every plan, for the client report or the handover
The same DNS baseline for every client, and an alert when it drifts
Most agencies have a standard setup: the mail records, SPF, DMARC, CAA and whatever your hosting needs. Save it as a template and apply it to a new client’s zone in one step, with a preview of every record before anything is written. After that, InfraNest keeps checking what each domain actually answers on the public internet. When a record changes outside InfraNest, because a contractor or a plugin edited it, you see the exact record, its old and new value, and a button to put it back.
- Your own templates, plus presets for Google Workspace, Microsoft 365 and a security baseline
- A preview of every record before it is written, with anything it would replace flagged
- Changes made outside InfraNest caught per record, to restore or to keep
- One editor for Cloudflare, Route 53, TransIP, Hetzner and the other providers your clients use
Email
Slack
Teams
Discord
Telegram
PagerDutyRenewals and certificates owned by the team, not by whoever remembers
Every client domain and certificate is checked continuously, and the overview opens with what needs attention: auto-renew switched off, an expiry coming up, nameservers that do not answer, a certificate whose renewal failed. Alerts go to a shared channel such as Slack, Teams or email instead of one person’s inbox, so the reminder does not leave when a colleague does. InfraNest also finds the certificates you had forgotten about, on subdomains and old launches.
- Expiry, auto-renew and transfer lock watched on every client domain
- Certificates discovered across subdomains, with a warning when a renewal fails
- Alerts to Slack, Teams, Discord, Telegram, email or PagerDuty
- Every expiry on one renewal calendar you can add to your own
Cloudflare
5 other checks passed
A status page per client, so “is the site down?” answers itself
Clients email when they are worried, usually when you are busiest. Give each one a status page instead, built from the monitoring you already run. When a check fails the page updates on its own, and the client can subscribe to email updates. Put it on the client’s own domain, such as status.client.com, with their logo and colours; HTTPS is handled for you. On Business, checks run from Europe, North America and Asia-Pacific, and a site only counts as down when several regions agree, so nobody is told about an outage that never happened.
- Built from your monitors, so there is no status to update by hand
- The client’s logo, colour and domain, with HTTPS set up for you
- Public or password-protected, per page
- Every incident at a permanent link you can send the client
Northwind Cloud Status
status.northwind.example
Major outage
Checkout & payments is down
Scheduled maintenance this weekend
We'll be upgrading our database cluster on Saturday 02:00–03:00 UTC. Brief API slowdowns are possible; no downtime is expected.
Public
Developer
Get notified
6 of 8 services up · 100% 90-day uptime · 3 subscribers·Powered by InfraNest
See your own client roster in about ten minutes
Connect one registrar and one DNS provider. Nothing transfers, and nothing changes until you ask it to.
Getting started
Onboard a client in a few minutes
Connect once, and every account joins the same overview.
Connect the client’s providers
Add each registrar and host with an API token. Their domains, zones and servers appear in your workspace.
Apply your DNS template
Roll out your standard records and security baseline, with a diff preview before anything changes.
Publish a status page
Give the client a branded page to check uptime themselves, and route alerts to the right people.
How you actually do it
Step-by-step guides for the jobs on this page.
What you get
What changes on day one
401
Dashboards your team logs into
emailself-serve
How clients check if their site is up
0100%
Client zones on a consistent DNS template
The cost of doing it separately
Buy each piece from a different tool and it adds up fast:
- Uptime monitoring
- ~€26
- SSL tracking
- ~€15
- Status page
- ~€26
- Across 3 separate tools
- ~€67/mo
Also in Pro, not counted above: 100 domains with DNS, 10 servers across your cloud providers, 25 automations, Dynamic IP and Drop Catch.
Each line is that tool’s cheapest paid plan. Pro covers all of it: 50 monitors, 100 certificates and 3 status pages on your own domain.
Prices checked October 2026 · dollar prices at the ECB rate
Questions
Questions agencies ask
Can we separate clients from each other?
Yes, two ways. Tag each client’s domains and filter the whole list down to one client, or give a client an organisation of its own and switch between them from one login. Business includes five organisations; Enterprise has no limit.
What do clients see?
Their status page, and only if you publish one. Make it public or password-protected, on the client’s own domain. Everything else stays inside your workspace.
How do DNS templates handle exceptions?
Apply the template everywhere, then override per zone where a client needs something specific. Drift detection flags anything that changes outside InfraNest.
Can status pages carry the client’s brand?
Yes. Logo, accent colour and the client’s own domain, with HTTPS handled for you. Removing the “Powered by InfraNest” line is part of white-label on Enterprise.
Do we need our clients’ registrar passwords?
No. You need an API token from each account you want to manage. Where the client owns the account, they create a token and send it to you, so nobody shares a password. Tokens are encrypted at rest, and revoking one at the provider disconnects it straight away.
Do we have to move client domains or DNS?
No. Domains stay at their registrar and zones stay at their DNS provider. InfraNest works through the providers’ APIs, and nothing changes at the provider until you edit something.
How many clients fit on Business?
Business has unlimited domains, 200 monitors with multi-region checks, unlimited status pages, five organisations and ten team members. Agencies that outgrow it move to Enterprise, which lifts the limits.
What happens if we stop using InfraNest?
Nothing goes offline. Domains and zones were never moved, so they are exactly where they were. Export your inventory first if you want it: CSV on every plan, JSON and scheduled exports on Business.
Not quite you?
Client infrastructure, under control.
Managing infrastructure for a roster of clients means a hundred moving parts. InfraNest gives your team one source of truth across every account — with templates, drift detection and status pages that make you look buttoned-up.
Free plan · No credit card required · Set up in minutes