Changelog
What changed, and when
HopMango is worked on every day, and a product that changes in silence looks like a product nobody is looking after. So every day that shipped something you can see or rely on gets an entry here, written in plain words rather than copied out of our commit messages.
2026-09-08 · Three servers, a public status page, and a digest in the morning
The platform moved to redundant hardware, the portal was rebuilt to be read at a glance, and the API stopped being something you had to have an account to read about.
- HopMango now runs on three servers in three zones with automatic failover. If one of them goes away, the other two keep answering, and nothing you configured is lost.
- A public status page. Choose the monitors you are happy for the world to see and publish them on a page anyone can open, with no account and no password.
- A daily digest by e-mail. One message a day with what happened to your systems, so nobody has to keep a dashboard open to stay informed.
- A failing website check now says why. Instead of a bare “down”, a monitor names the cause it actually found: the certificate, the name that did not resolve, the redirect that went somewhere else, the request that never finished.
- Invite your team by e-mail. Roles decide who can change what, removing somebody takes their access away on their very next request, and every mail we send says when its link stops working and arrives in the language of the person reading it.
- The portal, rebuilt. Hosts, checks, events and settings were reworked to be understood in one look, the whole thing works on a phone, and the first hour after signing up now explains itself instead of leaving you on an empty screen. Every sentence is available in English and in Spanish, including the ones the platform writes itself.
- Prices on the website, and the door open. The plans and what they cost are published, and anyone can open an organization on the free plan without a call and without a card.
- Thirty days of Team, on the house. Every new organization starts on the Team plan for thirty days: more servers, more website checks, a month of history and alerts by phone, with no card asked for. When the month is up the organization goes on with the free plan and nothing is deleted; whatever is over the free limits is simply frozen until you choose a plan.
- And the trial tells you what its ending will change, before it ends. The billing screen lists exactly what is different for your organization on that date - which of your things go over the free limits, which ways of alerting stop, and how much history is kept - and if nothing of yours changes it says so in one line. We also write, a week, three days and one day before, so the date is never a surprise.
- Public documentation. The API and the way to connect an assistant to HopMango are now documented in the open, in both languages, next to a page that says plainly what our agent will never do on your machines.
- Six Skills you can download. An assistant you already use can learn HopMango from them and work with your monitoring the way you would.
- The installer verifies signatures by default. What it downloads is checked against our signature before a single file is installed, and it refuses to continue if the check fails.
- The agent reloads its file. Edit its configuration file and it picks the change up without a restart, and it will now answer questions about its own state from the shell.
- A PostgreSQL check. It watches archiving, the write-ahead log and replication, and tells you when a database has quietly stopped keeping up.
- Mango AI, more useful and still only a proposal. It names the thing it is talking about, groups incidents that share a cause and shows what it spent in dollars. It proposes; it never touches your systems.
2026-09-07 · On-call, Mango AI, three regions, and a way to sign up
The night the product stopped being a monitoring agent and became something a team can be on call with.
- Mango On-Call. Rotations that survive daylight saving time, escalation ladders, covering a colleague's shift, and acknowledging a page from a link without signing in first. Voice calls go out through our own number.
- Mango AI. It summarises an incident, suggests a likely cause and answers questions about what it is allowed to read. It proposes; it does not act, and it never sees your secrets.
- Website checks run from three regions. A site is watched from three points of presence, so one bad network between us and you is not reported as your outage.
- A site that refuses our probes reads “blocked by the target”, not “down”. And a monitor can be sent through a firewall with a header of your choosing, so a protected site can be watched honestly.
- Sign up with an e-mail address. A visitor becomes an organization by verifying an address. No sales call, no waiting list.
- Plans, and limits that are enforced everywhere. Every limit bites in the platform rather than in the screen, so an API key and an assistant are refused exactly as a browser is, and the refusal names the plan, the current count and the call that lifts it.
- The portal speaks Spanish. Every screen, in English and in Spanish.
- Silence an incident from its own page, with or without an account, reopen one that was closed too early, and see the checks an incident was built from.
- Delete your own account from the portal. Without asking us, and without a form.
- Your visitors' countries. Real-user monitoring now reports where a session came from.