Gremlin Chaos Engineering
Build trust in complex systems with Chaos Engineering
Trusted by teams worldwide
Chaos Engineering makes your systems reliable. Gremlin makes it safe, easy, and secure.
Confidently recreate incidents and outages
- Test system reliability by thoughtfully injecting failure into services, hosts, containers, and serverless workloads.
- Use the experiments library to see how systems respond to a variety of common failure conditions.
- Start small and scale experiments once you're confident in system stability.
- Easily and automatically halt and roll-back attacks should issues arise.
Validate systems against any incident scenario
- Replicate real-world incidents by running multiple Chaos Engineering experiments in sequence.
- Create your own or use Gremlin's pre-configured library of recommended Scenarios to simulate real-world outages that can impact performance, uptime, and customer experience.
- Share scenarios across teams to create a stronger culture of reliability.
- Run scenarios on a schedule to keep your availability high and your incident count low.
Prepare and run effective GameDays
- Use GameDay Manager to reduce your internal prep and run time, ensuring a successful event.
- Automatically analyze and store results so you can review what success or failure looked like. Turn that data into action to improve your system.
- Integrate with Jira to ensure action items are captured and tracked with your team.
Superpowers for SRE teams
Meet uptime and availability SLOs
Identify hidden reliability risks
Validate and tune monitors
Mitigate dependency failure
Eliminate revenue impacting outages
Ensure reliable mitigations & launches
The Gremlin Advantage
Used by 100+ of the Fortune 2000, including 5 of the 7 biggest US banks
Hundreds of thousands of hosts safely and securely run Gremlin
Over one million chaos engineering experiments and reliability tests run
Stress your systems, any way you choose.
Generate load across CPU cores. Ensure your systems can withstand stressful conditions caused by high demand or heavy traffic.
Terminate a specific process or set of processes. Prepare for application crashes, Out Of Memory (OOM), and similar events.
Consume a specific amount of RAM. Validate resilience to memory leaks or resource-intensive applications.
Drop network traffic based on port, network interface, or hostname. Test your ability to failover during a complete network outage.
Create read/write pressure on I/O devices such as hard disks. Test the performance of your systems when connected to high-latency, low-throughput storage.
Inject a delay into outbound network traffic. Validate your system's responsiveness under slow network conditions.
Consume a specific amount of space on a storage device. Ensure your systems keep running even with disk-hungry applications (such as log files and exhausted storage volumes).
Drop or corrupt a percentage of outbound network traffic. Ensure you can successfully send and receive data despite poor network conditions.
Shutdown (and optionally reboot) the host operating system. Build resilience to host failures.
Block access to DNS servers. Prepare for DNS outages, test fallback DNS servers, and validate DNS resolver configurations.
Change the system time. Prepare for Daylight Savings Time, clock drift between systems, expiring SSL/TLS certificates, and other time-sensitive events.
Retrieve the certificate chain and validate that no certificates expire in the next 30 days.