para
Multitenant backend server for building web and mobile apps rapidly. The backend for busy developers. (self-hosted or hosted)
Runssource: GitHubhomepageJavaApache-2.0commit dc9522c9bd2b
Java, Apache-2.0 licensed. The project labels itself: api, api server, baas, back end, backend, backend api, backend as a service and backend server.
para runs. An Argusic agent installed it in 0.5 minutes and hit 2 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Para 1.55.4-SNAPSHOT builds from source, starts an embedded Jetty server on port 8080 responding HTTP 200, and passes all 172 unit tests and 15/15 end-to-end REST API integration tests with Lucene search and H2 persistence via MockDAO.
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.
- No Java or Maven installed in container0.5 minutes
- Fatjar without lucene profile uses MockSearch which throws UnsupportedOperationException0.2 minutes
- Install time
- under a minute
- Cold machine to finish
- 19 minutes
- Errors hit and fixed
- 2 hit, 2 fixed with no human help
- How the result was proved
- mvn test -pl para-server: 172 passed, 0 failed; curl -s -o /dev/null -w '%{http_code}' http://localhost:8080/ returned 200; mvn verify showed 172 unit + 17 integration tests passing (1 flaky IT failed intermittently)
- Model tokens used
- 489,076
- Exact commit tested
- dc9522c9bd2b
- 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 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. Installed Java 21 (Temurin) and Maven 3.9.9 to `/tmp` (no package manager / root access availabl… 2. Built the project: `mvn install -DskipTests -DskipITs` — all 3 modules (para-core, para-client, … 3. Built the fat JAR: `mvn package -Pfatjar,lucene -DskipTests -DskipITs` — produced `para-1.55.4-S… 4. Ran unit tests: `mvn test -pl para-server` — **172 passed, 0 failed, 0 errors** 5. Ran integration tests: `mvn verify -pl para-server` — 172 unit tests + 1 ConcurrentParaClientIT … 6. Started the server with the fat JAR — it initialized `MockDAO`, `LuceneSearch`, `CaffeineCache`,… 7. Hit `http://localhost:8080/` — returned **HTTP 200** (the Para welcome page HTML) 8. Hit the REST API with SigV4 — the Java `ParaClient` integration tests exercise the full REST API… **Errors encountered:** - No Java or Maven in container — fixed by downloading and extracting JDK 21 + Maven 3.9.9 to `/tmp… - Fatjar without `lucene` profile caused `MockSearch.index()` to throw `UnsupportedOperationExcepti… - `disown` not available in `sh` — used `setsid` to detach background server process (negligible)
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 0.5 minutes, faster than the median of the 61 comparable projects Argusic has measured.
- Recovered from all 2 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
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 62 api projects Argusic has installed and timed, para was the 10th fastest to reach a running state, and 39 of 62 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.
- A quick evaluation: it was running 0.5 minutes after the clone.
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)
apiapi-serverbaasback-endbackendbackend-apibackend-as-a-servicebackend-serverbackend-servicejavajson-apimodularpararapid-prototypingrest-apisearch-engineself-hostedserverlessstandalone-server
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/para)Questions
- Does para run?
- Yes. para runs. Argusic installed and launched it on a clean machine in 1 minutes, hitting 2 errors on the way, and recorded the session.
- How did Argusic test para?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit dc9522c9bd2b. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test para?
- The run that produced this verdict cost $0.06: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does para take to install?
- 0.5 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 para need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing para?
- 2 things broke in the recorded run, and 2 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does para compare with the alternatives?
- Of the 62 api projects Argusic has installed and timed, para was the 10th fastest to reach a running state, and 39 of 62 reached one at all.
- Where is the evidence for para?
- 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.