Skip to main content
[ PIER ]

Alerts & notifications for self-hosted infrastructure

Catch failing deploys, crashed containers, expiring SSL and runaway CPU before your users do — with delivery to Telegram, Discord, Slack and email.

10 preset rules out of the box

CPU, RAM and disk thresholds; container crashed; deploy or backup failed; agent offline; SSL certificate expiring soon; container CPU and RAM hot-spots. Each rule has tunable thresholds and per-rule cooldown windows so you don't drown in pages.

Four notification channels

Telegram, Discord, Slack and email — channels are first-class entities, so one rule can fan out to multiple destinations and you can route warning vs. critical events differently.

Three alert states with audit trail

Each rule tracks ok / warning / critical. Every state change is recorded as an alert event you can inspect after the fact, so post-mortems don't depend on Slack scrollback.

Built into the binary

No Prometheus, no Alertmanager, no extra container. The Pier core evaluates rules in a Tokio task and dispatches notifications directly — works on a 512 MB VPS.

Set up alerts in Pier

  1. 01

    Open Settings → Notifications

    Add a Telegram bot token, Discord webhook, Slack webhook or SMTP credentials. Channels are encrypted at rest.

  2. 02

    Open Settings → Alert rules

    Pick one of the 10 preset rules or define a custom threshold. Set the cooldown window.

  3. 03

    Attach channels to the rule

    Choose which channels receive warning vs. critical events. You can attach multiple channels to a single rule.

  4. 04

    Trigger a test event

    Hit the Test button on the rule — Pier dispatches a sample notification to verify wiring without waiting for a real incident.

Common questions

Can I write custom alert rules?

Yes — the 10 presets cover the common cases, but every rule is editable: threshold, comparison operator, evaluation window and cooldown. The same rules engine is used for both presets and custom rules.

Does Pier support PagerDuty or Opsgenie?

Not as first-class channels in v1.0 — but most paging services accept email or Slack webhooks, both of which are supported. PagerDuty Events v2 support is on the roadmap.

How does the cooldown work?

When a rule fires, Pier records the event and suppresses re-firing for the configured cooldown window. If the underlying condition is still true after the cooldown, a follow-up notification is sent — so you stay informed without being spammed.

Related

Read the docs See what shipped

Ready to deploy?

One command installs Pier on any Ubuntu or Debian VPS.

curl -fsSL https://pier.sh/install | sudo bash
Read the docs Sponsor Us