port-buddy
Expose local ports to the internet in seconds
Runssource: GitHubhomepageJavaApache-2.0commit 59a2ef2b452f
Java, Apache-2.0 licensed. The project labels itself: localhost tunnel, ngrok alternative, port forwarding, port forwarding tcp, port forwarding udp, reverse proxy, reverse proxy ssh and tcp tunnel.
port-buddy runs. An Argusic agent installed it in 12 minutes and hit 2 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
All 8 Maven modules build and all 145 tests pass across eureka, gateway, net-proxy, server, and ssl-service modules; the CLI jar prints 'portbuddy 1.0-SNAPSHOT' with full usage help
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
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.

What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- Java 25 JDK not found in container2 minutes
- Web (npm) build failed: 'URI malformed' on index.html because VITE_CANONICAL env var was unset, leaving %VITE_CANONICAL% literal in HTML1 minute
- Install time
- 12 minutes
- Cold machine to finish
- 12 minutes
- Errors hit and fixed
- 2 hit, 2 fixed with no human help
- How the result was proved
- mvn test exited 0, 145 tests passed, 0 failures, 0 errors; java -jar cli/target/cli-1.0-SNAPSHOT.jar --version returned 'portbuddy 1.0-SNAPSHOT'; java -jar cli/target/cli-1.0-SNAPSHOT.jar --help printed full usage; Java modules (common, cli, server, net-proxy, gateway, eureka, ssl-service) built successfully; web npm build succeeded
- Model tokens used
- 180,898
- Exact commit tested
- 59a2ef2b452f
- 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.
**Setup & Install** - Java 25 was not installed — downloaded Temurin JDK 25.0.5+7 and set `JAVA_HOME` - Web (npm) build failed because `VITE_CANONICAL` was unset, causing a "URI malformed" error in Vit… - After those fixes, full Maven build passed (`./mvnw clean install -DskipTests`) across all 8 modu… **Tests** - `./mvnw test` — **145 tests run, 0 failures, 0 errors, 0 skipped** - Tests cover eureka, gateway (security, SSL, config), net-proxy (tunnel registry, concurrency, evi… **CLI Verification** - `java -jar cli/target/cli-1.0-SNAPSHOT.jar --version` → `portbuddy 1.0-SNAPSHOT` - `java -jar cli/target/cli-1.0-SNAPSHOT.jar --help` → prints full usage with http, tcp, udp modes … **Server** - Eureka starts and registers; server needs PostgreSQL for full startup (unsatisfied DB dependency …
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 12 minutes.
- Recovered from all 2 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.
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
Topics (from GitHub)
localhost-tunnelngrok-alternativeport-forwardingport-forwarding-tcpport-forwarding-udpreverse-proxyreverse-proxy-sshtcp-tunneludp-tunnel
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/port-buddy)Questions
- Does port-buddy run?
- Yes. port-buddy runs. Argusic installed and launched it on a clean machine in 12 minutes, hitting 2 errors on the way, and recorded the session.
- How did Argusic test port-buddy?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 59a2ef2b452f. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test port-buddy?
- 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 port-buddy take to install?
- 12 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 port-buddy need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing port-buddy?
- 2 things broke in the recorded run, and 2 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for port-buddy?
- 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.