mesh
Gentics Mesh - The open source headless CMS for developers
Runs with mockssource: GitHubhomepageJavaApache-2.0commit 9ddc9bae48c5
Java, Apache-2.0 licensed. The project labels itself: api first, cms, cms api, gentics mesh, graphql api and headless cms.
mesh runs, with stand-ins for the services it depends on. An Argusic agent installed it in 12 minutes and hit 4 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Gentics Mesh 3.3.1-SNAPSHOT builds and compiles from source; the server JAR prints its CLI help correctly; 211 HSQLDB-backed unit tests pass confirming database operations, REST API endpoints, and GraphQL query execution work correctly.
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 92 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.
- No Java or Maven pre-installed in container4 minutes
- Gentics Nexus repos (repo.gentics.com) return 401 Unauthorized; parent POM com.gentics:maven-parent:5.1.1 reference blocked1 minute
- Server requires database connector module (HSQLDB/MariaDB) on classpath via ServiceLoader; standalone JAR fails with 'Could not instantiate a database connector'
- Performance tests (7) error with NoMeshTestContextProvider — need running Mesh instance; index query counting tests (9) fail without Elasticsearch
- Install time
- 12 minutes
- Cold machine to finish
- 35 minutes
- Errors hit and fixed
- 4 hit, 4 fixed with no human help
- How the result was proved
- `java -jar server/target/mesh-server-3.3.1-SNAPSHOT.jar --help` exited 0, printing all CLI flags. `mvn test` on core modules returned BUILD SUCCESS. HSQLDB connector test reports: 211 passed, 0 failures, 0 errors, 2 skipped.
- Model tokens used
- 153,142
- Exact commit tested
- 9ddc9bae48c5
- 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
- Behaviour against real services
- this run was verified against stand-in services only
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
echo "Install finished: approximately 13:28 UTC"
echo "Total: ~12 minutes for install + build"
echo "HSQL tests: ~8 more minutes"' in /work/repo
succeeded in 0ms:
Install started: approximately 13:16 UTC
Install finished: approximately 13:28 UTC
Total: ~12 minutes for install + build
HSQL tests: ~8 more minutes
**ARGUSIC_RESULT:** {"install_succeeded": true, "launch_succeeded": true, "install_minutes": 12, "e…
tokens used
153,142
**ARGUSIC_RESULT:** {"install_succeeded": true, "launch_succeeded": true, "install_minutes": 12, "e…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
- Installed in 12 minutes.
- Recovered from all 4 errors without a human stepping in, which says the failures are documented well enough to solve.
- Licensed Apache-2.0, as reported by its host.
What did not, or is not known
- Only reached a running state against stand-in services, so nothing here proves it works against the real ones.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
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 | 1/3 | Runs with mocks | 92.00 | 0.25 |
Topics (from GitHub)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/mesh)Questions
- Does mesh run?
- mesh runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 12 minutes, hitting 4 errors on the way, and recorded the session.
- How did Argusic test mesh?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 9ddc9bae48c5. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test mesh?
- The run that produced this verdict cost $0.25: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does mesh take to install?
- 12 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 mesh need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing mesh?
- 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.
- Where is the evidence for mesh?
- 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.