PriorStates Studio · for Alerts

PriorStates Studio Link

When something breaks on a server, it shows up in Alerts on your phone.

A Studio add-on for the machines that stay on: servers, scheduled jobs, build machines. One small program, with nothing to keep running and no port to open, puts alerts in the Gallery app Alerts and can ring your phone. All it can do is add an alert: it can't read your alerts back, and it can't reach your phone or your computer.

Set it up

Four steps, on two devices: your phone with PriorStates Studio, and the machine that will send alerts. About five minutes.

  1. 1

    Get a code on your phone

    In PriorStates Studio, open Alerts (add it from the Gallery if you don't have it), then Setup → Add. You get a code like PT-GESN-NXPB. It works once, for half an hour.

  2. 2

    Install Link on the machine

    On the machine that will send alerts, run the one-line installer below, or download the file for your system.

  3. 3

    Enroll it and send a test

    Run priorstates-link enroll PT-GESN-NXPB --name web-1, then priorstates-link test. The test alert appears in Alerts on your phone.

  4. 4

    Send from your scripts

    From a script, a scheduled job, a build step or your monitoring: priorstates-link send --sev1 --service backup "Nightly backup failed".

Made for machines that stay on

One small file

About 6 MB, with no runtime and nothing that starts at boot. Linux, macOS and Windows.

No open port

It only sends. Nothing on the machine has to be reachable from the internet.

Sealed end to end

Each alert is sealed on the machine with a key that only your phone holds, so the relay that carries it can't read it.

Repeats are counted

The same alert again is one line with a count, not a new line each time.

Rings when it matters

Turn on Ring this phone in Alerts and a sev1 rings even when Studio is closed. Ringing is best effort, not a pager.

One machine at a time

Each machine has its own key. Revoke one in Alerts and the others keep working.

Your data

What Link keeps on the machine, what it can do with it, and what it can't.

What it does

  • It keeps one credential for each phone it enrolled with, in a file that only its user can read.
  • With it, it can add an alert to those phones: a severity, a service, a title, a detail and a link.
  • Alerts go through our relay sealed, and the relay stores only what it can't read. Alerts lists each machine and when it last sent.
  • If a phone hasn't collected its alerts for a week, Link says so when it sends, so a phone that is gone doesn't fail quietly.

What it doesn't do

  • It can't read any alerts, reach your phone or computer, or enroll another machine.
  • No account, no background service, no open port.
  • It sends nothing but the alerts you send.

Get Studio Link

For Linux and macOS (x86-64 and ARM) and Windows (x86-64). Free.

Linux and macOS: one line

curl -fsSL https://priorstates.com/link/install.sh | sh

It checks the download against the published checksums. It's about forty lines; read it first if you like: install.sh

Or download the file

SystemFile
Linux · x86-64priorstates-link-linux-amd646.0 MBDownload
Linux · ARM64priorstates-link-linux-arm645.6 MBDownload
macOS · Apple siliconpriorstates-link-macos-arm645.7 MBDownload
macOS · Intelpriorstates-link-macos-amd646.1 MBDownload
Windows · x86-64priorstates-link-windows-amd64.exe6.1 MBDownload

Version 1.1.1 · Checksums: SHA256SUMS

The macOS files aren't notarized yet: the first time, allow it in System Settings → Privacy & Security → Open Anyway.

Wiring it into your systems

The integration guide, in English, shows alerts from code in any language, cron, systemd, CI and Prometheus Alertmanager, more than one phone, phone calls and text messages for what must reach someone, and running your own relay.

Read the integration guide