Cabot vs Oncall (LinkedIn)
Self-host pick — both replace PagerDuty (On-call rotation / incident response / paging).
Both Cabot and Oncall (LinkedIn) self-host as a replacement for PagerDuty (On-call rotation / incident response / paging). Pick Cabot if you want the lighter footprint — 20min docker-compose (Cabot + Postgres), $5 vps; sms via twilio at the usual per-leg rate. Pick Oncall (LinkedIn) if you need larger orgs that already use Iris for paging and want a calendar-shaped rotation tool with strong audit logs — 30min docker-compose (Oncall + MySQL + Iris for paging) and $10 vps; pair with iris (sister project) for paging — same upstream twilio cost.
| Cabotopen-source | Oncall (LinkedIn)open-source | |
|---|---|---|
| License | MIT | BSD-2-Clause |
| Setup time | 20min docker-compose (Cabot + Postgres) | 30min docker-compose (Oncall + MySQL + Iris for paging) |
| Monthly cost | $5 VPS; SMS via Twilio at the usual per-leg rate. | $10 VPS; pair with Iris (sister project) for paging — same upstream Twilio cost. |
| GitHub | cabotapp/cabot | linkedin/oncall |
| Replaces | PagerDuty | PagerDuty |
Good fit for
Cabot
Small teams that want a simple on-call + uptime monitoring combo in one app, without the Grafana ecosystem dependency.
Weak at:**GitHub repo returns 404** — `cabotapp/cabot` is no longer reachable on github.com (renamed, deleted, or moved); freshness pill renders as `unknown`. Treat as unmaintained until a successor namespace is confirmed. Maintenance had already slowed for years; fewer integrations than Keep.
Oncall (LinkedIn)
Larger orgs that already use Iris for paging and want a calendar-shaped rotation tool with strong audit logs.
Weak at:**Last commit Aug 2025** — repo is unarchived but no longer actively pushed (freshness pill: stale). Two-component setup (Oncall + Iris); UI looks 2018; less active than Keep or pre-archive Grafana OnCall.
In a terminal? npx -y github:SolvoHQ/os-alt-cli pagerduty prints PagerDuty's self-host options including both —
how the CLI works →
FAQ
Which is easier to self-host, Cabot or Oncall (LinkedIn)?
Cabot: 20min docker-compose (Cabot + Postgres). Oncall (LinkedIn): 30min docker-compose (Oncall + MySQL + Iris for paging).
What does each cost to run?
Cabot: $5 VPS; SMS via Twilio at the usual per-leg rate.. Oncall (LinkedIn): $10 VPS; pair with Iris (sister project) for paging — same upstream Twilio cost.. Both projects are free and open source.
Do Cabot and Oncall (LinkedIn) replace the same SaaS?
Yes — both are open-source alternatives to PagerDuty.