Buddyflare

Cloudflare's built-in Worker logs are useful for recent debugging, but small teams still need alerting, longer history, and one place to inspect production signals across their apps.

Traditional observability platforms can introduce another vendor, another server, and a bill that grows with data volume. I wanted the useful parts of that stack to live in the same Cloudflare account as the applications it watches.

I built Buddyflare as an open-source, serverless observability stack on Cloudflare Workers, Durable Objects, D1, R2, and Queues. Logs stream to the dashboard in realtime and archive into the owner's own infrastructure.

The product stays deliberately focused: searchable logs, practical alert channels, visible usage costs, and an MCP server that lets coding agents inspect production context without putting another hosted vendor in the middle.

• Realtime live tail with searchable log history stored in the user's Cloudflare account.
• Alert delivery to Slack, Discord, Telegram, email, webhooks, PagerDuty, and Opsgenie.
• OpenTelemetry, Loki JSON, Vercel drain, and native JSON ingestion paths.
• A built-in MCP server for scoped, agent-readable production logs.

• Turns the missing alerting and longer-term memory around Workers logs into a deployable product.
• Keeps ownership, infrastructure, and metered usage inside the user's Cloudflare account.
• Closed beta is planned for the end of September 2026.