Solutions · Hosting providers

One box, 400 sites.
Finally priced like it.

Hosting density breaks most monitoring twice: the tooling drowns in vhosts, and the per-host pricing pretends a packed server equals an empty VM. Wakora treats sites as the first-class unit — discovered from the real config, watched individually, counted honestly.

Real configs
Vhosts come from the web server's own config dump — panel-generated layouts, custom paths and all.
Folded
Aliases, www and port duplicates collapse into one site. You see the exact list you pay for.
Per site
Certificates, DNS health, domain expiry and drop-catch — watched per site, not per server.
<1% CPU
One static binary per box, probes on a rotating budget. Density never turns into load.

The failure modes only hosters know

A panel migration leaves one php-fpm pool dead and 30 sites answering 502 — while the server is "up" and every host-level check is green. A client's domain expires, the zone dies, and a drop-catcher re-registers it the same week. An origin certificate rots behind Cloudflare for months because visitors see the edge cert. Wakora alerts on all three, because it watches every site's response codes, DNS resolution, registration dates and certificate — including the origin one.

Bots are not outages

On shared hosting the error logs are a bot zoo: scanners probing for wp-config, .env and a thousand PHP paths that never existed. Wakora separates that noise from real breakage by shape and by response status — a broken docroot fails its few real entry points for many visitors; a scanner sprays hundreds of paths from one address. Your on-call sleeps through the scanners and wakes for the broken site.

The plumbing under the sites

php-fpm pools are discovered per version with workers, saturation and queue backlog per pool. Databases, mail, DNS, FTP and panels are recognized and monitored with real checks, not just process presence. Undersized pools get a rightsizing insight instead of a mystery of slow sites. And when a whole box misbehaves, host story and per-service logs are one click from the incident.

Onboarding at fleet scale

One install command per box; registration is rate-limited and capped by your plan, so a mass rollout with your config tool converges by itself.

Billing that respects density

Hosts and sites are separate, visible counters, billed on the monthly average — a migration weekend never becomes a billing event.

A path to reselling

When monitoring becomes part of your offer, the Agency plan adds white-label, client workspaces and wholesale pricing.

Frequently asked

How does Wakora count sites on a dense server?
Discovery parses the live web-server configuration, then folds aliases, the www variant and port duplicates into one site, and drops catch-all and redirect-only blocks. The console shows the exact folded list you are billed on — on real panel-managed boxes that turns hundreds of raw vhost entries into the honest number of actual sites.
Will probing hundreds of sites load my server?
No. Per-site probes run over loopback on a rotating budget with paced starts, so a 400-site box sees a slow trickle, never a burst. The agent itself is a single static binary that idles well under 1% CPU.
Can I offer monitoring to my own customers?
Yes. The Agency plan adds client workspaces under your own white-labeled console and domain, wholesale usage pricing, and consolidated billing to you — you set the retail price, and your clients never see our invoice.

Put your densest box on the free plan.

If it survives that one, the rest is easy. Three hosts, no card.

Start free White-label for your clients