StackGen's Autonomous Operations Factory runs Aiden- governed AI agents for SRE, DevOps & InfraOps on shared context with guardrails built in.
San Francisco Bay Area
Joined December 2023
- Tweets218
- Following11
- Followers78
- Likes33
Pinned Tweet
1/@shipyardbuild is joining StackGen. Shipyard gives every pull request a full-stack ephemeral environment and removes it on merge. Why we're excited ๐งต
Google reported 17.5% more change lists per engineer per month, while Microsoft saw 24% more merged pull requests per engineer per day.
That's more code making its way through development. But how quickly can teams get it into production?
Infrastructure still needs to be provisioned, deployments need to be managed, and production incidents still need attention. Each step takes time, especially with manual handoffs between teams.
Our latest blog explains where these delays occur and how teams can keep pace with faster development cycles.
Read the full article: stackgen.com/blog/ai-coding-โฆ
How much of a production incident can an AI agent realistically handle on its own?
An agent needs operational context, an understanding of service dependencies, and clear boundaries around the actions it can take. That becomes more complicated when it has to work across multiple tools and infrastructure environments.
Our Field CTO, @sd_architect, will discuss these architectural challenges in his session, โThe 4-Body Problem of SRE: Building an Agentic OS for Autonomous Operations,โ at All Day AI.
October 22 | 12:30 PM ET
Register: alldayai.com/schedule
A developer needs a new environment. The request sounds simple, but the platform team still has to check the infrastructure modules, validate policies, and approve the deployment.
Now imagine handling those requests across 1,000+ applications and thousands of deployments every month.
With Aiden for InfraOps, developers can request infrastructure through tools like Claude Code, Copilot, Kiro, or Backstage. Aiden uses approved modules, checks policies, and prepares the plan for human approval.
After deployment, it also detects configuration drift when cloud resources no longer match the code.
See how it works: stackgen.com/schedule-demo
An AI agent says it's 94% confident about the root cause of your production incident, but you'd probably want to see the evidence before approving a fix.
In this example, Aiden for SRE traces a spike in payment API errors to connection pool exhaustion after a deployment. The error rate jumped from 0.4% to 11.8%, traces show slow connection acquisition, and the logs contain 2,104 connection timeouts.
How close are we to an incident that can resolve itself without an engineer stepping in? It's an interesting idea until you consider everything that happens during a real production incident. An agent might identify the cause and recommend a fix, but giving it permission to change production systems is a much bigger decision.
That's the topic of our panel at AISRE Meetup Hyderabad today: "The Self-Driving Incident: What Full Autonomy in SRE Actually Looks Like."
๐ค Made with AI
How quickly can your monitoring detect a production issue? Meenu shares Freshworks' approach to using AI-powered observability to identify incidents sooner and bring down MTTD.
An incident can start affecting users long before anyone gets an alert. And by the time the on-call engineer knows there's a problem, the clock has already been ticking.
Meenu Sowjanya Chandrasekaran, SRE at Freshworks, is presenting "O11y: Our AI-Powered MTTD Framework" at AI SRE Meetup Hyderabad!
#AISRENext #AISRE
There's only so much you can explain with slides.
Sravanthi Naga from Pegasystems is running a live demo at the AISRE Meetup Hyderabad!
#AISRENext #AISRE
Today, AI agents handle more of the on-call workload, but someone still has to decide when to trust their recommendations, when to escalate, and who answers for the outcome when a fix goes wrong.
At AISRE Meetup Hyderabad today, Sravanthi Naga, Senior Engineering Manager at Pegasystems, is sharing her insights on "Who Owns the Incident? Accountability When AI Joins the On-Call."
#AISRENext #AISRE
For engineering leaders responsible for systems that thousands of businesses rely on, deciding how much control to give an AI agent has real consequences.
Surya Srinivas, SVP of Engineering at greytHR, is delivering his keynote, "The Autonomy Budget: How Much Freedom Can Production Afford?", at AI SRE Meetup Hyderabad today!
#AISRENext #AISRE
Keeping systems reliable at enterprise scale comes with a lot of difficult decisions, especially as teams start bringing AI into production operations.
We're at AISRE Meetup Hyderabad today, where Dr. Nagarjun Malladi, VP and Group Delivery Head at Tech Mahindra, is sharing his perspective on the challenges of maintaining reliability across large organisations and how agentic AI, autonomous infrastructure, and SRE practices can help.
Sharing a few moments from his session!
#AISRENext #AISRE
The first few minutes of an incident can disappear pretty quickly while you check alerts, logs, dashboards, and recent changes.
Aiden for SRE pulls that context from the telemetry already in your environment and gives the on-call engineer an RCA with the evidence behind it.
Try the Community Edition for free: app.stackgen.com/app/sre/
#AISRE
A runbook doesnโt always keep pace with the service it was written for. InMobiโs Sumedh Masulkar talked about why keeping documentation current is such a hard problem, even for experienced engineering teams, during our panel at #AISRE Next Bengaluru.
Their approach brings runbooks into the same GitHub workflow as the code. When a system change comes through a pull request, an agent checks whether the runbook needs to change too.
We are hosting the first ๐๐ ๐ฆ๐ฅ๐ ๐ ๐ฒ๐ฒ๐๐๐ฝ ๐จ๐ฆ, ๐๐๐ฏ๐ฒ๐๐ผ๐ป ๐ฒ๐ฑ๐ถ๐๐ถ๐ผ๐ป, on the sidelines of ๐๐๐ฏ๐ฒ๐๐ผ๐ป + ๐๐น๐ผ๐๐ฑ๐ก๐ฎ๐๐ถ๐๐ฒ๐๐ผ๐ป ๐ก๐ผ๐ฟ๐๐ต ๐๐บ๐ฒ๐ฟ๐ถ๐ฐ๐ฎ.
๐ Gracieโs, Salt Lake City
๐ Monday, November 9 | 5:30 โ 8:00 PM
๐ป Drinks and starters are on us
๐ช๐ต๐ผ ๐ถ๐'๐ ๐ณ๐ผ๐ฟ: SREs, Platform Engineers, and DevOps folks in town for the co-located events on Nov 9โ10, or anyone checking in early on the 9th. Grab your badge, then come unwind with people who get paged at 3 AM too.
๐ค ๐๐ฎ๐น๐น ๐ณ๐ผ๐ฟ ๐ฃ๐ฟ๐ผ๐ฝ๐ผ๐๐ฎ๐น๐ ๐ถ๐ ๐ผ๐ฝ๐ฒ๐ป
Have you run AI in your incident workflow, whether it was a win, a failure, or something in between? We're looking for short, practitioner-led lightning talks. No vendor pitches, just real stories from production.
DM for speaker opportunities.
Register to attend (only 40 spots): luma.com/bdp85cso
Interested in partnering? DM
See you in SaltLakeCity
@KubeConParties @CloudNativeFdn #KubeconNA
StackGen retweeted
Shipyard is now part of StackGen.
The product, your contracts and your support contacts stay the same. We're now Shipyard by StackGen, with a larger engineering organization behind us, and new opportunities to apply our technology.
Read more: stackgen.com/blog/shipyard-jโฆ
