prest
PostgreSQL ➕ REST, low-code, simplify and accelerate development, ⚡ instant, realtime, high-performance on any Postgres application, existing or new, MCP server
Runs with mockssource: GitHubhomepageGoMITcommit 9070bda7e9ab
Go, MIT licensed. The project labels itself: api, baas, backend, crud, database, docker, golang and instant api.
prest runs, with stand-ins for the services it depends on. An Argusic agent installed it in 17 minutes and hit 4 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
prestd compiles, all unit tests pass, and the app runs serving REST endpoints on a live PostgreSQL database
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.
- docker not available for integration test stack7 minutes
- Go not installed in container2 minutes
- Missing ICU/SSL runtime libs for embedded postgres2 minutes
- gcc missing for -race flag in unit tests1 minute
- Install time
- 17 minutes
- Cold machine to finish
- 21 minutes
- Errors hit and fixed
- 4 hit, 4 fixed with no human help
- Model tokens used
- 79,619
- Exact commit tested
- 9070bda7e9ab
- Container image
- sha256:4c3d41857be3
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.
- How the result was proved
- runs before 2026-09-07 did not record the command used to check the result
- 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
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
succeeded in 0ms: waiting for server to shut down.... done server stopped Let me compute total time elapsed: exec /bin/sh -lc 'date +%s' in /work/repo succeeded in 0ms: 1788504972 ~17 minutes elapsed. Let me compile the final result: tokens used 79,619 ~17 minutes elapsed. Let me compile the final 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 17 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.
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.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
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 | 1/3 | Runs with mocks | 92.00 | 0.10 |
Topics (from GitHub)
apibaasbackendcruddatabasedockergolanginstant-apijwtlow-codemcpmicroservicemodel-context-protocolopenapipostgrespostgresqlrest-apiself-hostedsqltimescaledb
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/prest)Questions
- Does prest run?
- prest runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 17 minutes, hitting 4 errors on the way, and recorded the session.
- How did Argusic test prest?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 9070bda7e9ab. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test prest?
- The run that produced this verdict cost $0.10: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does prest take to install?
- 17 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 prest need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing prest?
- 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 prest?
- The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.