Panic Design: A zero-intrusion AIOps edge gateway that injects deterministic network degradation globally
Are you a frontline SRE or backend developer exhausted by traditional Chaos Engineering? Endless YAML configurations, the necessity of hardcoding Agent SDKs into your business logic, and the "black box" nature of network states post-injection... These pain points make fault simulation an incredibly burdensome task.
Today, I'm thrilled to share my opensource project—Panic Design. This is a purely edge-native, AI-driven "zero-intrusion" chaos engineering platform. With a single natural language prompt, an immersive console, and a transparent proxy, we are fundamentally redefining how you approach fault injection.
🧠 The Magic Moment: Intent-Driven AIOps
"Simulate trans-Pacific cable congestion."
Using traditional tools, you'd likely need to configure dozens of parameters spanning packet loss rates, latency distributions, and routing rules. In Panic Design, you simply type this plain English sentence into the console. Powered by the logical deduction capabilities of the underlying Llama 4 Scout 17B (MoE) model, our AI Copilot automatically:
- Deduces the physical routing trajectory and triggers logical validations.
- Auto-fills deterministic edge chaos parameters.
- Predicts and measures the negative impact of these simulated environmental shifts on your enterprise Service Level Objectives (SLOs)—all without actually executing a real injection!
☠️ Strike with Precision: L4/L7 Mutilation Engine
The core philosophy of Panic Design is "True Zero-Intrusion." Neither clients nor servers require any installed Agents or SDKs. Leveraging Cloudflare's formidable global edge network, we achieve:
- L4 Transport Layer Degradation: Precise control over packet loss, absolute latency (Base Latency), and network jitter across various distribution models (Uniform / Normal / Spikes).
- L7 Application Layer Mutilation: One-click overwrites for 429/502/504 status codes, Type Poisoning, Empty Shell responses, and brutal Unexpected EOF truncations—an absolute nightmare for OCD developers and fault-tolerance mechanisms.
🌍 Ending Black-Box Testing: Global Spatial Sandbox & Cyberpunk Console
To ensure you can clearly visualize exactly where a fault occurs, we developed the proprietary LGPA (Localized Geodesic Proximity Algorithm). It renders physical node spatial drift and network degradation trajectories in real-time on a 3D SVG World Map. More importantly, it rigorously dissects request latency into three distinct phases, putting an end to blind testing:
T1: Client to Edge Node latency.T2: Execution time consumed by the edge chaos injection.T3: The true RTT (Round Trip Time) from the Edge Node to the Upstream Origin.
Coupled with a highly immersive, cyberpunk-styled interactive terminal, you can monitor edge interception logs and the AI's Chain-of-Thought in real-time. Supported by multi-dimensional quota and usage panels, you gain sub-second, global revocation control over issued JWT Chaos Tokens.
🏗 Architectural Deep Dive: Cloud-Native Extreme Response
To guarantee absolute zero interference with normal traffic, Panic Design utilizes a strictly decoupled Control Plane & Data Plane architecture:
[ External Client ] ◄─────► [ Panic Design Edge Gateway ] ◄─────► [ Target Host ]
(W1 Ingress) (Global W2 Proxy Nodes) (Upstream)
- Control Plane (
new_website): Built with Next.js 16.2 App Router. It centrally manages OAuth authentication, D1 database interactions, Token quotas, and AIOps prompt engineering. For enterprise-grade security, the Control Plane utilizes the Web Crypto API to sign JWTs offline, securely embedding the chaos payload and target coordinates directly into the Token. - Data Plane (
new_website_data): A purely stateless reverse proxy built on the ultra-lightweight Hono framework. Deployed across Cloudflare's 300+ global edge nodes. Key Takeaway: It verifies JWT signatures and extracts chaos configurations in under 1ms per request! It then seamlessly injects L4/L7 mutilations and asynchronously writes telemetry logs to SQLite (D1), ensuring zero latency overhead for regular traffic.
💥 Zero-Intrusion Live Demo: Forcefully Dropping Connections
Let's look at a real-world test case demonstrating the extreme transparency of the Data Plane. Here, we inject Traffic Degradation (Latency) + Payload Mutilation (Unexpected EOF) into HTTP traffic:
$ export PANIC_TOKEN="eyJhbG...9qu4MA"
$ curl -i "https://gateway.andrewwangdev.com/?token=$PANIC_TOKEN"
HTTP/1.1 200 OK
Date: Tue, 09 Jun 2026 06:14:15 GMT
Content-Type: text/html; charset=UTF-8
Transfer-Encoding: chunked
Connection: keep-alive
CF-Ray: a08dfeb1b9940d77-LAX
...
X-Powered-By: Express <-- [Fully Transparent] The upstream app's actual framework header is retained.
X-Ratelimit-Limit: 1000 <-- [Fully Transparent] True upstream rate-limiting rules pass through seamlessly.
X-Ratelimit-Remaining: 996
X-Ratelimit-Reset: 1780985615
# ===== 👇 Panic Design Edge Telemetry Headers 👇 ===== #
x-panic-colo: LAX
# [Telemetry] The Cloudflare datacenter code where the proxy executed (Los Angeles).
x-panic-t2: 997
# [Telemetry] Exactly 997ms consumed to execute our configured "Traffic Degradation" chaos injection.
x-panic-t3: 20
# [Telemetry] The true RTT from the Data Plane edge node to the upstream origin (20ms).
x-panic-w1: -118.2437,34.0522
# [Telemetry] Estimated latitude/longitude of the requesting client. Used for LGPA 3D trajectory calculation.
x-panic-w3: 0,0
# [Telemetry] Upstream origin coordinates. When testing via a pure local curl lacking dashboard context, the Data Plane defaults this to zero to guarantee zero-intrusion and avoid even 1ms of extra DNS resolution overhead. Target resolution is pre-calculated offline by the Control Plane—pushing performance to the absolute limit!
...
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="utf-8" />
......
<p><strong>Note
... [ERR_TCP_RESET: CONNECTION_DROPPED_BY_PEER]
# 💥 [High Alert] Right here! Based on the "Unexpected EOF" strategy, the Data Plane forcefully dropped the TCP connection, triggering a truncated Payload error!
<script>(function(){function c(){var b=a.contentDocument||...
# [God-Tier Easter Egg] The <script> block appended after the truncation is actually Cloudflare's external Bot Challenge defense logic.
# The outermost traffic scrubbing mechanisms treated our "forcefully truncated error" as normal HTML! This perfectly proves that our gateway successfully penetrated and bypassed the outermost perimeter defenses!
⚠️ Notice
Tech for good. Please DO NOT use this tool for malicious attacks or unauthorized DDoS simulations.
📄 Legal & Privacy
By using Panic Design, you acknowledge and agree to our terms:
- Privacy Policy: https://panic.andrewwangdev.com/privacy
- Terms of Service: https://panic.andrewwangdev.com/terms
Built by Andrew Wang Dev —— If you are also tired of cumbersome YAMLs and intrusive Agents, join us in exploring the infinite possibilities of Edge AIOps Chaos Engineering!
讨论与反馈
登录后才能参与讨论
前往登录提 示
确定要删除这条评论吗?