diboot
写的更少, 性能更好 -> 为开发人员打造的低代码开发框架，基础框架可免写90%的SQL，同时具备极强的零代码模型表单页面流程的设计能力和代码生成能力，可在pro-code、low-code、no-code之间自由选择灵活切换，全方位赋能开发。
Runssource: GitHubhomepageJavaApache-2.0commit cd211a2dcc06
Java, Apache-2.0 licensed. The project labels itself: flowable, low code, low code framework, mybatis, mybatis plus, spring, spring boot and spring cloud.
diboot runs. An Argusic agent installed it in 38 minutes and hit 7 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Diboot rest-api-example Spring Boot app compiled, packaged and runs with local MariaDB database, responding HTTP 200 on /api/ endpoint with 25 auto-created tables
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 MySQL-compatible database available8 minutes
- MariaDB process died when parent shell exited5 minutes
- mysql-connector-python default collation utf8mb4_0900_ai_ci not supported by MariaDB 11.43 minutes
- Root user auth failed via TCP on fresh MariaDB install due to unix_socket auth plugin3 minutes
- No JDK pre-installed in container2 minutes
- No Maven pre-installed in container2 minutes
- Install time
- 38 minutes
- Cold machine to finish
- 38 minutes
- Errors hit and fixed
- 7 hit, 7 fixed with no human help
- How the result was proved
- curl -s -o /dev/null -w '%{http_code}' http://127.0.0.1:8080/api/ returned 200; app log shows 'Started DemoStartupApplication' and 'HikariPool-1 - Start completed'; 25 database tables created automatically
- Model tokens used
- 468,986
- Exact commit tested
- cd211a2dcc06
- 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.
2026-10-06T19:54:25.389Z DEBUG 3959 --- [ main] o.m.s.mapper.ClassPathMapperScanner … 2026-10-06T19:54:25.389Z DEBUG 3959 --- [ main] o.m.s.mapper.ClassPathMapperScanner … This final end-to-end test confirms everything works. Let me compile the final result exec /bin/sh -lc 'kill 3902 3959 3763 3764 2>/dev/null; true echo "Cleaned up processes"' in /work/repo succeeded in 0ms: Cleaned up processes Now I have all the data needed for the final report. tokens used 468,986 Now I have all the data needed 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 38 minutes.
- Recovered from all 7 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.
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
Topics (from GitHub)
flowablelow-codelow-code-frameworkmybatismybatis-plusspringspring-bootspring-cloudspringbootvue
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/diboot)Questions
- Does diboot run?
- Yes. diboot runs. Argusic installed and launched it on a clean machine in 38 minutes, hitting 7 errors on the way, and recorded the session.
- How did Argusic test diboot?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit cd211a2dcc06. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test diboot?
- The run that produced this verdict cost $0.19: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does diboot take to install?
- 38 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 diboot need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing diboot?
- 7 things broke in the recorded run, and 7 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for diboot?
- 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.