PulseBoard Update: From Uptime Monitoring to AI Incident Investigation 🚀

Over the past few weeks, I've been focused on one question:

Monitoring tells you something broke.
But how do you figure out why?

That's where PulseBoard is heading.

What's new

🔗 GitHub Integration
Correlate incidents with recent commits and deployment activity.

🧠 Evidence-based Vigil AI
Instead of generating generic AI responses, Vigil now investigates incidents using:

• Monitoring failures

• Historical incident patterns

• GitHub commit summaries

• Deployment timing

• Infrastructure context

⚠️ No hallucinated root causes
If there isn't enough evidence, Vigil simply says:

"Cause unknown from available data."

I'd rather have honest uncertainty than confident misinformation during production incidents.

⚡ AI Provider Queue
Behind the scenes, Vigil now uses a custom priority queue with automatic provider failover, retries, circuit breakers, and rate limiting across Groq, Mistral, and Cerebras.

📦 Commit Intelligence
Commit diffs are summarized once, cached permanently, and reused across future investigations to reduce latency and AI costs.

The long-term goal isn't to build another monitoring tool.

It's to build an AI reliability engineer that helps answer:

Why did this happen?

What evidence supports that conclusion?

What should we do next?

I'd love feedback from the Product Hunt community.