Inspiration

Tired of every outage becoming our fault. Support burns 2hrs checking vendor status that should be automatic.

What it does

Live perception layer: detects external outages in 10s, gives structured proof + auto-drafts customer reply.

How we built it

Haiku resolves vendor → 6 parallel SerpApi queries (Google+Bing) → Sonnet synthesizes proof → JSONL audit log. FastAPI + asyncio.

Challenges we ran into

Stale status pages, single-index bias, forcing Claude to strict JSON schema, and building TTL caches + mock mode to save quota.

Accomplishments that we're proud of

Cross-engine corroboration (Google+Bing), structured proof object, 6 queries in 6s, Zendesk/PagerDuty-ready drafts.

What we learned

Status pages lag. Crowd signal is truth. Proof > summary. Cross-engine agreement matters more than more queries on one index.

What's next for DevAlibi

Background polling + webhooks, Google Trends early-warning, MCP server, Slack/PagerDuty/Zendesk bots, per-customer tone & polling.

Built With

Share this project:

Updates

posted an update —

Live demo is up!

DevAlibi now runs at devalibi.onrender.com — real Claude synthesis, not just local. Click Stripe/AWS/OpenAI to see a live proof object: confidence score, cross-engine signal agreement, draft reply, PagerDuty title.

Log in or sign up for Devpost to join the conversation.

Submission history