BlogUpdated 2026-09-24

Why restricted-network tooling

Why Pouya Ghourchiani builds mirrors, installers, and gateways for places where crates.io, npm, and CDN defaults flake.

By Pouya GhourchianiGhourchiani

engineeringinfrastructure

Mainstream install paths assume open egress, stable registries, and English-only docs. A large share of real teams do not have that. This note is the “why” behind the restricted-network projects on this site.

The failure mode

Builds stall on crates.io timeouts. Docker pulls hang. VS Code extensions never reach the marketplace from the office network. The team then pastes random mirror URLs into chat — and nobody owns the next outage.

What “tooling” means here

Not another blog tutorial. A repeatable path: pinned mirrors, installers that vendor what they need, gateways with explicit auth boundaries, and notes that say what to measure when it breaks again.