01
Network & edge
Routing plans, anycast edges and private interconnects designed to survive a provider going sideways. We write the runbook before we write the config.
Network engineering studio · est. 2019
We design and run the quiet layer: routing, edge, private clouds and the interfaces that make them legible. Small team, direct lines, no account managers.
01 / practice
01
Routing plans, anycast edges and private interconnects designed to survive a provider going sideways. We write the runbook before we write the config.
02
Boring, reproducible hosts: immutable images, key-only access, backups that are actually restored once a quarter, monitoring that pages a human only when it matters.
03
Admin surfaces and client apps for the infrastructure above — dense where operators need density, calm where clients need calm.
02 / method
What breaks, how often, and what it costs. We start from the incident, not the diagram.
The design that removes the failure with the fewest moving parts wins, even when it is less interesting.
Repo, tickets, staging and a shared channel. You see the work as it happens, not after.
Documents your team can use at 3 a.m. without calling us. That is the point of the exercise.
Two slots open this quarter. Remote-first, working hours CET and EST, written English or Russian.