hivepaas
Self hosted PaaS solution
Runssource: GitHubhomepageGoApache-2.0commit f7185c311719
Go, Apache-2.0 licensed. The project labels itself: automation, cloud, cloud infrastructure, deployment, deployment automation, devops, devops tools and docker.
hivepaas runs. An Argusic agent installed it in 30 minutes and hit 1 error and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Go 1.27.2 toolchain installed, all 170+ dependency packages resolved, hivepaas binary built successfully, full test suite passes (exit 0) with no failures
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.
- lz4 and zstd CLI binaries missing from PATH, causing 36 compress/decompress tests to fail5 minutes
- Install time
- 30 minutes
- Cold machine to finish
- 12 minutes
- Errors hit and fixed
- 1 hit, 1 fixed with no human help
- How the result was proved
- go test -count=1 ./... exited 0 with all packages ok; 36 compress/decompress subtest cases all PASS after installing lz4 and zstd
- Model tokens used
- 75,729
- Exact commit tested
- f7185c311719
- 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.
The binary loads its full dependency injection tree. It can't start serving because PostgreSQL and … Let me compile the complete summary of what was done and observed. **Build succeeded** — `make build` produced a 147MB `hivepaas` binary at `/work/repo/hivepaas`. **All 170+ test packages pass** — `go test -count=1 ./...` exits 0 with every package reporting `ok… **The only issue found and fixed:** `lz4` and `zstd` CLI tools missing from the runtime environment… tokens used 75,729 The binary loads its full dependency injection tree. It can't start serving because PostgreSQL and … Let me compile the complete summary of what was done and observed. **Build succeeded** — `make build` produced a 147MB `hivepaas` binary at `/work/repo/hivepaas`. **All 170+ test packages pass** — `go test -count=1 ./...` exits 0 with every package reporting `ok… **The only issue found and fixed:** `lz4` and `zstd` CLI tools missing from the runtime environment…
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 30 minutes.
- Recovered from all 1 error 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)
automationcloudcloud-infrastructuredeploymentdeployment-automationdevopsdevops-toolsdockerdocker-composedocker-containerdocker-registrydocker-swarmfree-softwaregithubgitopsgolangherokupaasself-hostedself-hosting
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/hivepaas)Questions
- Does hivepaas run?
- Yes. hivepaas runs. Argusic installed and launched it on a clean machine in 30 minutes, hitting 1 error on the way, and recorded the session.
- How did Argusic test hivepaas?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit f7185c311719. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test hivepaas?
- The run that produced this verdict cost $0.15: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does hivepaas take to install?
- 30 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 hivepaas need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing hivepaas?
- 1 thing broke in the recorded run, and 1 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for hivepaas?
- 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.