Status Page Aggregator for SRE Teams

A production-ready status monitoring dashboard that SRE teams can fork and customize for their specific vendor dependencies.

The Problem: Your production system depends on 20+ external services (AWS, Stripe, OpenAI, Datadog, etc.). During incidents, engineers waste critical time checking multiple status pages to determine if issues are vendor-related.

The Solution: Deploy your own unified status dashboard that automatically monitors all your critical vendor dependencies. Get real-time updates and instant notifications when high-priority services experience issues.

• 🔄 Automated Monitoring: Fetches status from 50+ services via RSS/Atom feeds and APIs
• ⚡ Real-time Updates: Supabase Edge Functions update status every minute
• 📧 Smart Notifications: Email alerts only for high-priority service changes
• 🎨 Customizable: Easy to add/remove services based on your stack
• 📱 Mobile-Ready: Check status during on-call incidents

┌─────────────────┐    ┌──────────────────┐    ┌─────────────────┐
│   Next.js App   │◄───│   Supabase DB    │◄───│  Edge Function  │
│  (Frontend)     │    │ (service_status) │    │  (Status Sync)  │
└─────────────────┘    └──────────────────┘    └─────────────────┘
                                                         ▲
                                                         │
                                                ┌────────▼─────────┐
                                                │ External APIs &  │
                                                │   RSS/Atom       │
                                                └──────────────────┘

git clone https://github.com/YOUR_USERNAME/status-page-aggregator
cd status-page-aggregator
npm install

See docs/API_AUTHENTICATION.md for API keys. Create .env.local with:

# Supabase Configuration
NEXT_PUBLIC_SUPABASE_URL=https://your-project.supabase.co
NEXT_PUBLIC_SUPABASE_ANON_KEY=your-anon-key

# POST /api/services/status — at least one key required
EXTERNAL_API_KEY=your-cloud-saas-key
ON_PREM_API_KEY=your-on-prem-only-key   # optional; use for drdroid-on-prem installs

NEXT_PUBLIC_HYPERLOOK_API_KEY=your-hyperlook-key

# Email Configuration
EMAIL_HOST=smtp.gmail.com
EMAIL_PORT=587
EMAIL_USER=your-email@gmail.com
EMAIL_PASS=your-app-password
SLACK_EMAIL=sre-team@yourcompany.com

npm run build
vercel --prod  # or your preferred hosting

This project is designed for forking and customization. Consider contributing back:

• New service integrations that benefit the SRE community
• Bug fixes for parsing edge cases
• Performance improvements for large-scale deployments
• Documentation improvements for additional deployment platforms

• 🐛 Report Issues
• 💬 Discussions

MIT License - Fork, customize, and deploy for your team!

Built with ❤️ by DrDroid team for SRE teams worldwide