peekaping
Open Source Uptime Kuma Alternative
Runssource: GitHubhomepageGoMITcommit 742a60d94fda
Go, MIT licensed. The project labels itself: monitor, monitoring, self hosted, selfhosted, telemetry, uptime and uptime monitoring.
peekaping runs. An Argusic agent installed it in 22 minutes and hit 6 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Peekaping API server starts on port 8034 with SQLite, connects to local Redis, and responds HTTP 200 on /api/v1/health. All 16 Go test packages pass. The React web frontend builds without errors.
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 96 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.
- Redis not available6 minutes
- Go compiler not installed5 minutes
- Node.js v18.19.1 is below required v20.18.02 minutes
- Database tables missing (starting server failed on 'no such table: settings')2 minutes
- pnpm not found1 minute
- Config validation failed: missing DB_TYPE, DB_NAME1 minute
- Install time
- 22 minutes
- Cold machine to finish
- 16 minutes
- Errors hit and fixed
- 6 hit, 6 fixed with no human help
- How the result was proved
- curl -s http://localhost:8034/api/v1/health returned 200 with '{"status":"success"}'; go test ./internal/... exited 0, all 16 packages PASS; pnpm build in apps/web completed successfully
- Model tokens used
- 102,670
- Exact commit tested
- 742a60d94fda
- 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 2, 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.
- **Install steps**: Installed Go 1.24.1 (decompressed binary tarball), Node v20.18.0 (decompressed… - **Errors encountered and fixed**: 1. Go not found → installed Go 1.24.1 binary tarball 2. Node v18.19.1 too old → installed Node v20.18.0 binary tarball 3. pnpm not found → npm i -g [email protected] 4. Redis not installed → compiled from source, started as daemon on port 6381 5. Config validation failed on start (DB_TYPE/DB_NAME required) → placed `.env` in `apps/server/`… 6. "no such table: settings" → ran database migration (`go run cmd/bun/main.go db init` then `db … - **No third-party credentials needed**: The SQLite + local Redis stack works fully offline. - **API verified**: `curl http://localhost:8034/api/v1/health` returned HTTP 200 with `{"status":"s… - **Tests**: `go test ./internal/...` — 16 packages, all PASS. - **Web build**: `pnpm build` in `apps/web` — tsc + vite build succeeded.
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 22 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 | Runs | 100.00 | 0.07 | |
| Argusic Runner | 1/3 | Runs with mocks | 92.00 | 0.12 |
Topics (from GitHub)
monitormonitoringself-hostedselfhostedtelemetryuptimeuptime-monitoring
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/peekaping)Questions
- Does peekaping run?
- Yes. peekaping runs. Argusic installed and launched it on a clean machine in 22 minutes, hitting 6 errors on the way, and recorded the session.
- How did Argusic test peekaping?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 742a60d94fda. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test peekaping?
- The run that produced this verdict cost $0.07: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does peekaping 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 peekaping need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing peekaping?
- 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 peekaping?
- 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.