enroute
Programmable git infrastructure on top of object storage. Think turbopuffer for git. Open source alternative to Pierre (code.storage) and Cloudflare Artifacts.
Runssource: GitHubhomepageRustApache-2.0commit bc0dc6efce9c
Rust, Apache-2.0 licensed. The project labels itself: agentic ai, agentic workflow, forge, git, git backend, git forge, git server and headless.
enroute runs. An Argusic agent installed it in 25 minutes and hit 2 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Enroute builds and passes all 22 integration tests, and the dev server starts listening for git on http://127.0.0.1:8080 and the grpc api on http://127.0.0.1:50051
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.
What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- raft test file (5 tests) failed on first run: idle_repos_go_quiet, lagging_follower_catches_up_via_snapshot, members_are_every_logs_voters, replicated_push_and_failover all panicked with timeout/read-barrier errors
- crash test (acknowledged_writes_survive_sigkill) failed on first run: cluster did not become ready
- Install time
- 25 minutes
- Cold machine to finish
- 9 minutes
- Errors hit and fixed
- 2 hit, 2 fixed with no human help
- How the result was proved
- cargo test passed all 22 test binaries (basic, api, cli, raft, crash, compaction, cold, features, inline, follow, grpc, hooks, lifecycle, migration, push_pack, replay, repos, restart, roles, sweep, access) and the binary started with cargo run dev showing the listening banner on ports 8080 and 50051
- Model tokens used
- 114,182
- Exact commit tested
- bc0dc6efce9c
- 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.
enroute dev is running. Press Ctrl-C to stop. git http://127.0.0.1:8080 api http://127.0.0.1:50051 dir /work/repo/.enroute/dev hooks off (every request may read and push; pass --hooks URL to opt in) Try: git push http://127.0.0.1:8080/hello.git main enroute repo list Everything builds, tests pass, and the dev server launches. Here's the result: tokens used 114,182 Everything builds, tests pass, and the dev server launches. Here's the 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
- Reached a running state on a clean machine, with the session recorded.
- Recovered from all 2 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 Apache-2.0, as reported by its host.
What did not, or is not known
- Took 25 minutes to install, slower than the median of the 31 comparable projects Argusic has measured.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 32 agentic-ai projects Argusic has installed and timed, enroute was the 27th fastest to reach a running state, and 21 of 32 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
Topics (from GitHub)
agentic-aiagentic-workflowforgegitgit-backendgit-forgegit-serverheadlessobject-storageopen-sourceopensourcerustself-hostedversion-controlversion-control-system
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/enroute)Questions
- Does enroute run?
- Yes. enroute runs. Argusic installed and launched it on a clean machine in 25 minutes, hitting 2 errors on the way, and recorded the session.
- How did Argusic test enroute?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit bc0dc6efce9c. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test enroute?
- The run that produced this verdict cost $0.03: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does enroute take to install?
- 25 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 enroute need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing enroute?
- 2 things broke in the recorded run, and 2 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does enroute compare with the alternatives?
- Of the 32 agentic-ai projects Argusic has installed and timed, enroute was the 27th fastest to reach a running state, and 21 of 32 reached one at all.
- Where is the evidence for enroute?
- 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.