Everything TerranPage does today
Every capability on this page is live. Public self-serve signup is still rolling out — see Available now and Coming soon on the home page.
Paging & escalation
When an alert is raised, TerranPage resolves the target team's on-call rotation and starts the escalation chain: step 1 immediately unless you set an initial delay, later steps on the delays you set — up to 10 steps and 24 hours per chain. Escalation stops the moment anyone acknowledges. If no step answers, the chain exhausts visibly — an explicit event in the log, so an unanswered page is never a quiet one.
- Per-person escalation chains with per-step delays, including an optional delay before step 1
- Critical pages are labeled end-to-end — subject line, console, and iOS badge
- Repeat firings deduplicate into the open alert instead of paging twice
- Notification storms are suppressed and recorded as events
On-call schedules
Rotations tell TerranPage who's up so the chain starts with the right person.
- Daily, weekly, or monthly rotation rules per team
- Overrides layer on top for swaps, vacations, and sick days — the original schedule stays intact underneath
- The team screen shows who is on call right now, and degenerate states are named plainly: "No schedule", "No one on call"
Getting alerts in
- REST API — raise an alert with one authenticated POST. Keys are created in-app and scoped to a single team.
- Alertmanager webhook — point Prometheus Alertmanager at TerranPage natively; no translation shim.
- Email ingest — every API key gets a private ingest address; mail that passes industry-standard authentication checks from your verified senders becomes an alert. Anything else is rejected and logged.
- Manual page — "Start a page" from the web console or iOS app, to a team or a person, normal or critical.
Pages deliver by verified email, SMS or voice call on the Pro plan, and push to the iOS app — never a single channel to fail.
Acknowledge & close
- Acknowledge links are embedded in the delivered page — one tap marks you as handling it, no sign-in required, and everyone else sees it instantly
- Acknowledge and close from the alert screen on web or iOS
- Late or duplicate actions are safe: "already closed" is a recorded no-op, not an error
The event log
Every alert carries a complete, append-only story: raised, escalation started, each notification sent or skipped, storms suppressed, re-fires, acknowledgement, close — with names and timestamps. Delivery receipts track each send against the provider, so "did the page actually go out?" has an answer.
Organizations, teams & roles
- Organizations are fully isolated tenants — teams, alerts, contact methods, and keys are scoped to the org and access-checked on every request
- Roles: org admins run the org, team admins run their teams, members get paged
- Invite teammates by email, optionally straight into a team and role
- Every person belongs to exactly one organization, so teams and permissions stay unambiguous
- Org admins can require two-factor sign-in for every member, enforced the next time they sign in
Contact methods & privacy
- Contact details are owner-only: teammates see your name in a chain, never your phone number or address
- Email, SMS, and voice contact methods are verified with a 6-digit code before they can be paged (voice reads the code aloud on a call; codes expire in 15 minutes); a push destination is your own device, verified automatically when the app registers it
- Contact methods are self-registered only — up to 2 emails, 2 SMS numbers, and 2 voice numbers per person
Usage, statements & spend protection
- Every accepted send lands in a metered usage ledger the org admin can see
- Monthly statements roll up in-app — Pro subscribe and wallet top-ups are available in the product console
- Daily send allowances per organization stop runaway loops; org suspension is immediate and reversible
Security
Access to TerranPage is limited to authorized accounts. Each organization's data is scoped and access-checked on every request. We apply controls intended to reduce account abuse and unauthorized access — we do not publish implementation details of those controls here.
- Optional two-factor sign-in with an authenticator app — any member can turn it on from their profile