NOFire AI @NOFireAI

The Context and Control Model for Production nofire.ai Joined June 2024

Tweets

129
Followers

71
Following

480
Likes

109

NOFire AI @NOFireAI

a week ago

Download the report here: nofire.ai/resources/ai-s…

0 0 2 19 0

View Details

The benchmark result that matters is not the headline number. It is what happens when you remove the context layer. Same #LLM. Same prompts. Same signals. With the Production Context Graph: 89%. Without it: 70%. That 19-point gap is the entire argument for building a live causal model of production before you build anything else. Most teams skip straight to the agent. The agent hallucinates, chases symptoms, and gets blamed for being unreliable. The problem is never the model. It is that the model has no idea what your production actually looks like. #AISRE #Kubernetes #ContextGraph #GenAI

1 2 3 59 0

View Details

V4bel @v4bel

2 weeks ago

Anyway, interesting. In practice, what matters for weaponization is controlling the GIC driver inside the guest

0 2 9 874 1

View Details

V4bel @v4bel

2 weeks ago

🧐 nofire.ai/blog/ITS-arm64…

1 4 20 2K 3

View Details

Panagiotis Moustafellos @pmoust

2 weeks ago

At @NOFireAI we 'design for breach'. The AI agent in production is untrusted by default. nofire.ai/blog/design-fo…

0 6 5 176 2

View Details

Panagiotis Moustafellos @pmoust

4 weeks ago

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 18 1K 0

View Details

NOFire AI @NOFireAI

4 weeks ago

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

0 1 5 140 0

View Details

NOFire AI @NOFireAI

2 months ago

5/5Try it now: Works with your production. Multi-account support for teams with multiple environments. From scattered context to full production understanding.

0 0 0 43 0

View Details

NOFire AI @NOFireAI

2 months ago

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 0 0 62 0

View Details

NOFire AI @NOFireAI

2 months ago

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 135 0

View Details

Spiros Economakis @spirosoik

2 months ago

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 103 0

View Details

NOFire AI @NOFireAI

7 months ago

"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-l…

0 0 0 67 0

View Details

NOFire AI @NOFireAI

8 months ago

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

0 1 2 254 0

View Details

NOFire AI @NOFireAI

9 months ago

nofire.ai/blog/shift-rel… #ShiftLeft #CausalAI #SRE #ReliabilityEngineering #CloudNative

0 0 1 36 0

View Details

NOFire AI @NOFireAI

9 months ago

5/ Reliability becomes proactive, not reactive. Teams move from “what broke?” → “what might break and why?”

1 0 0 37 0

View Details

NOFire AI @NOFireAI

9 months ago

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 👇