Gremlin

We’re excited to announce that Failure Flags is officially out of Beta! 🚀 Since its initial release, customers have used Failure Flags to run thousands of tests for applications running on serverless, container, and service meshes. And with all the customer-led improvements and optimizations over the last year, we’re pleased to make Failure Flags Generally Available for all customers. Head to the link in the comments  to read more about what’s available in Failure Flags. ⬇️

Reliability testing is ongoing, and tracking that work can be difficult in large organizations. According to our own product metrics, teams run an average of 200 to 500 tests each day! With so much happening, it’s hard to keep track of everything going on—unless you use Gremlin. In this week's Office Hours session, you’ll discover how to track your reliability work using Gremlin’s “Now Running,” “What Ran,” and “What’s Scheduled” screens, what data each screen provides, how to access them, and how to use them to manage ongoing testing activities. Join us on Thursday, March 13th at 11 AM PST to learn more: https://lnkd.in/gayZY5ec

❌ A failed reliability test isn’t a failure; it’s an opportunity to improve. It highlights potential weak spots in your system-before they impact users. Find out how to analyze and address failed tests to make your systems more resilient at the link in the comments.

I’m proud to share that my team at Gremlin recently released Gremlin Private Edition—a fully isolated version of our platform that runs entirely within your private network. It delivers all the capabilities of our SaaS solution, but with the added control over deployment, access, and data storage that many of our customers have been asking for. This release is a testament to the hard work and dedication of our team, who’ve been focused on building tools that make software resilience not just a goal, but a reality. With Private Edition, we’re helping customers strengthen their systems against failure, all while meeting their unique security and operational needs. #Reliability #ChaosEngineering #SoftwareEngineering #Teamwork #Gremlin

The complexity of modern systems has grown exponentially. With microservices, distributed architectures, and multi-cloud strategies, even small issues can ripple into large-scale outages. The challenge isn’t just managing complexity—it’s building systems that thrive in it. Chaos Engineering, and building a culture of reliability within impacted teams, is crucial here. One of the most valuable insights we’ve seen? Understanding the “unknown unknowns” in your infrastructure. These hidden risks are often the most dangerous, and often don’t see the light of day until a major incident occurs. The question isn’t whether your systems will face stress—it’s whether they’ll survive it. How are you approaching complexity in your reliability strategy this year?

We're thankful to have built an amazing team here at Gremlin- here's to many more anniversaries (and even more Gremlin stickers to add to the collection!) 💜

“Like a lot of things in software engineering, just because we intend things to work in a certain way doesn’t mean they will. Fortunately, we have a useful tool to evaluate the difference between “believing” you’re resilient and ‘knowing’ you’re resilient: we can test it.” Head to the comments to get the best practices for testing zone redundancy straight from our Principal Software Engineer, Samuel Rossoff

For years, disaster recovery was the gold standard for dealing with outages—wait for something to break, then fix it. But in a world where downtime costs thousands of dollars per minute, this reactive approach alone is no longer sustainable. Forward-thinking organizations are moving towards a preventive model, proactively testing their systems before failure occurs. Chaos Engineering plays a pivotal role here, helping teams identify weaknesses and simulate real-world scenarios under controlled conditions. This mindset shift—from recovery to prevention—doesn’t just save money; it builds confidence. Teams know their systems can handle stress, customers experience fewer disruptions, and businesses maintain their competitive edge. And that doesn’t mean it’s time  to abandon disaster recovery plans- instead, test them well before they’re needed so you’re prepared in a worst-case scenario. What steps are you taking to move towards prevention in your reliability strategy?