bandingkan
Keep vs OneUptime
Fakta yang sama untuk keduanya, dibaca dari GitHub setiap malam, dan hubungan keduanya yang ditinjau oleh manusia.
| Fakta | Keep | OneUptime |
|---|---|---|
| Bahasa | Python | TypeScript |
| Lisensi | Other | Other |
| Bintang | 12k | 7.7k |
| Terbaru | v0.54.3 | 14.0.14 |
| Push terakhir | 2026-09-28 | 2026-10-06 |
| Frekuensi rilis | sekitar 18 hari antar rilis | sekitar 1 hari antar rilis |
| Kontributor aktif | 18 penulis commit di branch default dalam 90 hari terakhir | 4+ penulis commit di branch default dalam 90 hari terakhir |
| Peringatan | tidak ada | tidak ada |
Hubungan keduanya
Keduanya menggantikan PagerDuty. Alternatif PagerDuty →
SebagianKeepCollects, deduplicates and correlates alerts into incidents and runs workflows on them, but has no on-call schedules or escalation policies of its own.
Pengganti penuhOneUptimeOn-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
✓ bertanda tangan Rilis terbaru, v0.54.3, memiliki tanda tangan yang diverifikasi GitHub.
Memuat laporan keamanan
OneUptime
tanpa tanda tangan Rilis terbaru, 14.0.14, tidak memiliki tanda tangan yang dapat diverifikasi GitHub.
Memuat laporan keamanan