5 articles
The technical companion: five components, two namespaces (public vs. internal split-horizon), one writer, two nameservers in two locations. Architecture, configuration samples, measured change latency, security, and how we verified the cutover.
This week, frao.tech began to be served by nameservers we own and operate ourselves — two independent hosts, two locations, one platform we control end to end. What the milestone means, what it gives us, and what it asks of us.
Frao-Guard: The Graduated Response — From Monitoring to Active Defense Frao-Guard spent its first weeks in observation mode — logging every packet, classifying every probe, scoring every attacker — by design. Once we had a clear picture of the threat...
# Frao-Guard: Network Defense at Kernel Speed — and What 10,000 Attackers Reveal > **The internet is not a friendly place. Every second, packets arrive at our gateway from hosts that have no business…
Environment Separation Plan: Development vs Production Status: Implemented and operational across all Frao stacks Approach: Dual VPN isolation ( frao.dev / frao.prod ) with same ports across both