relivator
🏬 relivator: next.js 15 react 19 ecommerce template ▲ better-auth polar shadcn/ui tailwind drizzle orm typescript ts radix, postgres neon, app router saas commerce ecommerce shop pricing payments dark mode full stack free ⭐ more stars 👉 more features
Runs with mockssource: GitHubhomepageTypeScriptMITcommit a1871b006ab0
TypeScript, MIT licensed. The project labels itself: drizzle orm, e commerce, ecommerce, next auth, nextauthjs, nextjs, nextjs boilerplate and nextjs example.
relivator runs, with stand-ins for the services it depends on. An Argusic agent installed it in 9 minutes and hit 4 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Bun 1.2.12 installed, all 11 bun tests pass, tsc type-check passes with zero errors, dev server serves HTTP 200 on / and /api/auth/get-session, production build compiles but OOM during static page generation due to container memory limit.
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 92 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.
- bun runtime not available in container1 minute
- bun test env.test.ts failed: DATABASE_URL had placeholder 'postgresql://...'1 minute
- next build type error in src/lib/queries/uploads.ts: findMany return type conflicted with UserWithUploads which includes uploads relation1 minute
- next build OOM during static page generation (Generating static pages (0/18) killed by SIGKILL)
- Install time
- 9 minutes
- Cold machine to finish
- 8 minutes
- Errors hit and fixed
- 4 hit, 4 fixed with no human help
- How the result was proved
- bun test ./.tests: 11 pass, 0 fail, 29 expect() calls; curl http://localhost:3000: HTTP 200; curl http://localhost:3000/api/auth/get-session: HTTP 200; tsc --noEmit: exit 0 (clean)
- Model tokens used
- 39,727
- Exact commit tested
- a1871b006ab0
- 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
- Behaviour against real services
- this run was verified against stand-in services only
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.
(pass) Polar Integration > Polar client should be properly configured (pass) Polar Integration > Better-Auth Polar plugin should be configured (pass) Payment API Routes > customer-state API should return customer state for authenticated user … (pass) Payment API Routes > subscriptions API should return user subscriptions 11 pass 0 fail 29 expect() calls Ran 11 tests across 2 files. [12.00ms] Now I have all the data collected. Let me produce the final structured result. tokens used 39,727 Now I have all the data collected. Let me produce the final structured result.
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
- Installed in 9 minutes.
- Recovered from all 4 errors without a human stepping in, which says the failures are documented well enough to solve.
- Licensed MIT, as reported by its host.
- Measured 2 times, so the result is not a one-off.
What did not, or is not known
- Only reached a running state against stand-in services, so nothing here proves it works against the real ones.
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 with mocks | 92.00 | 0.04 | |
| Argusic Runner | 1/3 | Runs with mocks | 92.00 | 0.05 |
Topics (from GitHub)
drizzle-orme-commerceecommercenext-authnextauthjsnextjsnextjs-boilerplatenextjs-examplenextjs-starternextjs-tailwindnextjs-templatenextjs14nextjs15radix-uishadcnshadcn-uistarterstripet3-stacktemplate
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/relivator)Questions
- Does relivator run?
- relivator runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 9 minutes, hitting 4 errors on the way, and recorded the session.
- How did Argusic test relivator?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit a1871b006ab0. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test relivator?
- The run that produced this verdict cost $0.04: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does relivator take to install?
- 9 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 relivator need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing relivator?
- 4 things broke in the recorded run, and 4 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for relivator?
- 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.