matrixone
AI-native HTAP database with Git-for-Data and built-in vector search, serving as the data and memory backbone for intelligent agents and applications.
Runssource: GitHubhomepageGoApache-2.0commit 7ce783464806
Go, Apache-2.0 licensed. The project labels itself: agents, ai native, cloud native, database, distributed database, distributed systems, fulltext support and git for data.
matrixone runs. An Argusic agent installed it in 29 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
MatrixOne server built from source (mo-service, 275MB binary), launched on port 6001, accepting MySQL protocol connections, queries returning correct results including data manipulation operations.
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.
- archsimd API mismatch: Load*Slice functions renamed to Load*, Store(&x) must use Store(x[:])3 minutes
- Server exited on startup due to stale data directory causing CN admission deadline exceeded3 minutes
- Go 1.26.4+ not installed (system has no go binary)2 minutes
- Install time
- 29 minutes
- Cold machine to finish
- 34 minutes
- Errors hit and fixed
- 3 hit, 3 fixed with no human help
- How the result was proved
- mysql -h 127.0.0.1 -P 6001 -u root -p111 -e 'SELECT VERSION()' returned '8.0.30-MatrixOne-v1.3.0'; CREATE DATABASE, CREATE TABLE, INSERT, SELECT all returned correct results.
- Model tokens used
- 397,295
- Exact commit tested
- 7ce783464806
- 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.
{"install_succeeded": true, "launch_succeeded": true, "install_minutes": 29, "errors": [{"msg": "Go…
exec
/bin/sh -lc 'pkill -f mo-service 2>/dev/null; sleep 1; echo "server stopped"' in /work/repo
exited 143 in 0ms:
exec
/bin/sh -lc "cat << 'ARGUSIC_END'
ARGUSIC_END" in /work/repo
succeeded in 0ms:
2026-10-04T22:49:04.285150Z ERROR codex_core::session: failed to record rollout items: thread 01a10…
tokens used
397,295
Let me produce the 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 3 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 Apache-2.0, as reported by its host.
What did not, or is not known
- Took 29 minutes to install, slower than the median of the 24 comparable projects Argusic has measured.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 25 agents projects Argusic has installed and timed, matrixone was the 24th fastest to reach a running state, and 15 of 25 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)
agentsai-nativecloud-nativedatabasedistributed-databasedistributed-systemsfulltext-supportgit-for-datagohtaphyperconvergedmemorymysql-compatibleolapone-size-fits-allsqlvector-database
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/matrixone)Questions
- Does matrixone run?
- Yes. matrixone runs. Argusic installed and launched it on a clean machine in 29 minutes, hitting 3 errors on the way, and recorded the session.
- How did Argusic test matrixone?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 7ce783464806. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test matrixone?
- The run that produced this verdict cost $0.53: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does matrixone 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 matrixone need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing matrixone?
- 3 things broke in the recorded run, and 3 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does matrixone compare with the alternatives?
- Of the 25 agents projects Argusic has installed and timed, matrixone was the 24th fastest to reach a running state, and 15 of 25 reached one at all.
- Where is the evidence for matrixone?
- 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.