compare
Keep vs OneUptime
The same facts for both, read from GitHub every night, and the relation a person reviewed.
| Fact | Keep | OneUptime |
|---|---|---|
| Language | Python | TypeScript |
| Licence | Other | Other |
| Stars | 12k | 7.7k |
| Latest | v0.54.3 | 14.0.14 |
| Last push | 2026-09-28 | 2026-10-06 |
| Release cadence | about 18 days between releases | about 1 day between releases |
| Active contributors | 18 commit authors on the default branch in the last 90 days | 4+ commit authors on the default branch in the last 90 days |
| Flags | none | none |
How they relate
Both replace PagerDuty. Alternatives to PagerDuty →
PartialKeepCollects, deduplicates and correlates alerts into incidents and runs workflows on them, but has no on-call schedules or escalation policies of its own.
Full replacementOneUptimeOn-call policies with escalation rules and incidents, fed by its own monitors or by incoming webhooks.
Keep
OneUptime
- 14.0.142026-10-04fix(cli): honor partial env credentials with active context
- 14.0.132026-10-03Add a Code section to the Products menu and fold Code Repositories into Tasks
- 14.0.122026-10-02fix(team-compliance): keep the rule filter across every member segment
- 14.0.112026-10-01fix(teams): create incident / create maintenance answer once, with a form Teams accepts (#4111)
- 14.0.102026-09-30Team compliance: severity- and channel-aware rules (Call/Push for critical incidents & alerts) and a rebuilt Compliance…
Keep
✓ signed The latest release, v0.54.3, carries a signature GitHub verified.
Loading the security report
OneUptime
unsigned The latest release, 14.0.14, carries no signature GitHub could verify.
Loading the security report