"Open source" gets thrown around loosely now. Here's what it means to us, specifically: You can read every line. Run it on your own hardware. Fork it if we make a decision you hate. Contribute a fix and see it ship. And never get an email that says "we've been acquired, your pricing is changing." Free is nice. Not being trapped is the real value.

An AI agent is only as good as what it can see. OpenSRE plugs into @datadoghq, @pagerduty, @sentry, @github , and whatever else you're already paying for, plus MCP servers for anything we haven't built yet. We're not replacing your stack. We're the thing that reads all of it so you don't have to.

The OpenSRE Discord just passed 2,000 members. 🌟 What started as a place to report bugs has turned into SREs comparing war stories, contributors pairing on issues, and people showing up to biweekly calls from a dozen time zones. If you're usually on call, come hang out. The #incidents channel alone is worth it. 🔨

Your incident data is the most sensitive thing you own. Logs, configs, architecture, what broke and why. Most AI SRE tools ask you to ship all of it to someone else's cloud. OpenSRE runs where you run. Your infra, your model provider, your keys. Nothing leaves unless you decide it does. Open source isn't just readable code. It's not having to trust anyone.

Turns out the best product feedback doesn't come from surveys. It comes from an SRE sharing their screen on a Thursday community call saying "this is where it lost me." Last call we covered: live investigation demos, a walkthrough of the benchmark results, and maintainers digging into where the loop still gets stuck. Thanks to everyone who showed up. Next one's Thursday 23rd, the invite's in the Discord: discord.com/invite/opensre ✉️

Unpopular opinion: the best AI infrastructure tools won't come from the big labs. They'll come from open source. 🛠️ Labs never see the weird failures, the vendor-specific ones, the ones that only happen at your company. A community does. The labs have the models. The community has the failures. The failures are the moat. 🏰

We recently ran a 7-day hackathon. 🛠️ → A pipeline rewrite shipped at 2:30am. → 10 PRs merged in a day. 23 total. → +36pts on the hardest Kubernetes failure category. +400 GitHub ⭐ in 7 days. This is what building in public looks like. See you at the next one! 🚀 github.com/Tracer-Cloud/open…

We benchmarked OpenSRE against 452 broken Kubernetes clusters. Same GPT-4o model. Same tools. Only difference: the investigation loop. 🔍 Hardest fault type in the benchmark: OpenSRE scored 56% vs GPT-4o at 20%. That's what thinking harder looks like. 🚀 github.com/Tracer-Cloud/open…

Big shoutout to Greptile, our newest sponsor 🦎 Less guesswork navigating a codebase, more time actually fixing things, that's the instinct behind their tool, and it's one we share. Proud to have them in our corner as we keep building OpenSRE fully in the open. → github.com/Tracer-Cloud/open… → greptile.com

big two weeks for opensre ↓ • GitHub Actions - investigate CI/CD failures directly from your pipeline • xAI Grok added as an LLM provider • 6 new integrations: Azure SQL, MongoDB Atlas, Snowflake, Supabase, OpenObserve, Trello • Hermes eval suite - measure RCA evidence quality, not vibes • CLI: session resume, cleaner commands, silent errors fixed github.com/Tracer-Cloud/open…