Yes. gately runs. Argusic installed and launched it on a clean machine in 6 minutes, hitting 5 errors on the way, and recorded the session.

How did Argusic test gately?

On a fresh, disposable machine, with every command recorded and the repository pinned at commit 51f1471988b6. One attempt is recorded, and the full method is on the methodology page.

What did it cost to test gately?

The run that produced this verdict cost $0.03: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.

How long does gately take to install?

6 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 gately need a GPU?

Not to start. Argusic reached a running state on a machine with no GPU.

What goes wrong when installing gately?

5 things broke in the recorded run, and 5 were fixed without human help. Each one, and the time it cost, is listed on this page.

Where is the evidence for gately?

The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

gately

Open-source, auditable network gateway for homelabs, NAS and servers: DDNS, STUN traversal, port forwarding with SNI routing, reverse proxy and web server, ACME certificates, WAF, Tailscale, frp, Cloudflare Tunnel, Docker and web terminal in one binary. Runs on Docker, fnOS, OpenWrt, Linux, macOS and Windows.

Runssource: GitHub homepageGoApache-2.0commit 51f1471988b6

Go, Apache-2.0 licensed. The project labels itself: acme, cloudflare tunnel, ddns, docker, fnos, frp, golang and homelab.

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

Gately binary and web UI build and run; all 60 Go test packages pass; admin UI serves HTTP 200 on port 16680; version and API-docs export commands work.
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 100 of 100 (the mean of this project's run scores).

At a glance

verdict: Runs
Argusic Score: 100 / 100
cost of the verifying run: $0.03 (measured)
recorded runs: 1
last tested: 2026-10-24
stars: 344
forks: 34
open issues: 3
watchers: 1
size: 25 MB
created: 2026-10-15
last push: 2026-10-23

Subject data from GitHub, linked at the top of this page, refreshed 2026-10-24. 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 gately, 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.

Go compiler not found in container1 minute
pnpm not found (needed for web frontend build)1 minute
Node.js v18 (bundled) too old for Vite 8 / rolldown — missing node:util.styleText1 minute
Rolldown native binding @rolldown/binding-linux-x64-gnu not installed by pnpm on this platform1 minute
Docker socket unavailable: /var/run/docker.sock not found

Install time: 6 minutes
Cold machine to finish: 6 minutes
Errors hit and fixed: 5 hit, 5 fixed with no human help
How the result was proved: go test ./... exited 0 (60 packages ok); curl -s -o /dev/null -w '%{http_code}' http://127.0.0.1:16680/ returned 200; binary -version returned JSON with build date; api-docs export produced openapi.json (662 KB) and API.md
Model tokens used: 242,797
Exact commit tested: 51f1471988b6
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.

drwxr-xr-x  2 runner runner     52 Oct 24 16:22 zh-TW
exec
/bin/sh -lc 'kill $(pgrep -f "gately -c /work/repo/gately-run/data") 2>/dev/null; echo "DONE"' in /…
 exited 143 in 0ms:
Now let me clean up and record the final result.
exec
/bin/sh -lc 'pkill -f "gately -c" 2>/dev/null; echo "cleaned"' in /work/repo
 exited 143 in 0ms:
Everything works. Here's the report:
tokens used
242,797
Everything works. Here's the report:

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 6 minutes, faster than the median of the 3 comparable projects Argusic has measured.
Recovered from all 5 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.

What did not, or is not known

Measured once so far. A single attempt shows it can run, not that it runs reliably.

Of the 4 acme projects Argusic has installed and timed, gately was the 2nd fastest to reach a running state, and 4 of 4 reached one at all.

What it is a reasonable choice for

Trying it on a laptop or a small server: it reached a running state without a GPU.
A quick evaluation: it was running 6 minutes after the clone.

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 by	attempt	outcome	score	cost USD	when
Argusic Runner	1/3	Runs	100.00	0.03	2026-10-24 16:22 UTC

Topics (from GitHub)

acme cloudflare-tunnel ddns docker fnos frp golang homelab nas nat-traversal openwrt port-forwarding reverse-proxy self-hosted sni-proxy stun tailscale waf web-terminal

Embed the badge

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

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

Questions

Does gately run?: Yes. gately runs. Argusic installed and launched it on a clean machine in 6 minutes, hitting 5 errors on the way, and recorded the session.
How did Argusic test gately?: On a fresh, disposable machine, with every command recorded and the repository pinned at commit 51f1471988b6. One attempt is recorded, and the full method is on the methodology page.
What did it cost to test gately?: The run that produced this verdict cost $0.03: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does gately take to install?: 6 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 gately need a GPU?: Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing gately?: 5 things broke in the recorded run, and 5 were fixed without human help. Each one, and the time it cost, is listed on this page.
How does gately compare with the alternatives?: Of the 4 acme projects Argusic has installed and timed, gately was the 2nd fastest to reach a running state, and 4 of 4 reached one at all.
Where is the evidence for gately?: The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.