Apache httpd monitoring
Monitoring and control for Apache httpd.
Health, SSL certificate expiry, logs and remote lifecycle commands for every Apache server — hosted for you, or installed on your own servers.
Free plan for up to 1 instance. Paid plans include a 14-day trial.
Everything you need to keep Apache healthy
One dashboard for every instance, in every environment.
Live health
Process status, uptime and mod_status traffic for every Apache instance, in one dashboard.
SSL certificate tracking
Expiry monitoring across every HTTPS virtual host, with warning thresholds you set.
Remote lifecycle
Start, stop, restart and graceful reload from the dashboard — no shell access needed.
Logs & configuration
Read error and access logs and the active configuration of each server from the browser.
Uptime history
Health and certificate history with hourly rollups, kept per plan.
Sign-in options
Local users with roles, Duo MFA from Professional, plus LDAP / Active Directory, SAML 2.0 and OpenID Connect on Enterprise.
How it works
Install the agent
A small agent on each Apache httpd server. The agent connects out to the server over one encrypted WebSocket; nothing connects in to the Apache host.
Connect it
Run sudo httpd-agent setup and paste the values the dashboard shows you.
Watch and act
Health, logs and alerts arrive within seconds — and you can start, stop and restart from the browser.
Hosted or on your own servers
Same product, two ways to run it.
Hosted
We run the HTTPDwatch server. Install only the agent.
- Ready in minutes — sign up and connect an agent
- Updates, backups and availability handled by us
- Monthly or annual billing; change plans any time
- Each organization fully isolated
Self-hosted
The whole product inside your network, from RPM packages.
- RHEL, Oracle Linux, Rocky or AlmaLinux 8 and 9
- One self-contained package — no runtime to install
- Your data never leaves your servers
- Free license for 1 instance; paid licenses on request
What's different
| Hosted | Self-hosted | |
|---|---|---|
| Who runs the server | We do. You install only the httpd-agent agent on each Apache httpd host. | You do: the httpd-monitor package on your own RHEL, Oracle Linux, Rocky or AlmaLinux 8/9 server. |
| Where your data lives | On our servers, kept separate for each organization. | Only on your server. Nothing about your instances leaves your network. |
| Network | Each agent connects out to our service over HTTPS (wss://) — the Apache httpd hosts need outbound internet access. | Agents connect only to your own server, so Apache httpd hosts can stay off the internet. The server itself checks its license over HTTPS, and keeps running for 48 hours if it cannot reach it — or runs with no internet at all on an offline license file. |
| Updates, backups, HTTPS | Included — we update, back up and run it with HTTPS. | Yours: dnf upgrade, your backups, and your own certificate in front of it. |
| Uptime & event history | Kept 7 days on Starter, 30 on Professional, 90 on Enterprise. | Live status, health and alerts; no stored history. |
| Plans and paying | Pay by card, monthly or annually; change plan any time from Billing in the app. | A license key with the same plans and limits. Free is issued during setup; paid keys on request. |
| Organizations | One sign-in can belong to several organizations and switch between them. | One organization per installation. |
| Sign-in (Duo, LDAP, SAML, OIDC) | Each organization connects its own Duo account and identity provider from Settings; people are invited first. | Set up in Settings on your server; directory and SSO users sign in directly, with their role taken from their groups. |
| Support tickets (Professional+) | In the app, with new replies flagged as they arrive. | In the app as well; open the Support page to see new replies. |
| Getting started | Sign up and connect an agent — ready in minutes. | Install one package, open the setup page, enter the setup code. |