Network infra engineer. I build tools that check whether the obvious explanation is actually true, and a few systems that just got to work.
A.V.E.N.G.E: edge vibration analytics
Go-based edge computing engine for real-time vibration analytics, inline signal compression, and predictive anomaly detection. Zero external runtime dependencies, zero-heap-allocation hot path.
FFT → SDT compression → Z-score anomaly detection.
MQTT → ClickHouse → Grafana, one docker compose up and u got the core stack.
- railcast: Sparkle is the updater. Railcast is the backend it needs.
live - komposer: terminal UI for Docker Compose files with spec validation and security checks.
- platform-infra: self-service infrastructure for small teams on Cloudflare Workers + D1 + R2 & gh runners.
friction → investigation → hypothesis → tool
- gai:
digworking doesn't mean your process resolves the name the same way. Reconstructs the realgetaddrinfo()decision path. - khm:
known_hostsis a database of server identities, not a cache. - cfzt: one-command Cloudflare Zero Trust Tunnel cli.
- sidecheck: remote timing side-channel detection using statistics instead of a stopwatch.
- burnafterread: share a secret without giving the server access to it.
live - netconv: config conversion is about semantics, not replacing keywords.
Packets are evidence, not truth. Everything runs in the browser; PCAPs never leave your machine.
Zero Trust ain't just for infra. Don't trust this file either, verify it.
Verify this README
gpg --keyserver keys.openpgp.org --recv-keys 2A49CD4AF95F76DF38FC1F9EBFB3563375149683
curl -sO https://raw.githubusercontent.com/casablanque-code/casablanque-code/main/README.md
curl -sO https://raw.githubusercontent.com/casablanque-code/casablanque-code/main/README.md.sig
gpg --verify README.md.sig README.md
