Yes. portabase runs. Argusic installed and launched it on a clean machine in 22 minutes, hitting 7 errors on the way, and recorded the session.

How did Argusic test portabase?

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

What did it cost to test portabase?

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

How long does portabase take to install?

22 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 portabase need a GPU?

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

What goes wrong when installing portabase?

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 portabase?

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.

portabase

Portabase - Database backup & restore tool for PostgreSQL, MySQL, MsSQL, MariaDB, Firebird SQL, SQLite, MongoDB, Redis and Docker Volume

Runssource: GitHub homepageTypeScriptApache-2.0commit 6cb2afdbc09b

TypeScript, Apache-2.0 licensed. The project labels itself: backup, backup tool, database, devops, docker, docker backup, docker volumes and firebirdsql.

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

Portabase v1.30.2 dev server is running on port 8887, connected to PostgreSQL 16.15 on port 5433, with 29 database tables, default organization and super admin created, all init functions completed, all 5 tested routes return 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 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.22 (measured)
recorded runs: 1
last tested: 2026-10-05
stars: 1,815
forks: 126
open issues: 40
watchers: 8
size: 36 MB
created: 2024-10-19
last push: 2026-09-29

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

PostgreSQL not available in container8 minutes
Node.js 18 too old for Next.js 16 (requires >=20.9.0)3 minutes
pnpm not installed on Node.js 18.19.12 minutes
@tailwindcss/oxide native binding not found (pnpm skips optional deps)2 minutes
Database migrations not applied — tables missing2 minutes
Corrupted CSS cache from earlier failed build caused 500 on page render2 minutes

Install time: 22 minutes
Cold machine to finish: 29 minutes
Errors hit and fixed: 7 hit, 7 fixed with no human help
How the result was proved: curl http://localhost:8887/api/health returned 200 with body {"success":true}; curl on /login, /, /register, /forgot-password each returned 200 with valid HTML; PostgreSQL is accepting connections on port 5433 with 29 migration tables applied; dev server logs show Init Functions completed, default org created, super admin ([email protected]) created, cron jobs started.
Model tokens used: 520,891
Exact commit tested: 6cb2afdbc09b
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.

forgot-password: 200
Now let me compile the final report, computing time precisely:
exec
/bin/sh -lc 'echo "Time check:"; date -u +%s' in /work/repo
 succeeded in 0ms:
Time check:
1791229498
Here is the final report:
2026-10-05T19:45:12.168545Z ERROR codex_core::session: failed to record rollout items: thread 01a10…
tokens used
520,891
Here is 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.
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

Took 22 minutes to install, slower than the median of the 16 comparable projects Argusic has measured.
Measured once so far. A single attempt shows it can run, not that it runs reliably.

Of the 17 backup projects Argusic has installed and timed, portabase was the 13th fastest to reach a running state, and 13 of 17 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.

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	100.00	0.22	2026-10-05 19:45 UTC

Topics (from GitHub)

backup backup-tool database devops docker docker-backup docker-volumes firebirdsql mariadb mongodb mssql-database mysql nextjs postgresql redis selfhosted sqlite-database valkey

Embed the badge

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

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

Questions

Does portabase run?: Yes. portabase runs. Argusic installed and launched it on a clean machine in 22 minutes, hitting 7 errors on the way, and recorded the session.
How did Argusic test portabase?: On a fresh, disposable machine, with every command recorded and the repository pinned at commit 6cb2afdbc09b. One attempt is recorded, and the full method is on the methodology page.
What did it cost to test portabase?: The run that produced this verdict cost $0.22: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does portabase take to install?: 22 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 portabase need a GPU?: Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing portabase?: 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.
How does portabase compare with the alternatives?: Of the 17 backup projects Argusic has installed and timed, portabase was the 13th fastest to reach a running state, and 13 of 17 reached one at all.
Where is the evidence for portabase?: 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.