vectordbz
A modern desktop application for exploring, managing, and analyzing vector databases
Runs with mockssource: GitHubhomepageTypeScriptMITcommit 57d51d2549ba
TypeScript, MIT licensed. The project labels itself: ai, aitools, chroma, database management, embeddings, milvus, pgvector and pinecone.
vectordbz runs, with stand-ins for the services it depends on. An Argusic agent installed it in 29 minutes and hit 5 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
npm ci completes successfully, Vite builds produce valid bundles, the Electron app launches on Xvfb with a visible VectorDBZ 1400x900 window connected to the Vite renderer dev server. The embedding mock server serves embedding vectors on port 3005. Integration tests require Docker containers not available in this environment. Package step fails with OOM.
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 92 of 100 (the mean of this project's run scores).
At a glance
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.
- Node.js version mismatch - system has v18.19.1, project requires >=22.12.03 minutes
- Corrupted Vite build artifacts from prior failed package attempt caused Electron SyntaxError: Unexpected end of input2 minutes
- Electron main.js entry-point had duplicated content after rebuild1 minute
- All 8 database integration test files fail - require Docker containers for Qdrant, Weaviate, ChromaDB, Milvus, pgvector, Pinecone, Elasticsearch, RedisSearch (docker not available in container)
- npm run package (electron-forge make) runs out of memory (OOM)
- Install time
- 29 minutes
- Cold machine to finish
- 30 minutes
- Errors hit and fixed
- 5 hit, 5 fixed with no human help
- How the result was proved
- npm run start (via electron-forge) launched Electron app; VectorDBZ window 1400x900 appeared on virtual display :99 and Electron processes remained alive for 25+ seconds. Embedding server at localhost:3005 responded 200 on POST /embed/text with valid 384-dim embedding vector. Electron --version via forge returned 7.11.1.
- Model tokens used
- 497,049
- Exact commit tested
- 57d51d2549ba
- 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
- Behaviour against real services
- this run was verified against stand-in services only
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
succeeded in 0ms:
The task is complete. Let me clean up the running processes.
exec
/bin/sh -lc "ps aux | grep \"[e]lectron\" | grep -v codex | grep -v grep | awk '{print "'$2}'"' | x…
ps aux | grep \"[v]ite\" | grep -v codex | grep -v grep | awk '{print "'$2}'"' | xargs -r kill 2>/d…
echo \"Cleanup done\"" in /work/repo
succeeded in 0ms:
Cleanup done
Done. The app has been installed, built, and launched—VectorDBZ window appeared on the virtual disp…
tokens used
497,049
Done. The app has been installed, built, and launched—VectorDBZ window appeared on the virtual disp…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
- Recovered from all 5 errors without a human stepping in, which says the failures are documented well enough to solve.
- Licensed MIT, as reported by its host.
What did not, or is not known
- Only reached a running state against stand-in services, so nothing here proves it works against the real ones.
- Took 29 minutes to install, slower than the median of the 236 comparable projects Argusic has measured.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 237 ai projects Argusic has installed and timed, vectordbz was the 223rd fastest to reach a running state, and 168 of 237 reached one at all.
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 | 1/3 | Runs with mocks | 92.00 | 0.51 |
Topics (from GitHub)
aiaitoolschromadatabase-managementembeddingsmilvuspgvectorpineconeqdrantragsemantic-searchvector-data-managementvector-databasevector-database-embeddingvector-searchvector-storevectordatabasevectordbvectorspaceweaviate
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/vectordbz)Questions
- Does vectordbz run?
- vectordbz runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 29 minutes, hitting 5 errors on the way, and recorded the session.
- How did Argusic test vectordbz?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 57d51d2549ba. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test vectordbz?
- The run that produced this verdict cost $0.51: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does vectordbz take to install?
- 29 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 vectordbz need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing vectordbz?
- 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 vectordbz compare with the alternatives?
- Of the 237 ai projects Argusic has installed and timed, vectordbz was the 223rd fastest to reach a running state, and 168 of 237 reached one at all.
- Where is the evidence for vectordbz?
- 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.