brig v0.4.0 gives new sandboxes their own networks by default on Linux and on macOS.
Run coding agents for different projects on one machine, while keeping their dev servers and test APIs separate.
In this demo, one sandbox tries to reach a web server in the other. The connection times out.
We then start both with --network shared, and the same request works.
You can run unrelated tasks side by side and enable network sharing when agents need to work together.
#OpenSource #Sandboxing
brig v0.4.0 limits where your coding agent can send your code and credentials.
This release brings egress policy enforcement on Linux! If brig cannot enforce the policy, then the run is refused.
Allow the services you need for the job. Then brig enforces your network policy outside the sandbox, so the rules also apply to the scripts and dependencies the agent runs. In this demo, an example domain works. Requests to Github API and a direct connection to 1.1.1.1 are blocked, even from a root shell inside the sandbox.
#OpenSource #Sandboxing
In San Francisco this Friday for #sftechweek?
Join our CTO, Panagiotis Moustafellos and DevRel Artemis Leonardou, for a private roundtable on AI, security and production reliability.
October 9 · 8–11 PM PT · San Francisco
#SFTechWeek#SRE
Brig v0.3 is out https://t.co/IwVul3XQVQ
Headliner is Linux rootless support.
On Linux #Brig now sets up the whole runtime incl. the VMM & guest kernels.
MacOS already supported an end-to-end experience: upgrade with; brew upgrade --cask brig
We built Brig as part of @NOFireAI's work on controlled autonomy in production.
We’ve open-sourced the #sandbox so developers can use the same microVM isolation for coding agents on Mac and Linux.
All components Apache 2.0.
At @NOFireAI we are building #sandboxing w/ microvm, hardware-level, isolation guarantees. The controls live outside of the reach of the agent running in the guest, with JIT enforcement. Clear audit trail & realtime inspection of agents’ behavior from outside the boundary. (cont)
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
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..
🔥 AI-powered incident response, built like a real team
At NOFire AI, we’ve redefined incident management by integrating Agentic AI—working alongside SREs & On-Call Engineers just like a human team.
How it works:
✔️ Smart alert triage – Prioritizes real issues, reduces noise.
✔️ Root cause analysis – Connects observability data to real insights.
✔️ Impact assessment – Understands how incidents affect users & business.
✔️ Actionable recommendations – AI suggests fixes based on past incidents.
✔️ Continuous learning – Gets smarter with every resolution.
We turn chaos into control. 🔥⬇️
#AI #IncidentResponse #SRE #ReliabilityEngineering
🚨 Alerts flooding your @SlackHQ? You have 2 options: spend few hours to figure out relevant dashboards, metrics, logs... or just know what's wrong.
⚡️ @opentelemetry + @grafana + NOFire AI = Faster incident resolution.
📹 Watch how it works 👇
#Grafana#OpenTelemetry #Kubernetes #SRE #DevOps #AI
🎄 To all the fellow SREs and on-call engineers this holiday season: we see you.
The late nights, the pager alerts, the sacrifices—keeping systems reliable isn’t easy, especially when it means missing precious moments.
Stay strong. Your work matters more than ever. Wishing you a peaceful and resilient Christmas.
#SRE #OnCallLife #IncidentManagement #AI #Christmas
SREs, tired of drowning in alerts? 🚨
Discover how to cut through the chaos and make your alerts more effective.
https://t.co/ElkDqRLyfg
Alert fatigue isn't just frustrating - it's a major productivity killer. Reducing noise is essential for sharp, efficient incident response.
#SRE #AlertFatigue #SiteReliability
The one thing that has not changed despite sophisticated automations, AI, smart tools...it's human(s) in the loop during a production incident.
The human always involved in a production incident will be your SRE.
#AI#SRE#OnCall#IncidentResponse
📢The #ApacheFlink community is happy to announce the release of #Flink 1.16, which contains a number of exciting changes. Please checkout out the release announcement for details.
https://t.co/wBIRKXQXuD
Big thanks to the community for all the contributions! 👏👏👏