utopia

World's first open-source enterprise world model.

Runssource: GitHubRustApache-2.0commit 417b49bc4433

Rust, Apache-2.0 licensed. The project labels itself: agent memory, bitemporal, graphrag, knowledge base, knowledge graph, llm, ontology and pgvector.

utopia runs. An Argusic agent installed it in 23 minutes and hit no errors on a clean machine with no GPU, and the whole session was recorded.

Utopia server 0.1.0 builds from source, starts on port 1516, serves health endpoint, runs database migrations on PostgreSQL 16 with pgvector, and passes the full end-to-end smoke test covering registration, authentication, workspace/knowledge-base creation, document upload with Chinese-language ingestion and search, unauthenticated access rejection, and job queue enqueue

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
2
last tested
stars
9,754
forks
1,046
open issues
43
watchers
398
size
8 MB
created
last push

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.

Install time
23 minutes
Cold machine to finish
17 minutes
Errors hit and fixed
0 hit, 0 fixed with no human help
How the result was proved
bash scripts/smoke.sh passed all 8 steps: health returned 'ok', registration created user, auth/me returned email, workspace CRUD succeeded, document upload/ingestion completed, Chinese search returned hit, unauthenticated request returned 401, login returned token, noop job enqueued successfully
Model tokens used
76,738
Exact commit tested
417b49bc4433
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.

exec
/bin/sh -lc "cat <<'CALC'
Start: ~22:16 UTC
End:   ~22:39 UTC
Delta: ~23 min
CALC" in /work/repo
 succeeded in 0ms:
Start: ~22:16 UTC
End:   ~22:39 UTC
Delta: ~23 min
tokens used
76,738

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 23 minutes.
  • Nothing broke on the way: zero errors between clone and running.
  • 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 it is a reasonable choice for

  • Trying it on a laptop or a small server: it reached a running state without a GPU.
  • Following its own README: the documented path worked with nothing to fix.

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 byattemptoutcomescorecost USDwhen
Argusic Runner2/3Runs100.000.08
Argusic Runner1/3Runs100.000.19

Topics (from GitHub)

agent-memorybitemporalgraphragknowledge-baseknowledge-graphllmontologypgvectorpostgresqlragrustself-hostedsemantic-searchtemporal-knowledge-graphworld-model

Embed the badge

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

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

Questions

Does utopia run?
Yes. utopia runs. Argusic installed and launched it on a clean machine in 23 minutes, hitting 0 errors on the way, and recorded the session.
How did Argusic test utopia?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 417b49bc4433. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test utopia?
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 utopia take to install?
23 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 utopia need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing utopia?
Nothing did, in the recorded run: zero errors between clone and running.
Where is the evidence for utopia?
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.

Discussion