Keep vs Oncall (LinkedIn)
Self-host pick — both replace PagerDuty (On-call rotation / incident response / paging).
Both Keep and Oncall (LinkedIn) self-host as a replacement for PagerDuty (On-call rotation / incident response / paging). Pick Keep if you want a MIT-licensed codebase (MIT); pick Oncall (LinkedIn) for BSD (BSD-2-Clause). Both run in roughly the same cost bracket — $10-20 vps; sms/voice via twilio at the usual per-leg rate ($0 vs $10 vps; pair with iris (sister project) for paging — same upstream twilio cost.
| Keepopen-source | Oncall (LinkedIn)open-source | |
|---|---|---|
| License | MIT | BSD-2-Clause |
| Setup time | 30min docker-compose (keep-frontend + keep-backend + websocket-server; SQLite default, swap to Postgres via `DATABASE_CONNECTION_STRING`) | 30min docker-compose (Oncall + MySQL + Iris for paging) |
| Monthly cost | $10-20 VPS; SMS/voice via Twilio at the usual per-leg rate ($0.0075-0.05/leg). | $10 VPS; pair with Iris (sister project) for paging — same upstream Twilio cost. |
| GitHub | keephq/keep | linkedin/oncall |
| Replaces | PagerDuty | PagerDuty |
Good fit for
Keep
Teams that want alert dedup, correlation, and workflow automation alongside on-call paging — i.e. the noisy-alerts problem and the on-call problem solved by the same tool. Currently the most actively maintained option in this category.
Weak at:Pure on-call scheduling UI is thinner than PagerDuty's — Keep leads with alert orchestration, not rotation calendars. If all you need is 'who's on-call this week', the workflow surface is more than you'll use.
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, Keep or Oncall (LinkedIn)?
Keep: 30min docker-compose (keep-frontend + keep-backend + websocket-server; SQLite default, swap to Postgres via `DATABASE_CONNECTION_STRING`). Oncall (LinkedIn): 30min docker-compose (Oncall + MySQL + Iris for paging).
What does each cost to run?
Keep: $10-20 VPS; SMS/voice via Twilio at the usual per-leg rate ($0.0075-0.05/leg).. Oncall (LinkedIn): $10 VPS; pair with Iris (sister project) for paging — same upstream Twilio cost.. Both projects are free and open source.
Do Keep and Oncall (LinkedIn) replace the same SaaS?
Yes — both are open-source alternatives to PagerDuty.