nylon

Self-healing WireGuard mesh. Reroutes around failures in seconds, no coordination server, fully FOSS.

Runssource: GitHubhomepageGoApache-2.0commit 93ad8733c75b

Go, Apache-2.0 licensed. The project labels itself: distributed networking, golang, mesh, mesh networks, overlay network, routing, self hosted and vpn.

nylon runs. An Argusic agent installed it in 46 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

Nylon builds cleanly and its unit, router, and integration suites pass; the daemon launches rootless via NYLON_RUN_DIR and answers live IPC status queries, while config verification and sealed-bundle open round-trips succeed.

What the agent ended up with on a clean machine, in its own words. How this is measured

Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 60 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs
Argusic Score
60 / 100
cost of the verifying run
$0.24 (measured)
recorded runs
2
last tested
stars
537
forks
27
open issues
12
watchers
5
size
8 MB
created
last push

Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.

What was measured

From the run that decided this verdict. Every line is a recorded value, not an estimate.

Time lost to each failure while testing nylon, drawn from the recorded run
Every bar is a failure the agent recorded, with the time it cost. Drawn from this run, not from anywhere else.

What went wrong, in the agent's own words

The agent's own words, worst first, never rewritten into advice.

  • nylon status failed with connection refused against running daemon22 minutes
  • mkdir /var/run/wireguard: permission denied (rootless)6 minutes
  • No Go toolchain in container4 minutes
Install time
46 minutes
Cold machine to finish
22 minutes
Errors hit and fixed
3 hit, 3 fixed with no human help
How the result was proved
NYLON_RUN_DIR=/tmp/ny/final/home /work/repo/nylon run -c /tmp/ny/central.yaml -n /tmp/ny/node.yaml -v -j then NYLON_RUN_DIR=... /work/repo/nylon status -i nylon returned 'interface: nylon ... listening port 57176' (exit 0), repeated across 8 launches
Model tokens used
1,070,876
Exact commit tested
93ad8733c75b
Container image
sha256:cdd920bce783

What was not measured

The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.

Peak GPU memory
this ran on a CPU machine, so there was no GPU to sample
Behaviour over a long run
each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load

The end of the recording

The last lines of the terminal session that decided this verdict, exactly as they were recorded.

- `nylon run` died immediately with `mkdir /var/run/wireguard: permission denied` (no root in conta…
- `nylon status`/`probe` worked briefly then consistently returned `connection refused` against a l…
- The e2e suite couldn't run: it needs Docker and TUN (`/dev/net/tun`), which this container lacks;…
**Verified by direct commands**
- `go build -ldflags "-s -w" -o nylon .` → exit 0.
- `go test ./... ./integration/... ./polyamide/...` → all packages `ok`, exit 0.
- `go test -race -tags=router_test ./core/... ./state/...` → `ok` 1.385s / 1.435s.
- `go test -race -tags=integration ./integration/...` → `ok` 59.044s.
- `./nylon --help` exit 0; `./nylon version` → `Version: v0.0.0-20260924024011-93ad8733c75b+dirty`.
- `./nylon verify central.yaml --node node.yaml` → `Config is valid`.
- `./nylon seal -c dist-central.yaml -k central.key -o central.nybundle` → wrote 592-byte bundle; `…
- `nylon run -c central.yaml -n node.yaml -v -j` launched and logged `Nylon has been initialized`, …

Replay the whole session, every command from a clean machine to this point.

How it was tested

One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.

Strengths and limits

Measured facts, not opinions. How this is written.

What went well

  • Reached a running state on a clean machine, with the session recorded.
  • Installed in 46 minutes.
  • Recovered from all 3 errors without a human stepping in, which says the failures are documented well enough to solve.
  • Ran without a GPU, so it does not need one to start.
  • Licensed Apache-2.0, as reported by its host.
  • Measured 2 times, so the result is not a one-off.

What it is a reasonable choice for

  • Trying it on a laptop or a small server: it reached a running state without a GPU.

Also tested, in the same area

Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.

Run history

tested byattemptoutcomescorecost USDwhen
Argusic Runner2/3Runs100.000.24
Argusic Runner1/3Did not run20.000.13

Topics (from GitHub)

distributed-networkinggolangmeshmesh-networksoverlay-networkroutingself-hostedvpnwireguard

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/nylon.svg)](https://argusic.com/subject/nylon)

Questions

Does nylon run?
Yes. nylon runs. Argusic installed and launched it on a clean machine in 46 minutes, hitting 3 errors on the way, and recorded the session.
How did Argusic test nylon?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 93ad8733c75b. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test nylon?
The run that produced this verdict cost $0.24: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does nylon take to install?
46 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
Does nylon need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing nylon?
3 things broke in the recorded run, and 3 were fixed without human help. Each one, and the time it cost, is listed on this page.
Where is the evidence for nylon?
All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

Discussion