spree
Open Source Platform for DTC, B2B Commerce, Marketplaces & Omnichannel. REST APIs, TypeScript SDKs, and production-ready Next.js storefront. Self-host it. Own your data. No vendor lock-in. Zero platform fees.
Runssource: GitHubhomepageRubyBSD-3-Clausecommit 8bf7b0721985
Ruby, BSD-3-Clause licensed. The project labels itself: b2b commerce, e commerce, ecommerce, ecommerce api, ecommerce framework, ecommerce platform, headless and headless commerce.
spree 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 11 TypeScript/JavaScript SDK, CLI, dashboard, and scaffolding packages install, build, and pass their test suites (1196 tests, 0 failures). The Rails backend requires Ruby 3.2+, PostgreSQL, and Docker which are not available in this container.
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
- 6 minutes
- Errors hit and fixed
- 0 hit, 0 fixed with no human help
- How the result was proved
- pnpm install completed in 11s; turbo build --filter=./packages/sdk-core --filter=./packages/sdk --filter=./packages/admin-sdk --filter=./packages/seller-sdk --filter=./packages/cli all succeeded; vitest run on @spree/sdk (192 pass), @spree/admin-sdk (256 pass), @spree/seller-sdk (12 pass), @spree/cli (210 pass), @spree/dashboard-core (229 pass), @spree/dashboard (160 pass), create-spree-app (96 pass), @spree/docs (41 pass) = 1196 tests, 0 failures; CLI --version returned 3.1.0
- Model tokens used
- 52,496
- Exact commit tested
- 8bf7b0721985
- 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.
node packages/cli/dist/index.js --version 2>&1' in /work/repo
succeeded in 0ms:
3.1.0
All tests passed. Let me compile the final report.
**Install summary:** The repository works as a standard npm/pnpm workspace. Had to work around the …
The Ruby backend (Rails, PostgreSQL) and Docker-based services can't run in this container — no Rub…
exec
/bin/sh -lc "echo '{\"install_succeeded\": true, \"launch_succeeded\": true, \"install_minutes\": 2…
succeeded in 0ms:
{"install_succeeded": true, "launch_succeeded": true, "install_minutes": 2, "errors": [], "test_dep…
tokens used
52,496Replay 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 BSD-3-Clause, 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.
- 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)
b2b-commercee-commerceecommerceecommerce-apiecommerce-frameworkecommerce-platformheadlessheadless-commerceheadless-ecommercemarketplacemulti-tenantmulti-vendormulti-vendor-ecommerceopen-sourcespree-commerce
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/spree)Questions
- Does spree run?
- Yes. spree 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 spree?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 8bf7b0721985. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test spree?
- 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 spree 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 spree need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing spree?
- Nothing did, in the recorded run: zero errors between clone and running.
- Where is the evidence for spree?
- 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.