For hosting providers
Domain monitoring for hosting providers.
Hosting providers use Aepto to watch the customer-facing side of every domain: uptime from outside the network, pages that return 200 but are broken, DNS and nameserver changes, expiring certificates, and status pages for customers. Keep your server monitoring for CPU and disk. Aepto covers the domain layer above it.
What do customers expect their host to notice first?
These are the tickets that arrive as screenshots while your server dashboards stay green.
- Their site shows a white screen or database error, but still returns HTTP 200.
- An SSL certificate expired on a customer domain you host DNS for.
- A DNS record or nameserver changed and mail or the website went elsewhere.
- A customer domain is about to expire at a registrar you don't control.
- A site is slow for one region only, so a single probe never sees it.
- Several customers ask "is it down?" at once and support answers each by hand.
What should Aepto do next to your existing hosting tools?
Keep server monitoring where it is. Add the customer-facing domain layer.
| Job | Keep in your stack | Add Aepto for |
|---|---|---|
| Server health (CPU, disk, hypervisor) | Server agents and provider metrics | Not needed |
| External uptime per customer site | Often missing | Multi-region checks across customer domains |
| "Up but broken" CMS pages | Rarely covered | Content Monitoring, paid plans |
| DNS and nameserver drift | Usually manual | DNS monitoring and Theft Guard |
| Certificates across customer domains | Partial (ACME logs) | SSL expiry checks |
| Customer communication | Ticket macros | Public status pages |
| Alert routing | Your existing on-call channels | Webhooks into the same channels, paid plans |
What is changing for customer domains?
Three shifts that add work for hosting providers.
398 → 47 days
maximum lifetime of public TLS certificates, cut in steps from March 2026 to March 2029
Source: CA/Browser Forum SC-081
5,000 a day
senders above this to Gmail must have SPF, DKIM and DMARC in place (since February 2024)
Source: Google Workspace Admin Help
WordPress 5.2
added fatal error recovery mode, which emails the admin a recovery link when a plugin or theme crashes the site
Source: Make WordPress Core
Which plan fits your customer book?
Pick by the number of customer domains you want in one account.
| Customer domains | Plan | Price | Alert contacts | Regions |
|---|---|---|---|---|
| Up to 25 | Professional | $29 a month | 15 | 4 |
| Up to 50 | Business | $59 a month | 50 | 6 |
| Up to 150 | Agency | $129 a month | 100 | 6 |
| More than 150 | Enterprise | Custom | Custom | 6 |
Start on Free or Starter to test on a slice. Full limits on Pricing.
How do you pilot it with one customer group?
Prove alert quality on a slice before you scale.
- 01
Pick a slice
One reseller book or one product line, not every customer on day one.
- 02
Folder by customer
Client boundaries stay obvious and alerts route cleanly.
- 03
Route alerts
Send webhooks to the channel your team already watches.
- 04
Measure for 30 days
Count alerts that named a real problem against noise.
- 05
Scale the plan
Business covers 50 domains and Agency 150. Larger books go to Enterprise.
Where does AI help, and where should checks stay plain?
Use AI where it removes clerical work: filling in details when you add customer domains, and reading page content for failures. Keep uptime, SSL and DNS checks deterministic so the answer is the same every time. The AI monitoring guide has the full breakdown.
Common questions
Short answers to what people ask before they start.
Does Aepto replace server monitoring?
No. Server agents and provider metrics answer questions about CPU, disk and hypervisors. Aepto watches each customer domain from outside: uptime, SSL, DNS, renewals and page content. Use both.
Which AI features matter for a hosting provider?
Quick Add fills in registrar, hosting, SSL and DNS details for each customer domain, and Content Monitoring reads pages that return HTTP 200 but are broken. Uptime, SSL and DNS checks stay deterministic.
How many customer domains can one Aepto account cover?
Business covers 50 domains and Agency covers 150, with a folder per customer. Larger books move to Enterprise. Limits match the live Pricing page.
Can status pages reduce support load?
Yes. A status URL you can send during an incident replaces screenshot threads. White-label status pages start on Professional.
Can we send alerts into our existing ops channels?
Yes, on paid plans. Webhooks deliver to Slack, Microsoft Teams, Discord or any HTTP endpoint, so alerts land where your team already works.
What should hosters demand from monitoring?
One inventory across client brands, renewal/SSL visibility, DNS drift alerts, alert routing into Slack/email, and optional status pages.
How does Aepto fit agencies and hosters?
Portfolio ops, Attention triage, multi-region uptime, Theft Guard, paid Content Monitoring and webhooks, plus status pages for client-facing status.
Know about customer domain problems first.
Start free on a customer slice. Scale with Agency when volume is real.