alchemy_cms
Alchemy is the Open Source Rails CMS framework for the component based web that can be used as classic server side rendered or headless CMS.
Runssource: GitHubhomepageRubyBSD-3-Clausecommit a58097e6abac
Ruby, BSD-3-Clause licensed. The project labels itself: admin, alchemy cms, cms, content management system, rails, rails engine and ruby.
alchemy_cms runs. An Argusic agent installed it in 62 minutes and hit 5 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
The AlchemyCMS Rails engine installs and builds in this container, its full RSpec suite (4222 examples, 0 failures) and JS suite (767 tests) pass, and the dev server serves the site root and admin dashboard with HTTP 200.
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 60 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.
- No Ruby, Docker, pnpm, and only too-old Node 18 present in container38 minutes
- Ruby core extensions (psych/zlib/fiddle) failed to build: missing libyaml/zlib/libffi headers/libs and broken extension hdrdir resolution15 minutes
- Local openssl extension failed to recompile (ractor header mismatch) during make install of the first build tree8 minutes
- sqlite3/ruby-vips native gems initially had missing shared libraries4 minutes
- Development server returned HTTP 500 on first boot because dev DB was empty2 minutes
- Install time
- 62 minutes
- Cold machine to finish
- 69 minutes
- Errors hit and fixed
- 5 hit, 5 fixed with no human help
- How the result was proved
- pnpm run test exited 0 (62 files, 767 tests passed); bundle exec rspec exited 0 (4222 examples, 0 failures); curl -s -o /dev/null -w %{http_code} localhost:3000/ returned 200 and curl -L localhost:3000/admin returned 200 after a 301; server process stayed up
- Model tokens used
- 5,992,405
- Exact commit tested
- a58097e6abac
- 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.
tokens used 5,992,405 I have completed the mission. Here is my report. **What I observed (all verified with my own commands):** - The container had **no Ruby, no Docker, no pnpm, and only Node 18** — none of the project's requi… - I built **Ruby 4.0.5 from source** (`~/opt/ruby/bin/ruby` → `ruby 4.0.5 ... +PRISM`), installed *… - `bundle install` → "187 gems now installed"; `sqlite3 2.9.6` and `vips 2.3.0` load. - `bundle exec rake alchemy:spec:prepare` and `db:prepare` completed (SQLite test+dev DBs migrated,… - **JavaScript suite:** `pnpm run test` → `Test Files 62 passed (62), Tests 767 passed (767)`. - **RSpec suite:** `4222 examples, 0 failures`, line coverage 95.07%. - Frontend builds succeeded: `build:js`, `build:admin`, `build:css` all exited 0 and produced `app/… - **App launched:** `bin/rails server -p 3000` stayed up; `curl localhost:3000/` → HTTP 200, `<titl…
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 5 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 BSD-3-Clause, as reported by its host.
- Measured 2 times, so the result is not a one-off.
What did not, or is not known
- Took 62 minutes to install, slower than the median of the 9 comparable projects Argusic has measured.
Of the 10 admin projects Argusic has installed and timed, alchemy_cms was the 10th fastest to reach a running state, and 8 of 10 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 by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 2/3 | Did not run | 20.00 | 0.05 | |
| Argusic Runner | 1/3 | Runs | 100.00 | 1.70 |
Topics (from GitHub)
adminalchemy-cmscmscontent-management-systemrailsrails-engineruby
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/alchemy-cms)Questions
- Does alchemy_cms run?
- Yes. alchemy_cms runs. Argusic installed and launched it on a clean machine in 62 minutes, hitting 5 errors on the way, and recorded the session.
- How did Argusic test alchemy_cms?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit a58097e6abac. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test alchemy_cms?
- The run that produced this verdict cost $1.70: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does alchemy_cms take to install?
- 62 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 alchemy_cms need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing alchemy_cms?
- 5 things broke in the recorded run, and 5 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does alchemy_cms compare with the alternatives?
- Of the 10 admin projects Argusic has installed and timed, alchemy_cms was the 10th fastest to reach a running state, and 8 of 10 reached one at all.
- Where is the evidence for alchemy_cms?
- 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.