Bring the problem.
We bring the fix.

Linux and networking: Ubuntu, Alpine, CentOS, RHEL, Debian, Arch, VyOS, OPNsense, SONiC, Shell, Ansible, Python, and Terraform. Bring the issue. We build a twin, prove the fix, and hand you a runbook and cluster to evaluate.

Start a case
provision(cluster: ["vyos", "ubuntu24.04 x3"],networks: ["wan", "lan-a", "lan-b"],nics: node1 ["wan", "lan-a", "lan-b"], node2 ["lan-a"], node3 ["lan-b"], node4 ["lan-b"]) Up in 1200ms. 1 VyOS, 3 Ubuntu, 6 NICs, WAN, 2 LANs.
No credentialsNo production accessNo guesswork

The process

Twin.
Fix. Prove.

A twin gives us a controlled place to troubleshoot, test the fix, and make the result provable.

01

You: Bring the problem

Email and a problem statement in your own words.

02

We: Create twin

Same OS, topology, packages, and services.

03

We: Analysis

Review logs and configs to gain solid understanding.

04

We: Fix

Troubleshoot, fix, and check the result from a clean start.

05

We: Prove

A runbook and a twin cluster to prove the result.

What we fix

Linux.
Networks. Automation.

From Linux distributions to network operating systems, we work across the platforms below. Shell, Ansible, Python, and Terraform are the tools. The goal is infrastructure that works.

ShellAnsiblePythonTerraform
Typical problem areas
OSOperating systemspackages · services · permissions · systemd · clusters · security
NETNetworkingTCP/IP · subnets · VLANs · routing · BGP/OSPF · DNS · DHCP · ACLs · NAT · routers · switches
ENVReal environmentsVMs · clusters · containers · HA
Starting points
UbuntuAlpineCentOSRHELDebianArchVyOSOPNsenseSONiC

The handoff

You get the fix.
And the proof.

Everything needed to run the change, check the result, and understand what happened.

01the runbook

Instructions your team can follow.

  • Preconditions and assumptions
  • Exact commands and configuration
  • Expected output and checks
  • Rollback path when it matters
$ ./verify-infra.sh --clean
RESULT  hosts=3  failed=0
02the twin environment

A place to verify the fix yourself.

  • Same OS and relevant versions
  • Same topology and moving parts
  • Logs and evidence reviewed
  • Fix verified from clean state

Start with a signal

Tell us what broke.

Just your email and a rough description.

No credentials required.