QuantDinger

The most complete open-source, self-hosted Agentic Trading OS, AI research, Python strategies, factor discovery, backtesting, optimization, paper/live multi-asset execution, risk controls, monitoring, MCP, and multi-tenant SaaS in one auditable stack.

Runssource: GitHubhomepagePythonApache-2.0commit a9c722e02476

Python, Apache-2.0 licensed. The project labels itself: agentic ai, ai agents, backtesting, crypto, finance, fintech, investment and llm.

QuantDinger runs. An Argusic agent installed it in 2 minutes and hit no errors on a clean machine with no GPU, and the whole session was recorded.

QuantDinger Python API v5.4.1 is installed and fully functional, all 3050 unit tests pass, the Flask app creates and serves the health endpoint on HTTP 200, and the only skipped tests require PostgreSQL/integration Docker containers that are not available in this environment.

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

At a glance

verdict
Runs
Argusic Score
96 / 100
cost of the verifying run
$0.03 (measured)
recorded runs
2
last tested
stars
13,800
forks
2,814
open issues
42
watchers
85
size
84 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.

Install time
2 minutes
Cold machine to finish
7 minutes
Errors hit and fixed
0 hit, 0 fixed with no human help
How the result was proved
pytest tests/ -q exited 0, 3050 passed, 55 skipped; curl http://127.0.0.1:5001/api/health returned 200 with {'status':'healthy','role':'legacy'}
Model tokens used
157,476
Exact commit tested
a9c722e02476
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

Watch the session

The whole run, from a clean machine, at the speed it actually happened. Nothing is cut and nothing is sped up.

A recording of attempt 2, run . The verdict above comes from a different attempt, so read this as one session and not as the current result. The terminal recording it was made from is the evidence, stored with a sha256 fingerprint; the video is a rendering of it. Nothing loads from the video host until you press play.

The end of the recording

The last lines of the terminal session that decided this verdict, exactly as they were recorded.

/bin/sh -lc 'cd /work/repo && cat backend_api_python/requirements-dev.txt' in /work/repo
 succeeded in 0ms:
bandit[toml]>=1.9.4,<2
pip-audit>=2.10.1,<3
pytest>=9.1.1,<10
pytest-cov>=7.1.0,<8
pytest-timeout>=2.4.0,<3
ruff>=0.16.0,<0.17
Good, I have all the data I need. Here's the final result:
tokens used
157,476
Good, I have all the data I need. Here's the final result:

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 2 minutes, faster than the median of the 137 comparable projects Argusic has measured.
  • Nothing broke on the way: zero errors between clone and running.
  • Ran without a GPU, so it does not need one to start.
  • Licensed Apache-2.0, as reported by its host.
  • Measured 2 times, so the result is not a one-off.

Of the 138 agent projects Argusic has installed and timed, QuantDinger was the 29th fastest to reach a running state, and 92 of 138 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 2 minutes after the clone.
  • Following its own README: the documented path worked with nothing to fix.

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/3Runs with mocks92.000.05
Argusic Runner1/3Runs100.000.03

Topics (from GitHub)

agentic-aiai-agentsbacktestingcryptofinancefintechinvestmentllmmarket-datamcpmcp-servermulti-agentportfolio-managementpythonquantquantitative-financerisk-managementself-hostedstock-markettechnical-analysis

Embed the badge

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

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

Questions

Does QuantDinger run?
Yes. QuantDinger runs. Argusic installed and launched it on a clean machine in 2 minutes, hitting 0 errors on the way, and recorded the session.
How did Argusic test QuantDinger?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit a9c722e02476. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test QuantDinger?
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 QuantDinger take to install?
2 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 QuantDinger need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing QuantDinger?
Nothing did, in the recorded run: zero errors between clone and running.
How does QuantDinger compare with the alternatives?
Of the 138 agent projects Argusic has installed and timed, QuantDinger was the 29th fastest to reach a running state, and 92 of 138 reached one at all.
Where is the evidence for QuantDinger?
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