pingoo

The fast and secure Load Balancer / API Gateway / Reverse Proxy with built-in service discovery, GeoIP, WAF, bot protection and much more - https://pingoo.io

Runssource: GitHubhomepageRustMITcommit f388e34e7adb

Rust, MIT licensed. The project labels itself: akamai, anti bot, apache2, api, api gateway, captcha, cloudflare and fastly.

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

Pingoo v0.14.9 compiles and runs as a static-file HTTP server, serving index.html on port 8080 with HTTP 200, using configurable paths via PINGOO_CONFIG/PINGOO_TLS_FOLDER/PINGOO_CAPTCHA_JWKS_PATH env vars instead of hardcoded /etc/pingoo

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 90 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs
Argusic Score
90 / 100
cost of the verifying run
$0.31 (measured)
recorded runs
2
last tested
stars
1,043
forks
44
open issues
22
watchers
16
size
0 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 pingoo, 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.

  • hardcoded /etc/pingoo paths unwritable (no root)10 minutes
  • captcha dist folder missing - npm build required before Rust compile3 minutes
  • info log message still prints DEFAULT_CONFIG_FILE constant instead of resolved path
Install time
15 minutes
Cold machine to finish
16 minutes
Errors hit and fixed
3 hit, 3 fixed with no human help
How the result was proved
curl -s -o /dev/null -w '%{http_code}' http://localhost:8080/ returned 200 with body '<html><body><h1>Hello from Pingoo</h1></body></html>'
Model tokens used
141,943
Exact commit tested
f388e34e7adb
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.

    Finished `test` profile [unoptimized] target(s) in 6.78s
     Running unittests pong.rs (target/debug/deps/pong-ac835ead04c0cc3e)
running 0 tests
test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s
exec
/bin/sh -lc 'cd /work/repo && . "$HOME/.cargo/env" && cargo check -p pingoo 2>&1 | grep -E "error|w…
 succeeded in 1666ms:
8
All tests pass, the build is clean, and the server is operational. Here's my summary:
tokens used
141,943
All tests pass, the build is clean, and the server is operational. Here's my summary:

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.
  • 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 MIT, as reported by its host.
  • Measured 2 times, so the result is not a one-off.

What did not, or is not known

  • Took 15 minutes to install, slower than the median of the 3 comparable projects Argusic has measured.

Of the 4 akamai projects Argusic has installed and timed, pingoo was the 3rd 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.

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.31
Argusic Runner1/3Unverified80.000.17

Topics (from GitHub)

akamaianti-botapache2apiapi-gatewaycaptchacloudflarefastlyfirewallhaproxyload-balancernginxpingooproxyquicreverse-proxyrustsecurityservice-discoverywaf

Embed the badge

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

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

Questions

Does pingoo run?
Yes. pingoo runs. Argusic installed and launched it on a clean machine in 15 minutes, hitting 3 errors on the way, and recorded the session.
How did Argusic test pingoo?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit f388e34e7adb. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test pingoo?
The run that produced this verdict cost $0.31: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does pingoo take to install?
15 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 pingoo need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing pingoo?
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.
How does pingoo compare with the alternatives?
Of the 4 akamai projects Argusic has installed and timed, pingoo was the 3rd fastest to reach a running state, and 4 of 4 reached one at all.
Where is the evidence for pingoo?
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