emissary
open source Kubernetes-native API gateway for microservices built on the Envoy Proxy
Runssource: GitHubhomepagePythonApache-2.0commit d6eb1ba441cb
Python, Apache-2.0 licensed. The project labels itself: ambassador, api gateway, api management, cloud native, docker, envoy, envoy proxy and gateway api.
emissary runs. An Argusic agent installed it in 8 minutes and hit 2 errors on a clean machine with no GPU, and the whole session was recorded.
Python packages install and 173 unit tests pass; Go binary builds and entrypoint tests pass; diagd CLI runs; integration tests requiring Docker skipped
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 90 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.
- Go not pre-installed; downloaded Go 1.25.0 tarball to ~/go_bootstrap2 minutes
- Python integration tests require Docker for envoy config validation; not available
- Install time
- 8 minutes
- Cold machine to finish
- 21 minutes
- Errors hit and fixed
- 2 hit, 1 fixed with no human help
- How the result was proved
- uv run pytest python/tests/src/tests/unit/ returned '173 passed'; go test ./cmd/entrypoint/... returned 'ok'; go build ./cmd/busyambassador/ produced working binary; uv run diagd --help showed usage
- Model tokens used
- 68,509
- Exact commit tested
- d6eb1ba441cb
- 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.
7. **Integration tests**: Failed because `assert_valid_envoy_config` requires Docker (not available… tokens used 68,509 Let me compile the final results. Here's what was done and verified: 1. **Python environment**: Created a venv with Python 3.13.5, installed all runtime and dev depende… 2. **Go environment**: Downloaded Go 1.25.0 tarball to `~/go_bootstrap/` (no system packages availa… 3. **Python unit tests**: `uv run pytest python/tests/src/tests/unit/` -> **173 passed** 4. **Go build**: `go build ./cmd/busyambassador/` -> produced `busyambassador` binary that runs and… 5. **Go tests**: `go test ./cmd/entrypoint/...` -> **OK** (both packages passed) 6. **diagd CLI**: `uv run diagd --help` -> shows usage (installed and importable) 7. **Integration tests**: Failed because `assert_valid_envoy_config` requires Docker (not available…
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.
- Installed in 8 minutes.
- 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
- Hit 2 errors during setup, 1 of which were not solved.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
- A quick evaluation: it was running 8 minutes after the clone.
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)
ambassadorapi-gatewayapi-managementcloud-nativedockerenvoyenvoy-proxygateway-apikuberneteskubernetes-annotationskubernetes-ingressmicroservice
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/emissary)Questions
- Does emissary run?
- Yes. emissary runs. Argusic installed and launched it on a clean machine in 8 minutes, hitting 2 errors on the way, and recorded the session.
- How did Argusic test emissary?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit d6eb1ba441cb. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test emissary?
- The run that produced this verdict cost $0.09: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does emissary take to install?
- 8 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 emissary need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing emissary?
- 2 things broke in the recorded run, and 1 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for emissary?
- 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.