FaultMesh vs Toxiproxy

FaultMesh is a Kubernetes-native platform for testing system resilience through controlled failures, anomaly detection and automatic remediation. It injects latency, packet loss, pod kills, CPU stress and memory stress using Chaos Mesh CRDs. Real-time metric analysis can surface regressions, while rules and actions can heal systems automatically. The platform scores services across six dimensions and assigns L1–L5 maturity levels. It tracks SLO error budgets and supports multi-step chaos game days with checks between steps. Safety controls include blast-radius limits, dry runs, an error-budget gate, a background monitor and an instant kill switch. Teams can use managed SaaS or deploy a Kubernetes Operator in their own cluster, where data stays inside their perimeter. Security features include JWT and API-key authentication, role-based Admin, Operator and Viewer access, encryption in transit and an immutable audit trail. The maker describes controls as SOC 2-aligned, with formal certification on the roadmap, and data handling as GDPR-aligned. Starter is free for up to three services; Growth costs $49 a month billed per host, and a 14-day trial is available.

Toxiproxy is a free, open-source TCP proxy for testing how software responds to network and system problems in development, testing, and CI. Applications route test connections through it, then users change connection behavior through an HTTP API or command-line interface. Built-in toxics can add latency or jitter, restrict bandwidth, delay socket closure, time out or reset connections, slice TCP data, limit transmitted data, or drop packets. Settings support deterministic connection changes as well as randomized chaos. The API manages proxies and toxics, resets proxies, and returns version information and Prometheus-compatible metrics. It listens on port 8474; configuring a proxy with listen port 0 assigns an ephemeral port. Client libraries are listed for Ruby, Go, Python, .NET, PHP, Node.js, Java, Haskell, Rust, and Elixir. Installation options include Linux packages and binaries, Homebrew and MacPorts, a Windows download, a container image, and building from source with Go. The project identifies its license as MIT. Its HTTP API is unauthenticated by default, though bearer-token authentication is supported.