Oncall (LinkedIn)
Open-source · self-hostable · replaces 1 SaaS tool on os-alt
linkedin/oncall · stale · ★ 1.25k · last commit 9mo ago · 79 open issues
License: BSD-2-Clause
Good fit for 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
the PagerDuty comparison table including Oncall (LinkedIn).
how the CLI works →
Replaces these SaaS
- PagerDuty · On-call rotation / incident response / paging
LinkedIn's Oncall is purely the rotation/calendar layer; pair it with `linkedin/iris` for actual paging. Migration: dump PagerDuty schedules to JSON, write a script that POSTs them as Oncall events. Wire alert sources to Iris webhooks instead of PagerDuty's. There is no UI mass-importer — the API path is the realistic one.
README badges for the SaaS this replaces
Maintainers and forks: drop a badge in your README to link readers from the SaaS-comparison page back to your repo.
FAQ
Is Oncall (LinkedIn) actively maintained?
Slowing — last commit 9mo ago. Counted as stale (between 90 days and 1 year since the last commit).
What does Oncall (LinkedIn) cost to self-host?
Oncall (LinkedIn) is free and open source under BSD-2-Clause. Typical self-host VPS cost: $10 VPS; pair with Iris (sister project) for paging — same upstream Twilio cost.
Which SaaS does Oncall (LinkedIn) replace?
Oncall (LinkedIn) is listed as an open-source self-host alternative to: PagerDuty.