The Context and Control Model for Production

Joined June 2024
33 Photos and videos
NOFire AI retweeted
Jun 13
Anyway, interesting. In practice, what matters for weaponization is controlling the GIC driver inside the guest
2
9
646
NOFire AI retweeted
At @NOFireAI we 'design for breach'. The AI agent in production is untrusted by default. nofire.ai/blog/design-for-br

6
5
79
NOFire AI retweeted
Nine years at @elastic , shipping the #observability products other teams got paged on. Watched the same pattern every time: AI tools arrive, talk big, then ask the on-call engineer to retrieve more context. Today we announce what we built instead..
1
9
16
1,207
We talked to a lot of engineers about production incidents. And today we are launching the first Context and Control Model for Production and announced our $2.5M seed from @marathon_vc , with participation from an exceptional group of angel investors. #ContextAndControl #AISRE #ProductionAI
1
5
134
1/5 We just shipped NOFire CLI. From investigation to action. In the terminal. No browser required. Here's why this matters đŸ§” #AISRE #SRE #ReliabilityEngineering #CloudNative
1
1
3
131
4/5Every investigation is persistent. Start a thread in the terminal during an incident at 3am. Pick it up in the web UI the next morning. Context doesn't die when you close the tab.
1
60
5/5Try it now: Works with your production. Multi-account support for teams with multiple environments. From scattered context to full production understanding.
41
NOFire AI retweeted
Remove the human, ship faster, no approval needed. Then the CISO walks in and the room goes quiet. @Gartner_inc predicts 40% of agentic AI projects will be canceled by end of 2027. #AISRE #Kubernetes #ReliabilityEngineering #SRE
1
1
3
100
18 Nov 2025
"For a decade, we’ve rewarded the heroes who fix things fast. AI will keep accelerating development; that’s inevitable. The answer isn’t to slow down. It’s to think faster than we ship." by our CTO, Chris Overton linkedin.com/pulse/how-we-lo

65
20 Oct 2025
Everyone’s waiting on AWS to fix us-east-1. Stay calm, hydrate, and may your alerts go quiet soon. It's always DNS. #SRE #AWS #OnCall #Reliability #DynamoDB #DNS
1
2
252
9 Oct 2025
1/ Reliability doesn’t live in process — it lives in understanding. In knowing what changed, when, and how it affects the system. Full blog & story in the thread 👇
1
1
2
74
9 Oct 2025
5/ Reliability becomes proactive, not reactive. Teams move from “what broke?” → “what might break and why?”
1
35
9 Oct 2025
2/ Most orgs treat reliability as a production problem. By the time you’re firefighting, the damage is already done.
17