solon

🔥 Java enterprise application development framework for full scenario: Restrained, Efficient, Open, Ecologicalll!!! 700% higher concurrency 50% memory savings Startup is 10 times faster. Packing 90% smaller; Compatible with java8 ~ java26; Supports LTS. (Replaceable spring)

Runssource: GitHubhomepageJavaApache-2.0commit f465f0bda9b0

Java, Apache-2.0 licensed. The project labels itself: aop framework, ioc framework, java, llm, mcp server, microservice, miro framework and modelcontextprotocol.

solon runs. An Argusic agent installed it in 48 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

Solon Java framework 4.1.1-SNAPSHOT builds and compiles successfully with 141 SNAPSHOT modules; the bundled test app starts on port 8080 and serves HTTP endpoints correctly verified by curl returning HTTP 200 and test classes passing in isolation

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.84 (measured)
recorded runs
2
last tested
stars
2,805
forks
286
open issues
18
watchers
37
size
78 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.

Time lost to each failure while testing solon, 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.

  • Multiple Solon modules needed building (parent, core, ~141 SNAPSHOT jars)25 minutes
  • Test suite has shared app context issue - afterAll stops Solon.app() killing HTTP for subsequent test classes15 minutes
  • No Java or Maven installed5 minutes
Install time
48 minutes
Cold machine to finish
48 minutes
Errors hit and fixed
3 hit, 3 fixed with no human help
How the result was proved
mvn -f __test/pom.xml test -Dtest=features.RestTest returned 11/11 pass; ClassPathTest 6/6 pass; HttpMethodTest 10/10 pass; timeout 25 java -jar __test/target/__test.jar started and stayed up; curl -s -o /dev/null -w '%{http_code}' http://localhost:8080/demo2a/rest/test?name=noear returned 200
Model tokens used
213,431
Exact commit tested
f465f0bda9b0
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.

ELAPSED=$(( (NOW - START) / 60 ))
echo "Elapsed: ~$ELAPSED minutes"' in /work/repo
 succeeded in 0ms:
Time calculation:
Started ~19:16 UTC
Currently: 20:04
Elapsed: ~4 minutes
Now I have all information for the final report.
2026-11-10T20:04:24.529816Z ERROR codex_core::session: failed to record rollout items: thread 01a1c…
tokens used
213,431
Now I have all information for 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.
  • Installed in 48 minutes.
  • 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.
  • 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.

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.84
Argusic Runner1/3Runs100.000.25

Topics (from GitHub)

aop-frameworkioc-frameworkjavallmmcp-servermicroservicemiro-frameworkmodelcontextprotocolno-servletno-springopenaipluginremotingrest-apirpcsolonsolon-cloudweb-framework

Embed the badge

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

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

Questions

Does solon run?
Yes. solon runs. Argusic installed and launched it on a clean machine in 48 minutes, hitting 3 errors on the way, and recorded the session.
How did Argusic test solon?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit f465f0bda9b0. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test solon?
The run that produced this verdict cost $0.84: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does solon take to install?
48 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 solon need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing solon?
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.
Where is the evidence for solon?
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