Free
- 10 monitors
- 5-minute checks
- 1 server agent
- E-mail, Telegram, Discord, Slack alerts
- 1 public status page
- 30-day history
Starter
- 50 monitors
- 1-minute checks
- 5 server agents
- 3 monitoring locations
- SMS & WhatsApp alerts
- 3 status pages
- API access
- 90-day history
Pro
- 200 monitors
- 30-second checks
- 25 server agents
- All monitoring locations
- Hosting panel integrations
- White-label status pages
- 10 team members
- 1-year history
Business
- 1,000 monitors
- 30-second checks
- 100 server agents
- Unlimited locations & channels
- Custom status-page domains
- 50 team members
- Priority support
- 2-year history
Agency
- 5,000 monitors
- Multiple client organisations
- White-label everything
- Unlimited team members
- Client reports
- 2-year history
Compare the limits
| Limit | Free | Starter | Pro | Business | Agency |
|---|---|---|---|---|---|
| Price | Free | $9.00 /month | $29.00 /month | $79.00 /month | $149.00 /month |
| Monitors | 10 | 50 | 200 | 1,000 | 5,000 |
| Fastest check interval | 5 min | 1 min | 30 seconds | 30 seconds | 30 seconds |
| Monitoring locations | 1 | 3 | 6 | Unlimited | Unlimited |
| Server agents | 1 | 5 | 25 | 100 | 500 |
| Alert channels | 2 | 10 | 30 | Unlimited | Unlimited |
| SMS & WhatsApp alerts | — | ||||
| E-mail alerts | |||||
| Status pages | 1 | 3 | 10 | 50 | Unlimited |
| White-label status pages | — | — | |||
| Badges & embeds | |||||
| Team members | 1 | 3 | 10 | 50 | Unlimited |
| API tokens | 1 | 5 | 20 | Unlimited | Unlimited |
| API requests per minute | 60 | 60 | 60 | 60 | 60 |
| Reports | |||||
| History kept | 30 days | 90 days | 365 days | 730 days | 730 days |
| Free trial | — | 14 days | 14 days | 14 days | 14 days |
Frequently asked questions
Straight answers to the questions people ask most before and after they sign up for AllInOneMonitor. If your question is not here, the documentation goes into more detail, and you can always ask us through the contact page.
Getting started
What exactly does AllInOneMonitor do?
AllInOneMonitor checks your websites, APIs, servers and other services around the clock and tells you as soon as something breaks, slows down or is about to expire. Checks run from monitoring locations in several regions, the history is kept so you can see uptime and response times over time, an incident is opened automatically when something goes down, and you can publish the state of your services on a status page for your customers.
It brings together what usually takes several separate tools: uptime and API checks, SSL and domain expiry warnings, cron-job heartbeats, server metrics, real-browser and multi-step checks, alerts, reports and status pages.
Do I need to install anything?
Not for most monitoring. Website, API, keyword, ping, port, DNS, SSL, domain, heartbeat, transaction, browser and database or mail protocol checks all run from our side: you only enter the address and choose the settings.
You install something only if you want metrics from inside a server, such as CPU, memory, disk usage or running services. That needs our small read-only agent, installed with one command on Linux or Windows (see Servers below). The mobile apps and browser push notifications are optional extras.
Can I start for free without a card? Is there a trial?
Yes. The Free plan needs no payment card and has no end date: it stays free for as long as you use it, with checks every 5 minutes, one monitoring location per monitor and 30 days of history.
Paid plans can come with a 14-day free trial that gives you the plan's limits; nothing is charged during the trial. When you need more monitors, shorter intervals, more locations, SMS or WhatsApp alerts or longer history, upgrade from the billing area. Current plans and limits are on the pricing page.
Monitoring
How often are my monitors checked, and from where?
The interval depends on your plan: every 5 minutes on Free, every minute on Starter, and down to every 30 seconds on Pro, Business and Agency. You can always choose a longer interval for a monitor that does not need to be checked so often.
Checks run from monitoring locations (we call them probes) in several regions. For each monitor you pick the locations it is checked from, up to your plan's limit: one on Free, more on the higher plans.
A failed check is not reported straight away. It is checked again, and when the monitor uses more than one location, another location has to confirm the failure before the monitor is marked down and an alert goes out. A short network blip at one location therefore does not wake you at night, while a real outage is still reported within a check or two.
Which kinds of monitors can I create?
There are 20 monitor types:
- Web: HTTP(S), Keyword (a text must be present or absent) and API (rules on the status code, headers and JSON or XML body).
- Network: Ping (ICMP), Port (TCP) and DNS (record types with expected values).
- Expiry: SSL certificate (expiry, chain, hostname) and Domain expiry (RDAP/WHOIS).
- Jobs: Heartbeat, for cron jobs and background tasks.
- Synthetic: Transaction (multi-step journeys) and Browser (a real headless browser).
- Protocols: MySQL/MariaDB, PostgreSQL, Redis, MongoDB, Memcached, SMTP, IMAP, POP3 and FTP.
Transaction checks walk through a journey over HTTP, such as signing in, filling in a form or adding an item to a cart, carrying cookies and variables from one step to the next and checking each step with assertions. Browser checks open the page in a real headless browser and record the load time, First Contentful Paint, Largest Contentful Paint, layout shift (CLS), the number of requests and a screenshot, so you see what a visitor sees. Use a browser check when the page needs JavaScript to work; a transaction check is lighter and is enough for server-rendered flows. Browser checks are heavier, so an interval of 5 minutes or more is recommended for them.
How do I monitor a cron job or background task?
Use a Heartbeat monitor. It works the other way round from the other checks: we do not call your server, your job calls us. Create the monitor, set how often the job runs (from 30 seconds up to 7 days), and add one line at the end of the job that requests the heartbeat URL shown on the monitor, for example with curl or wget.
If no call arrives within the expected interval plus a grace period (by default half the interval), the monitor goes down and you are alerted. This catches jobs that crash, hang or silently stop running: backups, imports, queue workers, scheduled reports. Because the job makes an outgoing request, heartbeats also work for machines behind a firewall or on an internal network.
Will you warn me before my SSL certificate or domain expires?
Yes. An SSL certificate monitor reads the certificate during the TLS handshake and checks its expiry date, chain of trust, hostname match and TLS version. You choose how many days before expiry the warning starts (1 to 90, default 14). HTTP(S) monitors can check the certificate of the same address too.
A Domain expiry monitor looks the domain up through RDAP, with WHOIS as the fallback, and warns you from a number of days you choose (1 to 365, default 30). Warnings are repeated once a day during the window and become critical in the last days. A few registries do not publish an expiry date; in that case the check tells you so instead of guessing.
Alerts
Where can alerts be sent, and are SMS and WhatsApp included?
Alerts can go to e-mail, SMS, WhatsApp, Telegram, Slack, Discord, Microsoft Teams, your own webhooks, and mobile push through the Android and iOS apps or browser Web Push. You choose the channels for each monitor; a monitor without its own channels uses your default channels. When a monitor comes back up, a recovery message is always sent so you know the problem is over.
SMS and WhatsApp alerts are available on paid plans, because every message has a delivery cost. The pricing page shows what each plan includes. Tip: set a cooldown on SMS channels so a monitor that keeps going up and down cannot send dozens of messages.
Can I silence alerts at night or during planned work?
Yes, in several ways:
- Quiet hours per channel (set in UTC) skip that channel during the window, for example 23:00 to 07:00. Recoveries still come through. Keep at least one channel without quiet hours for the problems that must wake someone up.
- Cooldown per channel limits how often the same channel is alerted.
- Escalation: if an incident has not been acknowledged after the number of minutes you set, your escalation channels receive one extra message. Acknowledging the incident stops it.
- Maintenance windows silence alerts for the chosen monitors during planned work and can be shown on your status page.
The alerts documentation explains each setting in detail.
Servers
Which operating systems does the server agent support, and what does it collect?
The agent runs on Linux (a bash script) and Windows (PowerShell). You install it with one command copied from the panel, and it sends metrics every minute over HTTPS.
On Linux it collects CPU (per core), memory, swap, load, disks, inodes, disk I/O, network, processes and services, and, where the tools are present, Docker, SMART, RAID, temperatures, CloudLinux LVE, PHP-FPM and web server status, MySQL, PostgreSQL, Redis and MongoDB, mail queues, firewall state and pending updates. The Windows agent collects fewer things: CPU, memory, disks, network, processes, services, the state of IIS and SQL Server services and, optionally, the number of pending Windows updates.
You set thresholds per server, for example disk usage or CPU load, and get an alert when a value crosses them. See Servers in the documentation.
Is the agent safe to run on a production server?
It is designed to be. The agent is read-only: it reads metrics and never changes anything on the server. It never opens a port and never accepts commands; it only makes outgoing HTTPS requests to send its data. There is nothing to open in your firewall, and there is no way for our service to make your server run something.
It is a small script that runs once a minute, so its CPU and memory use is small. Database passwords that some collectors need stay on your server in a file only root can read. You can uninstall the agent at any time and delete the server from your panel.
Status pages
Can I give my customers a status page, and can it be private or on my own domain?
Yes. A status page shows the monitors and servers you choose as components, with your logo, the overall state, uptime, current and past incidents with your updates, and scheduled maintenance. A page can be public, private (only signed-in members of your organisation) or password-protected.
On the higher plans you can serve the page on your own domain, such as status.example.com. Visitors can subscribe by e-mail: they confirm their address once and then receive every public incident update, with an unsubscribe link in each message. Embeddable badges and widgets show your status on your own website. See Status pages in the documentation.
API & integrations
Is there an API, and how do tokens and webhooks work?
Yes. The REST API (v1) lets you create and manage monitors and read results, incidents, servers and status pages from your own scripts and tools. You create API tokens in the panel and give each one only the scopes it needs, for example read-only; a token can be revoked at any time. API access and the rate limit depend on your plan; the default is 60 requests per minute.
Outgoing webhooks send events such as monitor down or recovered to your own URL. Every request is signed, so your code can verify that it really came from us. The full reference is on the developers page.
Does it work with my hosting panel or cloud provider?
Integrations read data, read-only, from cPanel/WHM, Plesk, DirectAdmin, CyberPanel, Webmin/Virtualmin, aaPanel, CloudPanel and JetBackup, from AWS, Google Cloud, Azure, DigitalOcean, Hetzner and Vultr, and from Kubernetes. Stopped services, instances, pods or failed backup jobs show up as alerts in your account, and the data can be shown next to a server's agent metrics. The credentials you enter are stored encrypted.
Integrations show only what each provider's API exposes, so they complement the server agent rather than replace it.
Data & security
How long do you keep my data, and can I export or delete it?
Raw check results are kept for your plan's history period:
| Plan | Raw check history |
|---|---|
| Free | 30 days |
| Starter | 90 days |
| Pro | 1 year |
| Business and Agency | 2 years |
Daily uptime summaries are kept for up to 2 years. Raw server metrics are kept for up to 30 days and hourly server summaries for up to 2 years. Alert records are kept for 1 year.
You can export reports as CSV and download an export of your account data. You can delete monitors, servers and your whole account at any time; the results of deleted monitors are removed by our regular clean-up job. Details are in the privacy policy.
How is my account and data protected?
All traffic uses HTTPS. Account passwords are stored only as hashes, never in plain text. You can turn on two-factor authentication with an authenticator app (with recovery codes), review your login history and, in a team, give each member a role with only the permissions they need; important actions are recorded in an audit log.
Integration credentials, alert-channel settings and the passwords of database monitors are encrypted at rest. Card numbers are entered on the payment gateway's own page, so AllInOneMonitor never sees or stores them. If AI incident summaries are enabled, passwords and secrets in monitor targets are removed before anything is sent.
Can I monitor internal or private IP addresses?
No. Targets that resolve to private or internal network addresses (such as 10.x, 192.168.x or localhost) are refused. This protection, known as an SSRF guard, makes sure nobody can use our checks to reach into a private network, including yours.
To watch something inside your network, install the server agent on a machine there, or use a Heartbeat monitor that your internal job calls. Both only make outgoing connections, so nothing has to be exposed. For a service that must be checked from outside, publish a protected health-check endpoint on a public address.
Billing
How can I pay, and where do I find my invoices?
Paid plans are billed monthly or yearly in advance; the yearly cycle costs less. You can pay by card and international gateways (Stripe, PayPal, Paddle, Razorpay, Paystack) or with Bangladeshi methods (SSLCommerz, bKash, Nagad, aamarPay). Manual bank transfer and mobile "Send Money" are also accepted: you enter the transaction ID and can upload a proof, our staff review it, and the plan is applied once it is approved. The checkout shows the methods currently available.
Card numbers are entered on the gateway's own page; AllInOneMonitor never sees or stores full card numbers. Every invoice, with its status and a printable view, is in the billing area of your account.
Can I get a refund?
Yes, within limits. New customers get a 7-day money-back guarantee on the first payment of a paid plan, monthly or yearly. After 7 days the current billing period is not refunded, and there are no pro-rata refunds for unused time or downgrades. Duplicate or mistaken charges are always refunded in full. A free trial costs nothing; if it turns into a paid plan and you cancel within 7 days of that first charge, the guarantee applies.
To ask for a refund, write from your account e-mail address through the contact page with the invoice number. The full rules, including how long refunds take for each payment method, are in the refund policy.
How do I cancel or move to a smaller plan?
You can cancel at any time from the billing area. Cancelling stops the renewal; your plan keeps working until the end of the period you have already paid for. We send reminder e-mails before a subscription ends.
When a paid plan ends, your organisation moves to the Free plan. Your monitors are not deleted, but while you are above the Free plan's limits you cannot add new ones, and features the Free plan does not include, such as extra locations, SMS alerts or API access, stop working. You can upgrade again at any time and everything picks up where it left off.
Still have a question? Browse the documentation or write to us through the contact page. The people who build AllInOneMonitor answer.
Something else? Ask us

