totum-mit
Small-code database for non-programmers. Universal UI, simple-code logic, automatic actions, access rules, logging, API and more. Quickly create a complex internal apps using the database as an interface.
Runssource: GitHubhomepagePHPMITarchived upstreamcommit 45980e25653d
PHP, MIT licensed. The project labels itself: crm platform, database, erp, erp framework, internal apps, low code, low code development platform and php.
totum-mit runs. An Argusic agent installed it in 11 minutes and hit 6 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Totum is installed and running: FrankenPHP serves the Totum web app on port 8080, returning HTTP 302 redirect to /Auth/Login for unauthenticated requests, with the CLI managing a 'main' schema backed by PostgreSQL 16 containing 59 tables and 4 default users (admin, cron, service, anonym).
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 60 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.
- PostgreSQL not installed3 minutes
- PHP not installed in container2 minutes
- Composer not installed1 minute
- Missing ext-soap and ext-xsl in static PHP1 minute
- CLI.totum.php.ini missing1 minute
- FrankenPHP php-server needs Host header routing1 minute
- Install time
- 11 minutes
- Cold machine to finish
- 12 minutes
- Errors hit and fixed
- 6 hit, 6 fixed with no human help
- How the result was proved
- curl -s -w '%{http_code}' -H 'Host: localhost' http://127.0.0.1:8080/ returned 302; follow with curl -sL -H 'Host: localhost' http://127.0.0.1:8080/totum returned 200 with login page HTML; php bin/totum schemas-list returned 'main'; psql -d totum_main -c 'SELECT count(*) FROM main.tables' returned 59; psql -d totum_main -c 'SELECT id, login FROM main.users' returned 4 rows
- Model tokens used
- 410,891
- Exact commit tested
- 45980e25653d
- 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. **PHP not found** - Installed static PHP 8.3.4 via FrankenPHP binary (contains pgsql, pdo_pgsql,…
2. **Composer not found** - Downloaded and installed via FrankenPHP's PHP
3. **PostgreSQL not found** - Downloaded and initialized static PostgreSQL 16.15.0 binaries; config…
4. **Missing ext-soap and ext-xsl** - Ignored platform requirements during `composer install` since…
5. **CLI.totum.php.ini missing** - Created minimal ini file with memory_limit and time limit settin…
6. **FrankenPHP php-server requires Host header** - Used `-H "Host: localhost"` to route to the cor…
7. **Database schema needed** - Created `totum_main` database and `main` schema; installed via `bin…
**Verification results:**
- Web server: `curl -s -w '%{http_code}' -H 'Host: localhost' http://127.0.0.1:8080/` returns 302 r…
- Followed redirect: `curl -sL -H 'Host: localhost' http://127.0.0.1:8080/totum` returns 200 with t…
- CLI: `php bin/totum schemas-list` returns `main`
- Database: `psql -d totum_main -c "SELECT count(*) FROM main.tables"` returns 59, `SELECT id, logi…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 11 minutes.
- Recovered from all 6 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 MIT, 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 by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 2/3 | Did not run | 20.00 | 0.00 | |
| Argusic Runner | 1/3 | Runs | 100.00 | 0.17 |
Topics (from GitHub)
crm-platformdatabaseerperp-frameworkinternal-appslow-codelow-code-development-platformphppostgrespostgresqlproductivitysmall-code
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/totum-mit)Questions
- Does totum-mit run?
- Yes. totum-mit runs. Argusic installed and launched it on a clean machine in 11 minutes, hitting 6 errors on the way, and recorded the session.
- How did Argusic test totum-mit?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 45980e25653d. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test totum-mit?
- The run that produced this verdict cost $0.17: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does totum-mit take to install?
- 11 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 totum-mit need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing totum-mit?
- 6 things broke in the recorded run, and 6 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for totum-mit?
- 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.