Docs Getting started Pingtower What Pingtower is

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.

QuickstartSign up, mint a token, send one log line, watch it become an alert. About five minutes. Write a ruleMatch on shape, level, source or tag. Fire after N in M minutes. Renotify until someone acks. Add a hosted checkHTTP, API, browser, gRPC, WebSocket, TLS, DNS, ping, TCP and domain expiry, from multiple regions of the world. Publish a status pageComponents bound to your checks and rules, on ptwr.net or your own domain, public or members-only. Run probes with addonsA small Go agent for external servers: HTTP, TCP, DNS, TLS expiry, ping, host metrics and more. Run your own boxKeep alert data on your hardware. pingtower.com holds only the account and relays the page.

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.

your app→POST /v1/ingest→template + dedup→rules→alert→push · webhook · Slack · Telegram

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 agent you must run. On pingtower.com the service runs hosted checks itself (HTTP, TLS, DNS, ping, TCP, gRPC, WebSocket, domain expiry, multi-step API and browser checks, from Pingtower’s own servers in multiple regions of the world), and a rule can alert when a source goes quiet. Anything inside your network, from host metrics to UDP and mail servers, is the addons agent’s job, and its measurements arrive as ordinary events.
Not a status page first. Pingtower pages your team first. Its status pages tell your customers once someone has acknowledged the outage or it has lasted 15 minutes, so a blip that clears in a minute never reaches them.
Not a ticketing system. An alert opens, gets acked, gets resolved. Incidents group alerts and can open a GitHub or GitLab issue where your tickets already live.
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.

Hosted firstEverything in these docs works on the hosted service without installing anything. Self-hosting and the addons agent are optional layers on top.

Where things are

Getting started: quickstart, the nine nouns, and the three kinds of credential.
The service: ingest, hosted and browser checks, rules, alerts, incidents, status pages, maintenance, uptime reports, log search, secret detection, integrations, actions, on-call, 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.