nano-vectordb

A simple, easy-to-hack Vector Database

Runssource: GitHubPythonMITcommit 03f821348f04

Python, MIT licensed. The project labels itself: embedding, rag, vector and vector database.

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

The nano-vectordb package installs in a local venv, all 7 tests pass, and real upsert/query/get/delete/filter/save-reload and multi-tenant persistence operations all worked in this container.

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.01 (measured)
recorded runs
1
last tested
stars
211
forks
12
open issues
7
watchers
5
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.

Install time
5 minutes
Cold machine to finish
1 minutes
Errors hit and fixed
0 hit, 0 fixed with no human help
How the result was proved
python -m pytest -v exited 0 with 7 passed in 0.19s; a smoke script upserting 200 vectors, querying (top hit score 1.0), filtering, getting, deleting, saving/reloading, and persisting a multi-tenant entry printed SMOKE_OK
Model tokens used
44,789
Exact commit tested
03f821348f04
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 1, run , the attempt that decided the verdict above. 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.

Everything is verified. Final state of the mission:
- **Install**: `pip install -e .` in a Python 3.12 venv succeeded, installing `nano-vectordb 0.0.4.…
- **Tests**: `python -m pytest -v` exited 0 — **7 passed in 0.19s**.
- **Real behavior**: README Quick Start exercised end to end — upserted 200 vectors (report: 200 in…
- **Errors**: none encountered; no third-party keys or mocks required.
tokens used
44,789
Everything is verified. Final state of the mission:
- **Install**: `pip install -e .` in a Python 3.12 venv succeeded, installing `nano-vectordb 0.0.4.…
- **Tests**: `python -m pytest -v` exited 0 — **7 passed in 0.19s**.
- **Real behavior**: README Quick Start exercised end to end — upserted 200 vectors (report: 200 in…
- **Errors**: none encountered; no third-party keys or mocks required.

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 5 minutes.
  • Nothing broke on the way: zero errors between clone and running.
  • 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

  • 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.
  • A quick evaluation: it was running 5 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 Runner1/3Runs100.000.01

Topics (from GitHub)

embeddingragvectorvector-database

Embed the badge

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

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

Questions

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