gate
Build efficient Bedrock & Java Minecraft networks with multi-version support. Powers global Connect network at production scale. Runs with 10MB.
Runssource: GitHubhomepageGoApache-2.0commit 7d9b2e1debcb
Go, Apache-2.0 licensed. The project labels itself: docker, forge, go, java, kubernetes, lightweight, minecraft and minecraft forge.
gate runs. An Argusic agent installed it in 25 minutes and hit no errors on a clean machine with no GPU, and the whole session was recorded.
Gate proxy builds from source, passes all 52 test packages with zero failures, starts up binding port 25565 and registering 4 configured servers, and shuts down gracefully.
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 96 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.
- Install time
- 25 minutes
- Cold machine to finish
- 4 minutes
- Errors hit and fixed
- 0 hit, 0 fixed with no human help
- How the result was proved
- go test -count=1 ./... exited 0 with 52 packages passing (no failures); ./gate --version printed 'gate version test-verify'; ./gate started, bound 0.0.0.0:25565, registered 4 servers, and shut down cleanly on SIGTERM
- Model tokens used
- 66,675
- Exact commit tested
- 7d9b2e1debcb
- 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.
**Install**: Go was not present in the container. I downloaded Go 1.26.0 to `/tmp/go/`, set `PATH` … **Build**: `go build ./...` succeeded. `go build -o gate gate.go` produced a 26MB binary. **Launch**: `./gate` started, logged server registration (4 servers), bound to `0.0.0.0:25565`, and… **Tests**: All 52 test packages passed with zero failures. Notable packages exercised: `pkg/gate` (… tokens used 66,675 Everything works. Let me compile my report. The project built and ran without any errors. Here's a summary of what I observed: **Install**: Go was not present in the container. I downloaded Go 1.26.0 to `/tmp/go/`, set `PATH` … **Build**: `go build ./...` succeeded. `go build -o gate gate.go` produced a 26MB binary. **Launch**: `./gate` started, logged server registration (4 servers), bound to `0.0.0.0:25565`, and… **Tests**: All 52 test packages passed with zero failures. Notable packages exercised: `pkg/gate` (…
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.
- Nothing broke on the way: zero errors between clone and running.
- 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.
What did not, or is not known
- Took 25 minutes to install, slower than the median of the 23 comparable projects Argusic has measured.
Of the 24 docker projects Argusic has installed and timed, gate was the 18th fastest to reach a running state, and 17 of 24 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.
- Following its own README: the documented path worked with nothing to fix.
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 by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 2/3 | Runs | 100.00 | 0.02 | |
| Argusic Runner | 1/3 | Runs with mocks | 92.00 | 0.05 |
Topics (from GitHub)
dockerforgegojavakuberneteslightweightminecraftminecraft-forgeminecraft-networkminecraft-proxyminecraft-serverminecraft-server-proxypaperproxyreverse-proxyserver-proxyspigot
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/gate)Questions
- Does gate run?
- Yes. gate runs. Argusic installed and launched it on a clean machine in 25 minutes, hitting 0 errors on the way, and recorded the session.
- How did Argusic test gate?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 7d9b2e1debcb. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test gate?
- The run that produced this verdict cost $0.02: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does gate 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 gate need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing gate?
- Nothing did, in the recorded run: zero errors between clone and running.
- How does gate compare with the alternatives?
- Of the 24 docker projects Argusic has installed and timed, gate was the 18th fastest to reach a running state, and 17 of 24 reached one at all.
- Where is the evidence for gate?
- 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.