Expertise

Rust tooling

Systems tooling, control planes, and CLIs in Rust for reliable binaries in constrained networks — Axum, gateways, and installers.

I use Rust where reliability and deployable binaries matter more than framework fashion: Axum services, CLIs, and control-plane pieces that have to survive constrained networks.

Typical work: shared cores behind CLI + REST + TUI (aurum-rs), gateway-style services (NebulaGrid), DNS helpers (dnstt-kit), and Cargo workflows when crates.io is unreliable (cargo-rust-network-ir). The goal is boring production behavior — clear interfaces, explicit errors, and installers that work offline-ish.

Common questions

What does Pouya Ghourchiani build with Rust?

Axum services, CLIs, and control-plane pieces — NebulaGrid (gateway), aurum-rs (one core behind CLI, REST and TUI), and dnstt-kit (DNS tunnel helpers).

How do you run Cargo when crates.io is unreliable?

Mirrors, vendoring discipline, and prebuilt installers — documented in the cargo-rust-network-ir project and the “Running Cargo on a Restricted Network” note.

Why Rust instead of Node for these tools?

Deployable single binaries, explicit error handling, and predictable behavior on constrained networks matter more here than framework speed.

Related projects

Related writing

Other expertise