pezzo

🕹️ Open-source, developer-first LLMOps platform designed to streamline prompt design, version management, instant delivery, collaboration, troubleshooting, observability and more.

Runssource: GitHubhomepageTypeScriptApache-2.0commit 0787e3c037ad

TypeScript, Apache-2.0 licensed. The project labels itself: ai, devtools, gpt 3, gpt 4, hacktoberfest, javascript, langchain and llm.

pezzo runs. An Argusic agent installed it in 19 minutes and hit no errors on a clean machine with no GPU, and the whole session was recorded.

Pezzo server (v0.8.0) is running on port 3000 with GraphQL and Swagger endpoints, all 22 Prisma migrations are applied to PostgreSQL 16.4, ClickHouse 24.8.14.39 with knex migrations is operational, Redis 7.2.3 answers PONG, and the console front-end builds and serves on port 4200.

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

verdict
Runs
Argusic Score
96 / 100
cost of the verifying run
$0.28 (measured)
recorded runs
2
last tested
stars
3,284
forks
279
open issues
54
watchers
29
size
27 MB
created
last push

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
19 minutes
Cold machine to finish
20 minutes
Errors hit and fixed
0 hit, 0 fixed with no human help
How the result was proved
curl http://127.0.0.1:3000/api/healthz returned {"status":"OK","version":"0.8.0"}
Model tokens used
1,321,537
Exact commit tested
0787e3c037ad
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 1, 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.

ClickHouse: 24.8.14.39
Redis: PONG
Postgres:
Elapsed: 1159 seconds
exec
/bin/sh -lc 'LD_LIBRARY_PATH=/tmp/pg/lib /tmp/pg/install/bin/psql -h 127.0.0.1 -p 5433 -U postgres …
 succeeded in 0ms:
 PostgreSQL 16.4 on x86_64-pc-linux-gnu, compiled by gcc (Ubuntu 13.3.0-6ubuntu2~24.04.1) 13.3.0, 6…
All verifications pass. Here is the final report:
tokens used
1,321,537
All verifications pass. Here is the final report:

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.
  • Nothing broke on the way: zero errors between clone and running.
  • Ran without a GPU, so it does not need one to start.
  • Licensed Apache-2.0, as reported by its host.
  • Measured 2 times, so the result is not a one-off.

What did not, or is not known

  • Took 19 minutes to install, slower than the median of the 234 comparable projects Argusic has measured.

Of the 235 ai projects Argusic has installed and timed, pezzo was the 198th fastest to reach a running state, and 166 of 235 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.
  • 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

tested byattemptoutcomescorecost USDwhen
Argusic Runner2/3Runs100.000.28
Argusic Runner1/3Runs with mocks92.000.10

Topics (from GitHub)

aidevtoolsgpt-3gpt-4hacktoberfestjavascriptlangchainllmllmopsmonitoringnestjsnodejsobservabilityopenaiplatformpromptprompt-engineeringprompt-managementpythontypescript

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/pezzo.svg)](https://argusic.com/subject/pezzo)

Questions

Does pezzo run?
Yes. pezzo runs. Argusic installed and launched it on a clean machine in 19 minutes, hitting 0 errors on the way, and recorded the session.
How did Argusic test pezzo?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 0787e3c037ad. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test pezzo?
The run that produced this verdict cost $0.28: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does pezzo take to install?
19 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 pezzo need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing pezzo?
Nothing did, in the recorded run: zero errors between clone and running.
How does pezzo compare with the alternatives?
Of the 235 ai projects Argusic has installed and timed, pezzo was the 198th fastest to reach a running state, and 166 of 235 reached one at all.
Where is the evidence for pezzo?
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.

Discussion