rqlite
The lightweight, fault-tolerant database built on SQLite. Designed to keep your data highly available with minimal effort.
Runssource: GitHubhomepageGoMITcommit 7eb7e54b14df
Go, MIT licensed. The project labels itself: consensus, database, distributed database, distributed systems, fault tolerance, go, high availability and raft.
rqlite runs. An Argusic agent installed it in 16.4 minutes and hit 7 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
rqlited is running on 127.0.0.1:44001, its HTTP endpoints return 200, and the built binary serves persisted SQL rows while the Go unit/integration suite and 15 single-node E2E tests pass.
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.
- `Test_Geopoly` failed because its expected JSON hardcoded `\ufffd` while Go 1.27.3 encoded the same replacement character as literal UTF-8.8 minutes
- Go toolchain was not installed or on PATH; `go version` returned `go: not found`, blocking the documented `go install ./...` workflow.2 minutes
- The first rqlited verification process exited when its launching command session ended, so curl and rqlite received connection failures.2 minutes
- The first single-node E2E run had two FileNotFoundError errors for system_test/e2e/testdata/1000-numbers.db.2 minutes
- Python requests was missing, preventing the bundled system_test/e2e suite from importing helpers.1 minute
- `/usr/bin/time` was unavailable while timing the install (`/usr/bin/time: No such file or directory`).
- Install time
- 16 minutes
- Cold machine to finish
- 17 minutes
- Errors hit and fixed
- 7 hit, 7 fixed with no human help
- How the result was proved
- go install ./... exited 0 in 91s; rqlited -version printed 'rqlited 10 linux amd64 go1.27.3 sqlite3.53.4 (commit unknown, compiler gc)'; go test -count=1 -timeout 20m -json ./... exited 0 with 1826 passed, 4 skipped, 0 failed across 49 packages; go vet ./... exited 0; python3 system_test/e2e/single_node.py exited 0 with 'Ran 15 tests ... OK'; curl POST /db/execute returned 200 and GET /db/query returned 200 with rows [[1,fiona],[2,declan],[3,clara]]; /readyz, /status, and /console/ each returned 200.
- Model tokens used
- 385,460
- Exact commit tested
- 7eb7e54b14df
- 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.
\"final_state\":\"rqlited is running on 127.0.0.1:44001, its HTTP endpoints return 200, and the bu…
}
print(json.dumps(result,separators=(',',':')))
PY" in /work/repo
succeeded in 0ms:
{"install_succeeded":true,"launch_succeeded":true,"install_minutes":16.4,"errors":[{"msg":"Go toolc…
Installed and verified rqlite end to end. The full Go suite passed with 1,826 tests, 4 skips, and 0…
The only repository change is `db/db_common_test.go:1`, replacing a brittle escaped-JSON string com…
tokens used
385,460
Installed and verified rqlite end to end. The full Go suite passed with 1,826 tests, 4 skips, and 0…
The only repository change is `db/db_common_test.go:1`, replacing a brittle escaped-JSON string com…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 16.4 minutes.
- Recovered from all 7 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 MIT, 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.
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)
consensusdatabasedistributed-databasedistributed-systemsfault-tolerancegohigh-availabilityraftrelational-databasesqlsqlite
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/rqlite)Questions
- Does rqlite run?
- Yes. rqlite runs. Argusic installed and launched it on a clean machine in 16 minutes, hitting 7 errors on the way, and recorded the session.
- How did Argusic test rqlite?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 7eb7e54b14df. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test rqlite?
- The run that produced this verdict cost $0.15: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does rqlite take to install?
- 16.4 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 rqlite need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing rqlite?
- 7 things broke in the recorded run, and 7 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for rqlite?
- 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.