OpenFlare

Next-Gen Distributed Reverse Proxy & Edge Security Gateway

Runssource: GitHubhomepageGoApache-2.0commit c3606bc6f6f0

Go, Apache-2.0 licensed. The project labels itself: cdn, cloudflare alternative, ddos protection, nat traversal, network, pingora, reverse proxy and security.

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

OpenFlare server (SQLite+Redis) parsed config, ran 48 SQLite goose migrations, started API+Worker+Scheduler all mode, served embedded Next.js frontend at :3000, authenticated admin login via POST /api/v1/user/login, served admin API endpoints under /api/v1/d/ returning 200, and rejected unauthenticated requests with 401; all 1543 Go tests and 132 frontend Vitest UI tests pass.

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.28 (measured)
recorded runs
1
last tested
stars
304
forks
76
open issues
1
watchers
0
size
95 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 OpenFlare, 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.

  • Redis not installed3 minutes
  • Go 1.25.x not in PATH2 minutes
  • Server died after background launch due to process-group cleanup2 minutes
  • Node 18 shipped no longer supports corepack-shim downloads1 minute
  • pnpm not available after corepack failed1 minute
  • PostgreSQL not available in container
Install time
19 minutes
Cold machine to finish
20 minutes
Errors hit and fixed
6 hit, 6 fixed with no human help
How the result was proved
go test ./... produced 1543 passed / 0 failed across 95 packages; frontend `npx vitest run` produced 26 files / 132 passed; curl POST /api/v1/user/login with admin/12345678 returned HTTP 200 + session cookie; curl -b session http://localhost:3000/api/v1/d/status returned HTTP 200 with real status data; curl http://localhost:3000/ returned HTTP 200 with rendered Next.js HTML; curl /api/v1/d/nodes without cookie returned HTTP 401
Model tokens used
639,747
Exact commit tested
c3606bc6f6f0
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.

/bin/sh -lc 'echo "All findings gathered. Compiling final report."; echo "Start: ~01:32, Now: $(dat…
 succeeded in 0ms:
All findings gathered. Compiling final report.
Start: ~01:32, Now: 01:51
Let me stop the running test session and compile the final report.
Now I have everything needed. Let me compile the final structured report.
Let me close out that test session and submit my final report.
All data collected. Here's the final report:
2026-10-26T01:52:44.168153Z ERROR codex_core::session: failed to record rollout items: thread 01a17…
tokens used
639,747
All data collected. Here's the final 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 19 minutes.
  • Recovered from all 6 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

tested byattemptoutcomescorecost USDwhen
Argusic Runner1/3Runs100.000.28

Topics (from GitHub)

cdncloudflare-alternativeddos-protectionnat-traversalnetworkpingorareverse-proxysecurityturnstilewaf

Embed the badge

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

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

Questions

Does OpenFlare run?
Yes. OpenFlare runs. Argusic installed and launched it on a clean machine in 19 minutes, hitting 6 errors on the way, and recorded the session.
How did Argusic test OpenFlare?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit c3606bc6f6f0. One attempt is recorded, and the full method is on the methodology page.
What did it cost to test OpenFlare?
The run that produced this verdict cost $0.28: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does OpenFlare take to install?
19 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 OpenFlare need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing OpenFlare?
6 things broke in the recorded run, and 6 were fixed without human help. Each one, and the time it cost, is listed on this page.
Where is the evidence for OpenFlare?
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