OpenSRE just hit 5,000 stars on GitHub! ⭐
What started as an idea is now a community of thousands building, contributing, and shipping together.
Thank you all! Lots more to come. 🚀
https://t.co/KPlG9UMFes
@sahildarz Exactly that, the weird ones are always where the learning is. Nobody writes a postmortem about the failure that behaved exactly like the docs said it would.
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. 🏰
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! 🚀
https://t.co/zP0GFlntlQ
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! 🚀
https://t.co/zP0GFlntlQ
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. 🚀
https://t.co/zP0GFlntlQ
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. 🚀
https://t.co/zP0GFlntlQ
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.
→ https://t.co/zP0GFlntlQ
→ https://t.co/Pfb8AtFtjO
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.
→ https://t.co/zP0GFlntlQ
→ https://t.co/Pfb8AtFtjO
OpenSRE just hit 5,000 stars on GitHub! ⭐
What started as an idea is now a community of thousands building, contributing, and shipping together.
Thank you all! Lots more to come. 🚀
https://t.co/KPlG9UMFes
OpenSRE just hit 5,000 stars on GitHub! ⭐
What started as an idea is now a community of thousands building, contributing, and shipping together.
Thank you all! Lots more to come. 🚀
https://t.co/KPlG9UMFes
@GG_Observatory Exactly why we’re building OpenSRE.
The goal isn’t just smarter agents — it’s traceable ones.
Every decision, every action, every outcome… tied together so debugging in prod actually works.
most of the time, it’s not lack of data —
it’s lack of clarity
getting to the root cause faster is what we’re focused on at OpenSRE
https://t.co/KPlG9UNd40
LLMs write “perfect” code in seconds.
Engineers still have to debug the 3AM production outages.
AI automated the easy part.
We still own the fires 🔥.
We’re building AI agents that actually matter: autonomous incident response.
OpenSRE → https://t.co/RgAjCk7hQb