# 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.

Repository: https://github.com/linkedin/oncall
Canonical: https://ross.abutalabs.com/products/linkedin-oncall
Homepage: http://oncall.tools
Language: Python
License: BSD-2-Clause
License Family: permissive
Topics: oncall, calendar, scheduling
Last push: 2025-08-20T19:09:59+00:00

## Health v2 (maintenance only)
Score: 39/100 (v2, computed 2026-09-03T02:20:16.233290+00:00)
- activity 37, release rhythm 8, longevity 100
- inputs: {"age_days": 3410, "days_push": 378, "days_rel": null, "gap_med": null, "n_releases_24m": 0}
- flags: none
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 1258, forks 244 (observed 2026-08-28T04:04:09.476885+00:00)

## What it is
Oncall is a self-hosted calendar application for scheduling and managing on-call shifts, built by LinkedIn. It serves as a source of truth for dynamic ownership and contact information and integrates with paging systems like Iris via a REST API.

## Use cases
- schedule on-call shifts for my team
- manage who is on call each week
- swap on-call shifts with teammates
- feed dynamic ownership info to a paging system
- set up follow-the-sun on-call rotations across time zones
- get reminders when my on-call shift starts

## When to choose
- you need a self-hosted on-call calendar with a REST API
- you use or plan to use Iris or another escalation system needing ownership data
- you need complex scheduling templates, round-robin scheduling, or follow-the-sun shifts

## When to avoid
- you want a fully managed SaaS on-call product like PagerDuty or Opsgenie
- you need built-in alerting/escalation without a separate paging system
- you are not prepared to run your own MySQL-backed web service

## Facets
- artifact type: application
- maturity: active
- function: scheduling, web-framework, api-framework, workflow-automation
- domain: self-hosted, apis, web-development
- platform: python, self-hosted, cross-platform
- tags: on-call, incident-management, paging, calendar, escalation, rest-api, shift-scheduling, notification, devops, automation, web-server, docker, linux

## Member repositories
- linkedin/oncall (main) score 39

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:04:09.476885+00:00.
- Health v2: computed from the inputs above; adoption is never an input.
- Inferred fields (summary, facets, guidance): AI-extracted, prompt v1, taxonomy v1, on 2026-08-30T05:05:35.772308+00:00, confidence not recorded.
  - readme: https://github.com/linkedin/oncall (fetched 2026-08-28T04:04:09.476885+00:00, sha 37483ebe9756)
  - homepage: http://oncall.tools (fetched 2026-08-29T12:17:34.774017+00:00, sha 991cbfbc8c79)
  - site_page: https://oncall.tools/docs (fetched 2026-08-29T12:17:34.782872+00:00, sha a5b2bc558678)
  - registry_pypi: https://pypi.org/pypi/oncall/json (fetched 2026-08-29T12:17:34.785189+00:00, sha e8ceb157f598)
- Data as of 2026-08-30T08:39:29.467469+00:00.