krakend-ce
KrakenD Community Edition: High-performance, stateless, declarative, API Gateway written in Go.
Runssource: GitHubhomepageGoApache-2.0commit dc4321e9b427
Go, Apache-2.0 licensed. The project labels itself: ai gateway, api gateway, apis, async, backend services, cloud native, docker and go.
krakend-ce runs. An Argusic agent installed it in 12 minutes and hit 2 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
KrakenD-CE v2.13.11 binary built from source, all 57 integration tests pass, and the gateway starts and listens on port 8080.
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.
- go compiler not found3 minutes
- wget not found for schema download1 minute
- Install time
- 12 minutes
- Cold machine to finish
- 4 minutes
- Errors hit and fixed
- 2 hit, 2 fixed with no human help
- How the result was proved
- go test -v ./tests: 57 subtests and 1 example all PASS, entire suite 4.044s. Binary reports 'KrakenD Version: 2.13.11'. 'krakend run -c krakend.json' starts and listens on :8080.
- Model tokens used
- 57,638
- Exact commit tested
- dc4321e9b427
- 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.
tokens used 57,638 KrakenD starts up and listens on port 8080. Everything works. Let me summarize the final state. Here's the full summary: **Install**: `make build` succeeded after installing Go 1.22.10 from tarball and downloading the sc… **Errors encountered**: 1. **`wget: not found`** — The Makefile's schema download target uses `wget` which isn't installed.… 2. **`go: not found`** — No Go compiler was pre-installed. Fixed by downloading and extracting Go 1… **Verification**: - `./krakend version` printed `KrakenD Version: 2.13.11` - `go test -v ./tests` ran 57 integration tests and 1 example — all passed with `PASS, ok 4.044s` - `./krakend run -c krakend.json` started, initialized all endpoints, and listened on port 8080
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 12 minutes, faster than the median of the 22 comparable projects Argusic has measured.
- 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.
- Measured 2 times, so the result is not a one-off.
Of the 23 ai-gateway projects Argusic has installed and timed, krakend-ce was the 11th fastest to reach a running state, and 17 of 23 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)
ai-gatewayapi-gatewayapisasyncbackend-servicescloud-nativedockergogolanggraphqlmicroservicemicroservicesnatsreverse-proxy
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/krakend-ce)Questions
- Does krakend-ce run?
- Yes. krakend-ce runs. Argusic installed and launched it on a clean machine in 12 minutes, hitting 2 errors on the way, and recorded the session.
- How did Argusic test krakend-ce?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit dc4321e9b427. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test krakend-ce?
- 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 krakend-ce take to install?
- 12 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 krakend-ce need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing krakend-ce?
- 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 krakend-ce compare with the alternatives?
- Of the 23 ai-gateway projects Argusic has installed and timed, krakend-ce was the 11th fastest to reach a running state, and 17 of 23 reached one at all.
- Where is the evidence for krakend-ce?
- 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.