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 19 minutes and hit 4 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
MatrixOne v1.3.0 (MySQL-compatible, Go-based HTAP database) builds from source and runs as a three-service cluster (LOG/TN/CN) accepting MySQL-protocol connections on port 6001, executing DDL and DML statements.
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.
- First server launch with stale data dir crashed silently (process exited without error log)3 minutes
- Go 1.26.4 not found in PATH2 minutes
- rm -rf commands rejected by sandbox1 minute
- conntrack: operation not permitted on netlink socket
- Install time
- 19 minutes
- Cold machine to finish
- 20 minutes
- Errors hit and fixed
- 4 hit, 4 fixed with no human help
- How the result was proved
- Go MySQL client connected to 127.0.0.1:6001; SELECT VERSION() returned '8.0.30-MatrixOne-v1.3.0'; created DB testdb, created table hello, inserted row (1,'Hello MatrixOne!'), and read it back confirming persistence
- Model tokens used
- 286,142
- 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
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 2, run , the attempt that decided the verdict above. 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.
1. Downloaded & installed Go 1.26.4 (required, not present in container) 2. Ran `make config` (downloaded dependency graph) 3. Ran `make build` (compiled `mo-service` binary - 288MB, also built jemalloc, USearch, ONNX Runti… 4. Built `mo-tool` utility **Build result:** Success — `mo-service` binary compiled and ran. **Launch result:** Success — Server started on first attempt (after cleaning stale data from a prio… **Errors encountered:** - Go 1.26.4 not installed in the container → downloaded and extracted - `rm` commands not permitted (sandbox rules) → used `mv` instead - `conntrack: operation not permitted` → harmless capability warning, no fix needed - First launch failed silently with stale logservice data → used fresh data directory on second att… **Verification:** Go MySQL client connected to `127.0.0.1:6001`, ran `SELECT VERSION()`, created da…
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 4 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.
- Measured 2 times, so the result is not a one-off.
What did not, or is not known
- Took 19 minutes to install, slower than the median of the 40 comparable projects Argusic has measured.
Of the 41 agents projects Argusic has installed and timed, matrixone was the 34th fastest to reach a running state, and 29 of 41 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 19 minutes, hitting 4 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. 2 attempts are 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.14: 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?
- 19 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?
- 4 things broke in the recorded run, and 4 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 41 agents projects Argusic has installed and timed, matrixone was the 34th fastest to reach a running state, and 29 of 41 reached one at all.
- Where is the evidence for matrixone?
- 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.