What Pingtower is
Point your services at Pingtower. When something breaks, the alert reaches your phone the moment it opens. Ack it, resolve it, or read the log lines behind it, without opening a laptop.
How the pieces fit
Pingtower is two halves. The service is the inbound half: it ingests structured log lines, recovers each message’s shape, evaluates your rules, and keeps alert state with re-notify escalation until someone acknowledges. The iOS app is the outbound half: it is what actually wakes a human at 3 a.m.
Anything that can make an HTTP request can be a source: an application, a cron job, a log shipper, or the addons agent probing something from the outside.
What it is not
- Not an uptime prober. The service itself runs no HTTP, TCP or ping checks, and nothing in it alerts on silence. Outside-in checks are the addons agent’s job, and its measurements arrive as ordinary events.
- Not a status page. Pingtower tells you first. Telling your customers is a different product.
- Not a ticketing system. An alert opens, gets acked, gets resolved. That is the whole lifecycle.
- Not a dashboard you have to remember to check. If you are looking at Pingtower, it is because it paged you.
Where it runs
The service is hosted at api.pingtower.com. Accounts, tenants, memberships and push live there, and signups are open and free during preview. If you would rather keep alert data on hardware you own, run the daemon yourself and pair it from the app: your box keeps the sources, logs and alerts, and pingtower.com only relays the page to your phone.
Where things are
- Getting started: quickstart, the seven nouns, and the three kinds of credential.
- The service: ingest, rules, alerts, integrations, actions, on-call, reports, team, plans.
- iOS app: install, the feed, critical alerts, pairing.
- Self-hosting: what is hosted and what is not, installing the daemon, TLS, the relay.
- Addons agent: install, configure, every addon and sensor.
- Reference: errors, rate limits, and links to the generated API reference.
- FAQ and troubleshooting.