olla

High-performance lightweight proxy and load balancer for LLM infrastructure. Intelligent routing, automatic failover and unified model discovery across local and remote inference backends.

Runs with mockssource: GitHubhomepageGoApache-2.0commit bb0612193168

Go, Apache-2.0 licensed. The project labels itself: ai, amd, golang, intel, llama cpp, llamacpp, llm inference and llm proxy.

olla runs, with stand-ins for the services it depends on. An Argusic agent installed it in 2 minutes and hit 1 error and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

Olla v0.0.x builds from source with Go 1.24.13, starts on localhost:40114, serves health endpoint returning healthy, passes all 42 test packages, validates configuration, accepts and responds to HTTP requests, and passes the make ready pre-commit gate (test + fmt + vet).

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

verdict
Runs with mocks
Argusic Score
92 / 100
cost of the verifying run
$0.06 (measured)
recorded runs
1
last tested
stars
340
forks
68
open issues
32
watchers
3
size
14 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 olla, 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.

  • Go 1.24.13 binary not found in PATH1 minute
Install time
2 minutes
Cold machine to finish
6 minutes
Errors hit and fixed
1 hit, 1 fixed with no human help
How the result was proved
curl http://localhost:40114/internal/health returned 200 with body {"status":"healthy"}; go test ./... passed all 42 test packages with 0 failures; make ready passed (test-short, test-race, fmt, vet); config validation passed
Model tokens used
39,059
Exact commit tested
bb0612193168
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

The end of the recording

The last lines of the terminal session that decided this verdict, exactly as they were recorded.

ok    github.com/thushan/olla/test/cmd/ollamock  (cached)
ok    github.com/thushan/olla/test/config_docs  (cached)
ok    github.com/thushan/olla/test/integration  (cached)
exec
/bin/sh -lc 'cd /work/repo && export PATH="/tmp/go/bin:$PATH" && go test ./... -count=1 2>&1 | grep…
 succeeded in 41174ms:
42
42 test packages passed, 0 failures. Everything is solid.
2026-10-24T19:22:03.563056Z ERROR codex_core::session: failed to record rollout items: thread 01a16…
tokens used
39,059
42 test packages passed, 0 failures. Everything is solid.

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 2 minutes, faster than the median of the 236 comparable projects Argusic has measured.
  • Recovered from all 1 error without a human stepping in, which says the failures are documented well enough to solve.
  • Licensed Apache-2.0, 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.

Of the 237 ai projects Argusic has installed and timed, olla was the 54th fastest to reach a running state, and 168 of 237 reached one at all.

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 Runner1/3Runs with mocks92.000.06

Topics (from GitHub)

aiamdgolangintelllama-cppllamacppllm-inferencellm-proxyllm-routerllm-routinglmstudiolocal-aimlxnvidiaollamaproxyself-hostedself-hosted-aisglangvllm

Embed the badge

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

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

Questions

Does olla run?
olla runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 2 minutes, hitting 1 error on the way, and recorded the session.
How did Argusic test olla?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit bb0612193168. One attempt is recorded, and the full method is on the methodology page.
What did it cost to test olla?
The run that produced this verdict cost $0.06: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does olla take to install?
2 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 olla need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing olla?
1 thing broke in the recorded run, and 1 were fixed without human help. Each one, and the time it cost, is listed on this page.
How does olla compare with the alternatives?
Of the 237 ai projects Argusic has installed and timed, olla was the 54th fastest to reach a running state, and 168 of 237 reached one at all.
Where is the evidence for olla?
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.

Discussion