// the find
linkedin/oncall
Oncall is a calendar tool designed for scheduling and managing on-call shifts. It can be used as source of dynamic ownership info for paging systems like http://iris.claims.
LinkedIn's open-source on-call scheduling tool, built to manage shift rotations and serve as a dynamic ownership source for paging systems like Iris. It's a self-hosted Python/MySQL web app with a REST API, iCal export, and pluggable auth/notification backends. Aimed at ops teams that want to own their scheduling data rather than pay for PagerDuty.
The API surface is genuinely thorough — roster suggestions, event swaps, overrides, subscriptions, and audit logs are all first-class endpoints, not afterthoughts. The scheduler is pluggable: round-robin, no-skip-matching, and multi-team variants ship out of the box and the interface is simple enough to write your own. iCal export per-user and per-team means it integrates with any calendar client without any extra glue. The e2e test suite is unusually complete for an internal tool that was open-sourced — coverage across events, rosters, schedules, notifications, and overrides.
MySQL as the only supported backend in 2025 is a real constraint — no Postgres support, and the schema files are raw SQL dumps with manual versioning rather than a proper migration system, so upgrades are fragile. The frontend is vanilla jQuery + Handlebars with vendored, years-old copies of Bootstrap 3 and jQuery 3.3.1, making any UI customisation painful and leaving known CVEs in the bundle. Auth is LDAP-or-debug-module only; there's no OIDC or SAML support built in, so anyone not on LDAP has to write their own module. The last meaningful activity is sporadic — this reads like a tool LinkedIn open-sourced and then largely stopped investing in, so you're probably on your own for anything beyond the existing feature set.