Pingtower is live. The app is in review.

As of today, Pingtower is a real service you can sign up for. The hosted tower runs at api.pingtower.com, signups are open, and the whole thing is free while we’re in pre-release. One curl creates your account; a second one creates your team.

Here’s exactly what’s live, what’s signed, and what’s still sitting in a review queue at Apple.

The hosted tower is open

Everything the server does — shape-based deduplication, declarative rules with thresholds, escalation ladders that repeat until someone acks, on-call rotations, runbook actions, incident reports — runs hosted now. POST a log line with a source token and the pipeline is yours: repeats collapse into one alert with a count, your rules decide what opens an alert, and integrations fan out to Slack, Telegram, and HMAC-signed webhooks.

There’s no waitlist and no card. Pre-release means free; the terms spell out how pricing would arrive when it does. The get-started page has the three requests that take you from nothing to ingesting.

Or run it on your own box

The server is one static Go binary with its data in SQLite files, and as of today the releases are published and signed: a minisign signature per binary, SHA-256 sums in the open, and the release public key on the download page. Verify both before you run it — the trusted comment names the artifact, version, and commit it was signed for.

The same goes for the addons agent, the probe binary that watches your services from outside: signed tarballs, one signed SHA256SUMS covering all of them, and an installer that verifies the manifest before anything runs as root.

The app is at Apple’s door

The missing piece is the one in your pocket. The native iOS app — the pager whose critical alerts sound through Silent mode — is built and in Apple’s review pipeline, starting with the first TestFlight build. We’re not going to guess at Apple’s timeline; when the app ships, the App Store link lands on this site and alerts start reaching phones.

Until then, Pingtower pages you the way it already can: Slack, Telegram, and signed webhooks, driven by the same rules and ladders the app will use. Nothing about your setup changes when the app ships — your tower is already doing the paging; the app just answers it.

What happens next

Weekly release posts keep landing here as the app moves through review and the server keeps shipping. If you want the details of what’s live today, the new features, app, and how it works pages lay the whole thing out — and if you want an agent to do the setup for you, the agent guide is written for exactly that.