flame
Flame is self-hosted startpage for your server. Easily manage your apps and bookmarks with built-in editors.
Runssource: GitHubTypeScriptMITcommit 3e03c25138df
TypeScript, MIT licensed. The project labels itself: homepage, self hosted and startpage.
flame runs. An Argusic agent installed it in 7 minutes and hit no errors on a clean machine with no GPU, and the whole session was recorded.
Flame server runs on port 5005 serving both the React frontend (HTTP 200) and a complete REST API with apps CRUD, categories CRUD, bookmarks CRUD, config, auth with JWT, themes, weather, and queries endpoints, backed by a SQLite database with migrations.
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
- 7 minutes
- Cold machine to finish
- 10 minutes
- Errors hit and fixed
- 0 hit, 0 fixed with no human help
- How the result was proved
- node test-flame.mjs ran a comprehensive test: GET / returned 200 with React app HTML, POST /api/auth returned 200 with JWT token, GET /api/config returned 200 with config data, POST /api/apps created app (201), GET /api/apps listed apps (200), POST /api/categories created category (201), GET /api/categories listed categories (200), POST /api/bookmarks created bookmark (201), GET /api/bookmarks listed bookmarks (200), PUT /api/config updated config title (200), POST /api/auth with wrong password returned 401, POST /api/auth/validate returned 200, GET /static/js/main.3270a6fa.js returned 200 serving 2.9MB JS bundle
- Model tokens used
- 269,582
- Exact commit tested
- 3e03c25138df
- 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 verdict above comes from a different attempt, so read this as one session and not as the current result. 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.
Validate Token: 200 {"success":true,"data":{"token":{"isValid":true}}}
Create Bookmark: 201 {"success":true,"data":{"icon":"","isPublic":1,"orderId":null,"id":1,"name":"M…
List Bookmarks: 200 {"success":true,"data":[{"id":1,"name":"My Bookmark","url":"https://github.com"…
JS Bundle: 200 2914516 bytes
All endpoints are working perfectly. Let me clean up and generate the final report
exec
/bin/sh -lc 'pkill -f "node server.js" 2>/dev/null; sleep 1; echo "Cleaned up"' in /work/repo
exited 143 in 0ms:
Now let me compile the final result. Everything worked.
tokens used
269,582
Now let me compile the final result. Everything worked.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 7 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 MIT, as reported by its host.
- Measured 3 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.
- A quick evaluation: it was running 7 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)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/flame)Questions
- Does flame run?
- Yes. flame runs. Argusic installed and launched it on a clean machine in 7 minutes, hitting 0 errors on the way, and recorded the session.
- How did Argusic test flame?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 3e03c25138df. 3 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test flame?
- 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 flame take to install?
- 7 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 flame need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing flame?
- Nothing did, in the recorded run: zero errors between clone and running.
- Where is the evidence for flame?
- All 3 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.