Obscur

Network engineering studio · est. 2019

Networks that hold their shape under load.

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

Three things we do properly, and nothing else.

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.

  • BGP
  • Anycast
  • IPv6-first
  • WireGuard
  • Failover

02

Platform engineering

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.

  • Linux
  • Terraform
  • Ansible
  • Postgres
  • Backups

03

Interface systems

Admin surfaces and client apps for the infrastructure above — dense where operators need density, calm where clients need calm.

  • TypeScript
  • Design systems
  • Accessibility
  • Telemetry

02 / method

Four moves, in this order, every time.

Step 01

Map the failure

What breaks, how often, and what it costs. We start from the incident, not the diagram.

Step 02

Draw the smallest plan

The design that removes the failure with the fewest moving parts wins, even when it is less interesting.

Step 03

Build in the open

Repo, tickets, staging and a shared channel. You see the work as it happens, not after.

Step 04

Hand over a runbook

Documents your team can use at 3 a.m. without calling us. That is the point of the exercise.

03 / contact

Tell us what stopped working.

hello@obscurnet.com

Two slots open this quarter. Remote-first, working hours CET and EST, written English or Russian.

Studio
Obscur Network Studio
Base
New York · Lisbon
Reply
within one working day