Yes. infinity runs. Argusic installed and launched it on a clean machine in 8 minutes, hitting 3 errors on the way, and recorded the session.

How did Argusic test infinity?

On a fresh, disposable machine, with every command recorded and the repository pinned at commit b1083912a500. 2 attempts are recorded, and the full method is on the methodology page.

What did it cost to test infinity?

The run that produced this verdict cost $0.10: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.

How long does infinity take to install?

8 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 infinity need a GPU?

Not to start. Argusic reached a running state on a machine with no GPU.

What goes wrong when installing infinity?

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.

Where is the evidence for infinity?

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.

infinity

The AI-native database built for LLM applications, providing incredibly fast hybrid search of dense vector, sparse vector, tensor (multi-vector), and full-text.

Runssource: GitHub homepageC++Apache-2.0commit b1083912a500

C++, Apache-2.0 licensed. The project labels itself: ai native, approximate nearest neighbor search, bm25, cpp20, cpp20 modules, embedding, full text search and hnsw.

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

Infinity v0.7.3 nightly (x86_64-v2) standalone server starts and accepts Thrift connections on port 23817 and HTTP on port 23820; Python SDK can create tables, insert vectors, run dense vector search queries, and return results via Polars DataFrames
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 60 of 100 (the mean of this project's run scores).

At a glance

verdict: Runs
Argusic Score: 60 / 100
cost of the verifying run: $0.10 (measured)
recorded runs: 2
last tested: 2026-09-30
stars: 4,728
forks: 453
open issues: 142
watchers: 49
size: 80 MB
created: 2022-07-18
last push: 2026-09-23

Subject data from GitHub, linked at the top of this page, refreshed 2026-09-30. 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 infinity, 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.

Cannot build from source: container lacks clang-20, cmake 4.x, vcpkg, and root apt access2 minutes
Cannot create /var/infinity and /usr/share/infinity/resource - no root2 minutes
Can not pin thread! warnings printed at startup

Install time: 8 minutes
Cold machine to finish: 12 minutes
Errors hit and fixed: 3 hit, 3 fixed with no human help
How the result was proved: uv run python -c 'import infinity; infinity.connect(NetworkAddress("127.0.0.1",23817)).get_database("default_db").create_table(...).insert(...).output(["*"]).match_dense(...).to_pl()' returned correct Polars DataFrame with 2 rows; HTTP API POST/DELETE /databases returned {"error_code":0}; both TCP ports 23817 and 23820 were reachable
Model tokens used: 124,016
Exact commit tested: b1083912a500
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.

kill 9807 2>/dev/null
sleep 1
kill -0 9807 2>/dev/null && kill -9 9807 2>/dev/null || true
echo "Server stopped"' in /work/repo
 succeeded in 851ms:
Server stopped
Now let me compile the final report. I've verified the Infinity database works end-to-end in this c…
The server binary (`/work/repo/infinity_bin/infinity-x86_64-v2/bin/infinity`) launches successfully…
tokens used
124,016
Now let me compile the final report. I've verified the Infinity database works end-to-end in this c…
The server binary (`/work/repo/infinity_bin/infinity-x86_64-v2/bin/infinity`) launches successfully…

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

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 8 minutes after the clone.

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 by	attempt	outcome	score	cost USD	when
Argusic Runner	2/3	Runs	100.00	0.10	2026-09-30 04:55 UTC
Argusic Runner	1/3	Did not run	20.00	0.63	2026-09-30 02:39 UTC

Topics (from GitHub)

ai-native approximate-nearest-neighbor-search bm25 cpp20 cpp20-modules embedding full-text-search hnsw hybrid-search information-retrival multi-vector nearest-neighbor-search rag search-engine tensor-database vector vector-database vector-search vectordatabase

Embed the badge

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

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

Questions

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