database-lab-engine
DBLab enables 🖖 database branching and ⚡️ thin cloning for any Postgres database and empowers DB testing in CI/CD. This optimizes database-related costs while improving time-to-market and software quality. Follow to stay updated.
Runssource: GitHubhomepageGoApache-2.0commit 9e97e2f72e32
Go, Apache-2.0 licensed. The project labels itself: branching, ci, ci cd, cicd, cloning, database, database branching and database migration.
database-lab-engine runs. An Argusic agent installed it in 2 minutes and hit no errors on a clean machine with no GPU, and the whole session was recorded.
All 4 Go binaries (dblab-server, dblab, run-ci, rds-refresh) build cleanly, all 56 unit test modules pass, and the CLI binary responds to version and help commands.
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.
- Install time
- 2 minutes
- Cold machine to finish
- 9 minutes
- Errors hit and fixed
- 0 hit, 0 fixed with no human help
- How the result was proved
- make build compiled 4 binaries without errors; go test -race -count=1 ./... passed 56/56 modules; dblab --version returned version string; dblab --help printed command list
- Model tokens used
- 55,571
- Exact commit tested
- 9e97e2f72e32
- 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.
- `dblab` (12.3 MB) — CLI tool - `run-ci` (9.4 MB) — CI checker - `rds-refresh` (11.7 MB) — RDS refresh tool **Tests**: `go test -race -count=1 ./...` — **all 56 test modules passed**, zero failures. **Verification**: - `dblab --version` → `dblab version 9e97e2f72e32d153197bae7f3685d92b10d8a47e-20261002-2219` - `dblab --help` → prints all commands (init, branch, clone, snapshot, config, etc.) - `rds-refresh --help` → prints usage and options - `dblab-server` expects config + Docker/PostgreSQL infrastructure (needs real database to run) - `run-ci` expects a CI checker config file **UI**: The UI (`ui/`) requires Node >=20 and pnpm; the container has Node 18.19.1. I did not attem… **Errors encountered**: None. Clean build, clean tests.
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 2 minutes.
- Nothing broke on the way: zero errors between clone and running.
- 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.
- A quick evaluation: it was running 2 minutes after the clone.
- Following its own README: the documented path worked with nothing to fix.
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)
branchingcici-cdcicdcloningdatabasedatabase-branchingdatabase-migrationdatabase-migrationsdatabase-schemadatabase-schema-evolutionsdatabase-schema-migrationpgsqlpostgrespostgresqlsql
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/database-lab-engine)Questions
- Does database-lab-engine run?
- Yes. database-lab-engine runs. Argusic installed and launched it on a clean machine in 2 minutes, hitting 0 errors on the way, and recorded the session.
- How did Argusic test database-lab-engine?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 9e97e2f72e32. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test database-lab-engine?
- The run that produced this verdict cost $0.03: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does database-lab-engine take to install?
- 2 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 database-lab-engine need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing database-lab-engine?
- Nothing did, in the recorded run: zero errors between clone and running.
- Where is the evidence for database-lab-engine?
- 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.