encore

Infrastructure orchestration from local to your cloud

Runssource: GitHubhomepageGoMPL-2.0commit 13dfbf46f262

Go, MPL-2.0 licensed. The project labels itself: aws, backend, cloud, cloud native, database, devops, devops automation and distributed systems.

encore runs. An Argusic agent installed it in 31 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 Encore CLI builds and reports its version, the bundled echo app runs and answers health, echo, pong, and dashboard requests with HTTP 200, the echo end-to-end test passes, and the short Go test suite exits 0 with 70 ok packages.

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

verdict
Runs
Argusic Score
100 / 100
cost of the verifying run
$0.28 (measured)
recorded runs
2
last tested
stars
12,718
forks
659
open issues
153
watchers
65
size
18 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.

Time lost to each failure while testing encore, drawn from the recorded run
Every bar is a failure the agent recorded, with the time it cost. Drawn from this run, not from anywhere else.

What went wrong, in the agent's own words

The agent's own words, worst first, never rewritten into advice.

  • tsparser-encore build failed because protoc, libclang, libLLVM, and C headers were missing8 minutes
  • pkg/clientgen failed because tsparser-encore was not on PATH5 minutes
  • encore run timed out dialing the daemon after a separately started foreground daemon raced on ports and the SQLite management database3 minutes
  • Go and Rust toolchains were absent2 minutes
  • The encore-go checksum file used the asset name linux_x86-64.tar.gz, so checksum verification against encore-go.tar.gz found no file1 minute
Install time
31 minutes
Cold machine to finish
25 minutes
Errors hit and fixed
5 hit, 5 fixed with no human help
How the result was proved
go build ./... exited 0; encore version printed v0.0.0-develop+13dfbf46f2621dc9456458b735cb2a5f0db15e6a; encore run served the echo app; curl returned 200 for /__encore/healthz, /echo.BasicEcho, /echo.Pong, and the dashboard; go test -tags=e2e -run '^TestEndToEndWithApp$' exited 0 with all subtests passing; go test -short -tags=dev_build ./... exited 0 with 70 package-level ok results
Model tokens used
331,152
Exact commit tested
13dfbf46f262
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.

- `go build ./...` exited `0`.
- `encore version` printed `v0.0.0-develop+13dfbf46f2621dc9456458b735cb2a5f0db15e6a`.
- `encore run` served the echo app on `http://127.0.0.1:4000`.
- `/__encore/healthz`, `/echo.BasicEcho`, `/echo.Pong`, and `/htytg` all returned HTTP `200`; Basic…
- `go test -v -count=1 -tags=e2e ./e2e-tests -run '^TestEndToEndWithApp$'` passed in 48s with all s…
- `go test -short -tags=dev_build ./...` exited `0` with 70 package-level `ok` results and no failu…
- Final `go build ./cli/cmd/encore` and `go test -short -tags=dev_build ./pkg/clientgen` both exite…
**Environment gaps fixed**
- Installed Go and Rust user-locally because neither toolchain was present.
- Installed the prebuilt Encore Go runtime, checked against GitHub’s published SHA-256.
- Installed `tsparser-encore` after supplying user-local `protoc`, `libclang`, `libLLVM`, and GCC h…
- No external credentials or mocks were needed. `git status` is clean and no daemons remain listeni…

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 MPL-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 31 minutes to install, slower than the median of the 11 comparable projects Argusic has measured.

Of the 12 aws projects Argusic has installed and timed, encore was the 12th fastest to reach a running state, and 10 of 12 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 byattemptoutcomescorecost USDwhen
Argusic Runner2/3Runs100.000.28
Argusic Runner1/3Runs100.000.17

Topics (from GitHub)

awsbackendcloudcloud-nativedatabasedevopsdevops-automationdistributed-systemsencoregcpgogolanginfrastructure-as-codeinfrastructure-automationmicroservicesserverlesstypescript

Embed the badge

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

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

Questions

Does encore run?
Yes. encore runs. Argusic installed and launched it on a clean machine in 31 minutes, hitting 5 errors on the way, and recorded the session.
How did Argusic test encore?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 13dfbf46f262. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test encore?
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 encore take to install?
31 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 encore need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing encore?
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 encore compare with the alternatives?
Of the 12 aws projects Argusic has installed and timed, encore was the 12th fastest to reach a running state, and 10 of 12 reached one at all.
Where is the evidence for encore?
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