ceryx

Dynamic reverse proxy based on NGINX OpenResty with an API

Runssource: GitHubhomepagePythonMITcommit 6b642b72dcce

Python, MIT licensed. The project labels itself: docker, gateway, lets encrypt, letsencrypt, lua, nginx, proxy and reverse proxy.

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

Ceryx running as nginx 1.24.0 with Lua module on ports 80/443/8080; SQLite storage backend working; test suite 96/96 passing (routes, API, certificates, mTLS, HTTP/2, OpenAPI contract); proxying verified end-to-end through a Python echo server.

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.44 (measured)
recorded runs
1
last tested
stars
812
forks
145
open issues
5
watchers
44
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.

What went wrong, in the agent's own words

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

  • nginx and dockerize not present in container; Lua module not available
  • tests/utils.py create_certificates_for_host fails on re-run because openssl cannot overwrite chmod 444 files
  • tests/utils.py CERTIFICATE_ROOT hardcoded to /usr/local/share/certificates (not writable)
  • tests/test_certificates.py uses hardcoded /etc/ceryx/ssl/default.crt for SSL verification
  • tests/test_mtls.py uses hardcoded /usr/local/share/certificates path
Install time
26 minutes
Cold machine to finish
26 minutes
Errors hit and fixed
5 hit, 5 fixed with no human help
How the result was proved
curl -H 'Host: echo.ceryx.test' http://127.0.0.1:80/hello-world returned 'Hello from behind Ceryx! Path: /hello-world'; pytest tests/ -m 'not lets_encrypt' exited 0, 96 passed, 18 skipped
Model tokens used
678,133
Exact commit tested
6b642b72dcce
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.

 succeeded in 0ms:
Let me now also compute the time spent and check the final state.
exec
/bin/sh -lc date in /work/repo
 succeeded in 0ms:
Thu Nov 12 07:42:01 UTC 2026
Given the session started around 07:16, this is about 26 minutes.
Let me compile the final results.
tokens used
678,133
Given the session started around 07:16, this is about 26 minutes.
Let me compile the final results.

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 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 MIT, as reported by its host.

What did not, or is not known

  • Took 26 minutes to install, slower than the median of the 23 comparable projects Argusic has measured.
  • Measured once so far. A single attempt shows it can run, not that it runs reliably.

Of the 24 docker projects Argusic has installed and timed, ceryx was the 19th fastest to reach a running state, and 16 of 24 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 Runner1/3Runs100.000.44

Topics (from GitHub)

dockergatewaylets-encryptletsencryptluanginxproxyreverse-proxyssl

Embed the badge

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

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

Questions

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

Discussion