portabase

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

Runssource: GitHubhomepageTypeScriptApache-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 37.5 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 http://localhost:8887 with PostgreSQL 16.4 database backend, all 87 migrations applied, default organization and super admin created, responding HTTP 200 on /, /login, and /api/config.

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.32 (measured)
recorded runs
2
last tested
stars
1,921
forks
145
open issues
47
watchers
9
size
36 MB
created
last push

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.

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.

  • @tailwindcss/oxide native addon not found (optional dep not auto-installed by pnpm in this env)5 minutes
  • No PostgreSQL database available on the system4 minutes
  • Production build crashed with SIGABRT during page data collection, second attempt OOM killed3 minutes
  • Node.js 18.19.1 is too old (Next.js 16 requires >=20.9.0)2 minutes
  • pnpm not available in PATH, corepack missing1 minute
  • Missing environment configuration (PROJECT_SECRET, DATABASE_URL)1 minute
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
pnpm dev started the Next.js dev server; curl http://localhost:8887/ returned HTTP 200, curl http://localhost:8887/login returned HTTP 200, curl http://localhost:8887/api/config returned HTTP 200. PostgreSQL 16.4 answering queries on port 5433. 87 database migrations applied. Server log shows GET / 200, GET /login 200, GET /api/config 200.
Model tokens used
769,623
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.

/bin/sh -lc 'export PATH=/home/runner/.n/bin:/home/runner/.npm-global/bin:$PATH && cd /work/repo &&…
 succeeded in 0ms:
PG OK: { '?column?': 1 }
PostgreSQL reachable
All verification is complete. Let me compile the final result.
exec
/bin/sh -lc "echo 'ARGUSIC_RESULT:{\"install_succeeded\":true,\"launch_succeeded\":true,\"install_m…
 succeeded in 0ms:
2026-11-13T05:16:40.912070Z ERROR codex_core::session: failed to record rollout items: thread 01a1d…
tokens used
769,623
All verification is complete. Let me compile the final result.

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.
  • Measured 2 times, so the result is not a one-off.

What did not, or is not known

  • Took 37.5 minutes to install, slower than the median of the 47 comparable projects Argusic has measured.

Of the 48 backup projects Argusic has installed and timed, portabase was the 48th fastest to reach a running state, and 32 of 48 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 byattemptoutcomescorecost USDwhen
Argusic Runner2/3Runs100.000.32
Argusic Runner1/3Runs100.000.22

Topics (from GitHub)

backupbackup-tooldatabasedevopsdockerdocker-backupdocker-volumesfirebirdsqlmariadbmongodbmssql-databasemysqlnextjspostgresqlrcloneredisresticselfhostedsqlite-databasevalkey

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 38 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. 2 attempts are 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.32: 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?
37.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 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 48 backup projects Argusic has installed and timed, portabase was the 48th fastest to reach a running state, and 32 of 48 reached one at all.
Where is the evidence for portabase?
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.

Discussion