FerretDB
A truly Open Source MongoDB alternative
Could not verifysource: GitHubhomepageGoApache-2.0commit 799235dab9e3
Go, Apache-2.0 licensed. The project labels itself: database, document, ferretdb, go, golang, hacktoberfest, mongo and mongo db.
Argusic could not get FerretDB running. An Argusic agent installed it in 9 minutes and hit 5 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
FerretDB compiles, builds to a working binary that starts and listens on port 27017, and 19 test packages (35 individual tests) pass; 5 packages fail solely because no PostgreSQL with DocumentDB extension is available in the 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 80 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.
- Go not pre-installed in container1 minute
- build/version/version.txt and related files missing (no git tags)1 minute
- cmd/ferretdb/ test failed: bin/ferretdb binary not found1 minute
- resource test TestTrackUntrack/LocalCleanup failed without ferretdb_dev tag1 minute
- All tests requiring PostgreSQL with DocumentDB extension fail: internal/documentdb, internal/dataapi, ferretdb — no PostgreSQL installed and no root/Docker access
- Install time
- 9 minutes
- Cold machine to finish
- 11 minutes
- Errors hit and fixed
- 5 hit, 5 fixed with no human help
- How the result was proved
- go test -tags ferretdb_dev -count=1 ./cmd/ferretdb/ ./internal/clientconn/ ./internal/handler/ ./internal/mcp/ ./internal/mongoerrors/ ./internal/util/... ./build/version/, 19 packages passed, 35 tests passed; /tmp/ferretdb --version printed version/commit/branch; /tmp/ferretdb started and listened on :27017
- Model tokens used
- 356,414
- Exact commit tested
- 799235dab9e3
- 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
- Whether it works at all
- this run verified nothing, so this page makes no claim either way
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
|---|---| | `go: not found` — Go not available in container | Downloaded Go 1.25.7 tarball to `$HOME/go`, set… | `build/version` test: version.txt/commit.txt missing (no git tags) | Created `build/version/versi… | `cmd/ferretdb` test: `TestVersion` failed looking for `bin/ferretdb` | Built the binary to `bin/f… | `resource` test `TestTrackUntrack/LocalCleanup` failed without `ferretdb_dev` tag | Built and tes… **Unfixable errors (require PostgreSQL + DocumentDB extension, no root/Docker available):** - `internal/documentdb` — connection refused to 127.0.0.1:5432 - `internal/documentdb/genwrap` — connection refused to 127.0.0.1:5432 - `internal/dataapi` — connection refused to 127.0.0.1:5432 - `ferretdb` — connection refused to 127.0.0.1:5432 **Tests passing:** 19 packages / 35 test functions all passed **Binary verification:** `./bin/ferretdb --version` printed version, commit, branch info. Running w…
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 Apache-2.0, as reported by its host.
- Measured 2 times, so the result is not a one-off.
What did not, or is not known
- An agent with no time limit did not get it running.
- Took 9 minutes to install, slower than the median of the 23 comparable projects Argusic has measured.
Of the 24 database projects Argusic has installed and timed, FerretDB was the 19th fastest to reach a running state, and 19 of 24 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 | 2/3 | Unverified | 80.00 | 0.06 | |
| Argusic Runner | 1/3 | Unverified | 80.00 | 0.07 |
Topics (from GitHub)
databasedocumentferretdbgogolanghacktoberfestmongomongo-dbmongodbmongodb-databasepostgrespostgresql
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/ferretdb)Questions
- Does FerretDB run?
- Argusic could not verify that FerretDB runs. Argusic installed and launched it on a clean machine in 9 minutes, hitting 5 errors on the way, and recorded the session.
- How did Argusic test FerretDB?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 799235dab9e3. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test FerretDB?
- The run that produced this verdict cost $0.06: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does FerretDB take to install?
- 9 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 FerretDB need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing FerretDB?
- 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 FerretDB compare with the alternatives?
- Of the 24 database projects Argusic has installed and timed, FerretDB was the 19th fastest to reach a running state, and 19 of 24 reached one at all.
- Where is the evidence for FerretDB?
- 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.