What is LinkedIn Oncall used for?

LinkedIn Oncall is a free, BSD-licensed, self-hosted calendar tool for scheduling and managing on-call shifts, designed to feed dynamic ownership data to paging systems. It is a good fit for managing on-call rotations for an engineering team and feeding ownership data to an incident paging tool.

Is LinkedIn Oncall open source?

Yes. LinkedIn Oncall is open source under the BSD-2-Clause licence. Its source code is on GitHub at linkedin/oncall and is written mainly in Python.

Is LinkedIn Oncall free?

Yes. LinkedIn Oncall is open source, so the software itself is free to use.

Can I self-host LinkedIn Oncall?

Yes. LinkedIn Oncall can be self-hosted on your own server or infrastructure; there is no official hosted version.

What is LinkedIn Oncall an alternative to?

LinkedIn Oncall is an open-source alternative to incident.io, Rootly, PagerDuty and FireHydrant. Other open-source alternatives to incident.io include Keep, OneUptime and HolmesGPT.

Is LinkedIn Oncall actively maintained?

The most recent commit to LinkedIn Oncall was on 20 August 2025, and the latest release is v2.1.7, published on 12 March 2024. The project has 1.3k stars on GitHub.

LinkedIn Oncall: open-source alternative to incident.io

About LinkedIn Oncall

Oncall is a calendar application built by LinkedIn specifically for scheduling and managing on-call rotations. It is aimed at operations and engineering teams who need to track who is responsible for responding to incidents at any given time, and it is designed to act as a source of dynamic ownership information for paging systems such as Iris.

As a calendar-focused tool, its core job is representing on-call schedules in a way that other systems can query programmatically, rather than functioning as a full incident-management platform on its own. It integrates into a broader on-call and alerting workflow where a paging tool consults Oncall's schedule data to determine who to notify.

Oncall is written in Python and requires a MySQL database, with setup instructions covering local development, Docker Compose deployment, and configuration through a YAML file; dummy data can be imported for testing. It is released under the BSD-2-Clause license, and the README notes some current limitations, including no built-in test-running mechanism documented and a need to rebuild to apply code changes in some setups.

Key features

On-call shift scheduling calendar
Dynamic ownership data for paging systems
MySQL-backed schedule storage
Docker Compose deployment option
Configurable via YAML

Good fit for

→Managing on-call rotations for an engineering team
→Feeding ownership data to an incident paging tool

Built with: Python
Tags: oncall; scheduling; incident-management; self-hosted; python; calendar

LinkedIn Oncall: questions and answers

What is LinkedIn Oncall used for?: LinkedIn Oncall is a free, BSD-licensed, self-hosted calendar tool for scheduling and managing on-call shifts, designed to feed dynamic ownership data to paging systems. It is a good fit for managing on-call rotations for an engineering team and feeding ownership data to an incident paging tool.
Is LinkedIn Oncall open source?: Yes. LinkedIn Oncall is open source under the BSD-2-Clause licence. Its source code is on GitHub at linkedin/oncall and is written mainly in Python.
Is LinkedIn Oncall free?: Yes. LinkedIn Oncall is open source, so the software itself is free to use.
Can I self-host LinkedIn Oncall?: Yes. LinkedIn Oncall can be self-hosted on your own server or infrastructure; there is no official hosted version.
What is LinkedIn Oncall an alternative to?: LinkedIn Oncall is an open-source alternative to incident.io, Rootly, PagerDuty and FireHydrant. Other open-source alternatives to incident.io include Keep, OneUptime and HolmesGPT.
Is LinkedIn Oncall actively maintained?: The most recent commit to LinkedIn Oncall was on 20 August 2025, and the latest release is v2.1.7, published on 12 March 2024. The project has 1.3k stars on GitHub.