nightingale

ccfos/nightingale

Open-source, self-hosted alerting for metrics, logs, and databases. Includes a built-in AI agent and MCP server.

Ship status

Still shipping

Pushed in the last 30 days.

Last push
Oct 22, 2026
today
Ship score
89/100
How it is calculated →
Stars, last 7 weeks
Stars, weekly: 13,280 → 13,370 (Sep 8 – Oct 20, 2026)
+68 stars in the 28 days to 2026-10-20

Shipping: pushed in the last 30 days · slowed: quiet for 31–120 days · silent: no push in over 120 days.

Repo facts

What GitHub reports.

Stars
13.4K
Forks
1.8K
Open issues
240
Watchers
170
Primary language
Go
Created
Mar 3, 2020
Owner
ccfos · Organization

Open issues are the issues and pull requests GitHub reports as open; watchers are the accounts subscribed to the repository. OSI-approved license — GitHub’s own license field, not legal advice. 100 startups in the directory ship primarily in Go.

Topics

#alerting#alertmanager#clickhouse#golang#logs#loki#mcp-server#metrics#monitoring#nightingale#observability#on-call#prometheus#self-hosted#sre#sre-agent#time-series#tsdb#victoriametrics

How it got here

What the classifier decided, and when.

Classified as an open-source startup by Jev, TypeSafe’s classifier, on Sep 22, 2026 — os_startup 72%, self-hostable 76%, hosted offering 46%. The classifier reads only the repository’s name, description and homepage; it can be wrong, and a probability under 0.5 puts a listing in the review queue rather than out of the directory.

Listed since the 2025-09 crawl. Answered by jev-1.13.0. How the classification works →

Embed your status

Put this badge on your README.

OSSEAN ship status: shipping — last push 2026-10-22This is the badge for ccfos/nightingale, as served from the URL below.
[![OSSEAN: shipping](https://ossean.com/badge/ccfos/nightingale.svg)](https://ossean.com/ccfos/nightingale)

Updates daily, from the last push GitHub saw.

Honest caveat: GitHub proxies README images through Camo and rewrites the anchor with rel=“nofollow”, so a README embed sends you referral traffic and brand, not link equity. The link is dofollow wherever you control the markup — your docs, your landing page, your blog. The snippet uses your frozen OSSEAN slug, so it survives a repo rename.