native_db
Drop-in embedded database in Rust
Runssource: GitHubRustMITcommit b9554fdabbdd
Rust, MIT licensed. The project labels itself: android, cross platform, database, embedded database, ios, kv store, mobile and orm.
native_db runs. An Argusic agent installed it in 12 minutes and hit 1 error and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
native_db v0.8.1 builds and passes all tests; the library compiles, all unit/integration tests succeed, doc-tests compile and run, and the major_upgrade example builds cleanly.
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
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.
- Rust toolchain (rustc, cargo) not found in PATH3 minutes
- Install time
- 12 minutes
- Cold machine to finish
- 3 minutes
- Errors hit and fixed
- 1 hit, 1 fixed with no human help
- How the result was proved
- cargo test: 156 integration/unit tests passed (0 failed, 7 ignored), 47 doc-tests passed (4 ignored), cargo test -F tokio --test watch_tokio: 1 passed
- Model tokens used
- 34,075
- Exact commit tested
- b9554fdabbdd
- 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 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.
**Tests**: All 156 integration + unit tests pass (plus 47 doc-tests/4 ignored). Some tests are pre-… **Examples**: `examples/major_upgrade` builds cleanly. No third-party keys needed — this is an embedded DB with no external services. **Final report:** tokens used 34,075 Everything is working. Here's the report: **Install**: Rust was missing initially. Installed via rustup (rustc 1.98.1). After that, `cargo bu… **Tests**: All 156 integration + unit tests pass (plus 47 doc-tests/4 ignored). Some tests are pre-… **Examples**: `examples/major_upgrade` builds cleanly. No third-party keys needed — this is an embedded DB with no external services. **Final report:**
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.
- Recovered from all 1 error 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 MIT, as reported by its host.
- Measured 2 times, so the result is not a one-off.
What did not, or is not known
- Took 12 minutes to install, slower than the median of the 7 comparable projects Argusic has measured.
Of the 8 android projects Argusic has installed and timed, native_db was the 6th fastest to reach a running state, and 7 of 8 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.
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
Topics (from GitHub)
androidcross-platformdatabaseembedded-databaseioskv-storemobileormreal-timerust
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/native-db)Questions
- Does native_db run?
- Yes. native_db runs. Argusic installed and launched it on a clean machine in 12 minutes, hitting 1 error on the way, and recorded the session.
- How did Argusic test native_db?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit b9554fdabbdd. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test native_db?
- 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 native_db take to install?
- 12 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 native_db need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing native_db?
- 1 thing broke in the recorded run, and 1 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does native_db compare with the alternatives?
- Of the 8 android projects Argusic has installed and timed, native_db was the 6th fastest to reach a running state, and 7 of 8 reached one at all.
- Where is the evidence for native_db?
- 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.