Does app-platform run?

app-platform runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 64 minutes, hitting 5 errors on the way, and recorded the session.

How did Argusic test app-platform?

On a fresh, disposable machine, with every command recorded and the repository pinned at commit dd242b21cb13. One attempt is recorded, and the full method is on the methodology page.

What did it cost to test app-platform?

The run that produced this verdict cost $0.18: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.

How long does app-platform take to install?

64 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 app-platform need a GPU?

Not to start. Argusic reached a running state on a machine with no GPU.

What goes wrong when installing app-platform?

5 things broke in the recorded run, and 5 were fixed without human help. Each one, and the time it cost, is listed on this page.

Where is the evidence for app-platform?

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.

app-platform

AppPlatform 是一个前沿的大模型应用工程，旨在通过集成的声明式编程和低代码配置工具，简化和优化大模型的训练与推理应用的开发过程。本工程为软件工程师和产品经理提供一个强大的、可扩展的环境，以支持从概念到部署的全流程 AI 应用开发。

Runs with mockssource: GitHub homepageJavaMITcommit dd242b21cb13

Java, MIT licensed. The project labels itself: agent, agentic ai, agentic workflow, ai, java and low code.

app-platform runs, with stand-ins for the services it depends on. An Argusic agent installed it in 64 minutes and hit 5 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

The Java backend builds and all 1752 unit tests pass with 0 failures. The agent-flow and frontend Node projects install and build to production bundles without errors. The frontend static build serves on localhost:3310 and returns HTTP 200.
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

verdict: Runs with mocks
Argusic Score: 92 / 100
cost of the verifying run: $0.18 (measured)
recorded runs: 1
last tested: 2026-10-07
stars: 1,458
forks: 233
open issues: 91
watchers: 150
size: 29 MB
created: 2025-03-31
last push: 2026-09-29

Subject data from GitHub, linked at the top of this page, refreshed 2026-10-07. 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 app-platform, 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.

Maven not pre-installed in container1 minute
Java JDK 17 not pre-installed in container0.5 minutes
Frontend dev server (webpack serve) failed due to missing react-refresh peer dependency0.3 minutes
Frontend npm install failed due to @types/react-dom@16 peer dep incompatible with React 18 types0.1 minutes
Docker and docker-compose not available in container, blocking docker/deploy.sh deployment path

Install time: 64 minutes
Cold machine to finish: 65 minutes
Errors hit and fixed: 5 hit, 5 fixed with no human help
How the result was proved: mvn test passed: 136 modules, 1752 tests, 0 failures, 0 errors, 72 skipped; mvn install -DskipTests built all 136 modules SUCCESS; frontend built to build/ via webpack; curl -s -o /dev/null -w %{http_code} http://localhost:3310/ returned 200
Model tokens used: 340,805
Exact commit tested: dd242b21cb13
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.

/bin/sh -lc 'echo "Start time: 19:18"
echo "End time: $(date +%H:%M)"
# Let'"'s compute approximate elapsed minutes
echo \"Approx elapsed: about 63 minutes\"" in /work/repo
 succeeded in 0ms:
Start time: 19:18
End time: 20:22
Approx elapsed: about 63 minutes
All checks pass. Here is the comprehensive report.
tokens used
340,805
All checks pass. Here is the comprehensive 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

Recovered from all 5 errors without a human stepping in, which says the failures are documented well enough to solve.
Licensed MIT, 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.
Took 64 minutes to install, slower than the median of the 77 comparable projects Argusic has measured.
Measured once so far. A single attempt shows it can run, not that it runs reliably.

Of the 78 agent projects Argusic has installed and timed, app-platform was the 78th fastest to reach a running state, and 53 of 78 reached one at all.

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.18	2026-10-07 20:23 UTC

Topics (from GitHub)

agent agentic-ai agentic-workflow ai java low-code

Embed the badge

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

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

Questions

Does app-platform run?: app-platform runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 64 minutes, hitting 5 errors on the way, and recorded the session.
How did Argusic test app-platform?: On a fresh, disposable machine, with every command recorded and the repository pinned at commit dd242b21cb13. One attempt is recorded, and the full method is on the methodology page.
What did it cost to test app-platform?: The run that produced this verdict cost $0.18: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does app-platform take to install?: 64 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 app-platform need a GPU?: Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing app-platform?: 5 things broke in the recorded run, and 5 were fixed without human help. Each one, and the time it cost, is listed on this page.
How does app-platform compare with the alternatives?: Of the 78 agent projects Argusic has installed and timed, app-platform was the 78th fastest to reach a running state, and 53 of 78 reached one at all.
Where is the evidence for app-platform?: 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.