Keep
Open-source · self-hostable · replaces 1 SaaS tool on os-alt
keephq/keep · alive · ★ 11.8k · last commit today · 559 open issues
License: MIT — Core is MIT; the `ee/` directory ships under a separate Keep Enterprise license. The non-EE surface (alert ingestion, providers, workflows, UI) is what you want for self-hosted on-call replacement, and that part is OSI-MIT.
Good fit for Teams that want alert dedup, correlation, and workflow automation alongside on-call paging — i.e. the noisy-alerts problem and the on-call problem solved by the same tool. Currently the most actively maintained option in this category.
Weak at Pure on-call scheduling UI is thinner than PagerDuty's — Keep leads with alert orchestration, not rotation calendars. If all you need is 'who's on-call this week', the workflow surface is more than you'll use.
In a terminal? npx -y github:SolvoHQ/os-alt-cli pagerduty prints
the PagerDuty comparison table including Keep.
how the CLI works →
Replaces these SaaS
- PagerDuty · On-call rotation / incident response / paging
Keep is an alert orchestration / AIOps platform with first-class on-call workflows, not a 1-1 PagerDuty clone. Migration path: (1) connect PagerDuty as a *source* provider in Keep to mirror existing alerts and incidents while you cut over; (2) wire your alert producers (Prometheus, Grafana, Sentry, Datadog — all have first-class providers under `keep/providers/`) to Keep's webhook endpoints; (3) configure the Twilio provider for SMS/voice paging; (4) build workflows for dedup/correlation/escalation in Keep's workflow YAML. PagerDuty schedules don't import directly — recreate them as Keep workflows or pair with a calendar source.
README badges for the SaaS this replaces
Maintainers and forks: drop a badge in your README to link readers from the SaaS-comparison page back to your repo.
