Yes. crate runs. Argusic installed and launched it on a clean machine in 30 minutes, hitting 1 error on the way, and recorded the session.

How did Argusic test crate?

On a fresh, disposable machine, with every command recorded and the repository pinned at commit 66927f3454e7. 3 attempts are recorded, and the full method is on the methodology page.

What did it cost to test crate?

The run that produced this verdict cost $0.08: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.

How long does crate take to install?

30 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 crate need a GPU?

Not to start. Argusic reached a running state on a machine with no GPU.

What goes wrong when installing crate?

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.

Where is the evidence for crate?

All 3 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.

crate

CrateDB is a distributed and scalable SQL database for storing and analyzing massive amounts of data in near real-time, even with complex queries. It is PostgreSQL-compatible, and based on Lucene.

Runssource: GitHub homepageJavaApache-2.0commit 66927f3454e7

Java, Apache-2.0 licensed. The project labels itself: analytics, big data, cratedb, database, dbms, distributed, distributed database and distributed sql database.

crate runs. An Argusic agent installed it in 30 minutes and hit 1 error and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

CrateDB 6.5.0 compiles, installs, launches as a single-node cluster, accepts HTTP SQL queries, and returns correct query results
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.08 (measured)
recorded runs: 3
last tested: 2026-09-25
stars: 4,450
forks: 621
open issues: 324
watchers: 169
size: 177 MB
created: 2013-04-10
last push: 2026-11-07

Subject data from GitHub, linked at the top of this page, refreshed 2026-11-07. 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.

Time lost to each failure while testing crate, drawn from the recorded run — Every bar is a failure the agent recorded, with the time it cost. Drawn from this run, not from anywhere else.

What went wrong, in the agent's own words

The agent's own words, worst first, never rewritten into advice.

JarHell in dist: duplicate crate-*.jar and crate-app-*.jar2 minutes

Install time: 30 minutes
Cold machine to finish: 27 minutes
Errors hit and fixed: 1 hit, 1 fixed with no human help
How the result was proved: curl -s -X POST http://127.0.0.1:14200/_sql -d '{"stmt":"SELECT * FROM test_table"}' returned rows [[1,"hello"],[2,"world"]], rowcount 2; mvn test across 5 modules passed 1258 tests/0 failures
Model tokens used: 194,707
Exact commit tested: 66927f3454e7
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

The end of the recording

The last lines of the terminal session that decided this verdict, exactly as they were recorded.

- Ran 22 tests in `libs/pgwire` — all passed
- Ran 329 tests in `libs/es-x-content` and `libs/sql-parser` — all passed
- Ran 715 server unit tests — all passed (34 skipped)
- Total: **1,258 tests passed, 0 failures, 0 errors**
**Launch verification:**
- Started CrateDB as a single-node cluster, confirmed it:
  - Listened on HTTP port 14200 and PostgreSQL wire port 5434
  - Responded to `GET /` with `{"ok":true,"status":200}`
  - Executed SQL queries via `POST /_sql` including `SELECT`, `CREATE TABLE`, `INSERT`, `SELECT COU…
  - Returned correct results: inserted 2 rows, queried back `[[1,"hello"],[2,"world"]]`
  - Full cluster metadata returned via `SELECT * FROM sys.cluster`
**Error fixed:** Jar hell in the distribution assembly — both `crate-6.5.0-*.jar` and `crate-app-6.…

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 Apache-2.0, as reported by its host.
Measured 3 times, so the result is not a one-off.

What did not, or is not known

Took 30 minutes to install, slower than the median of the 18 comparable projects Argusic has measured.

Of the 19 analytics projects Argusic has installed and timed, crate was the 17th fastest to reach a running state, and 15 of 19 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

tested by	attempt	outcome	score	cost USD	when
Argusic Runner	3/3	Runs	100.00	0.08	2026-09-25 01:48 UTC
Argusic Runner	2/3	Runs	100.00	0.13	2026-09-17 10:53 UTC
Argusic Runner	1/3	Runs	100.00	0.21	2026-09-07 11:50 UTC

Embed the badge

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

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

Questions

Does crate run?: Yes. crate runs. Argusic installed and launched it on a clean machine in 30 minutes, hitting 1 error on the way, and recorded the session.
How did Argusic test crate?: On a fresh, disposable machine, with every command recorded and the repository pinned at commit 66927f3454e7. 3 attempts are recorded, and the full method is on the methodology page.
What did it cost to test crate?: The run that produced this verdict cost $0.08: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does crate take to install?: 30 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 crate need a GPU?: Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing crate?: 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 crate compare with the alternatives?: Of the 19 analytics projects Argusic has installed and timed, crate was the 17th fastest to reach a running state, and 15 of 19 reached one at all.
Where is the evidence for crate?: All 3 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.