miniblue
Local Azure development. One binary. No account needed. 25+ emulated services for testing, CI and local dev.
Runssource: GitHubhomepageGoMITcommit 22b04dbbf4f3
Go, MIT licensed. The project labels itself: azure, azure emulator, ci cd, cloud, developer tools, devops, golang and localstack.
miniblue runs. An Argusic agent installed it in 6 minutes and hit 3 errors on a clean machine with no GPU, and the whole session was recorded.
miniblue builds, starts on port 4566, responds to /health with HTTP 200, serves 30 Azure service emulations, and passes 211 tests across all unit/e2e test suites. The azlocal CLI correctly creates resource groups and manages keyvault secrets against the running server.
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 93.3 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 (golang) 1.26 not installed on system6 minutes
- Go std library src tree had missing go.mod/go.sum (copied from pkg/share instead of pkg/lib)1 minute
- Integration tests fail: Docker not available for MySQL containers (rootless Docker not found)
- Install time
- 6 minutes
- Cold machine to finish
- 10 minutes
- Errors hit and fixed
- 3 hit, 2 fixed with no human help
- How the result was proved
- go test ./tests/ ./internal/storageauth/ ./internal/store/ ./internal/services/aks/ ./internal/services/deployments/ ./cmd/azlocal/ returned 'ok' for all 6 packages (211 tests passed); server start + curl http://localhost:4566/health returned HTTP 200 with status 'running'; azlocal keyvault secret set/show roundtripped secret values successfully
- Model tokens used
- 92,022
- Exact commit tested
- 22b04dbbf4f3
- 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.
/bin/sh -lc 'export GOROOT=/home/runner/go/1.26 && export PATH="$GOROOT/bin:$PATH" && cd /work/repo… succeeded in 0ms: ok github.com/moabukar/miniblue/tests (cached) ok github.com/moabukar/miniblue/internal/storageauth (cached) ok github.com/moabukar/miniblue/internal/store (cached) ok github.com/moabukar/miniblue/internal/services/aks (cached) ok github.com/moabukar/miniblue/internal/services/deployments (cached) ok github.com/moabukar/miniblue/cmd/azlocal (cached) All 211 tests pass, the server starts and responds correctly, and the azlocal CLI works against it.… tokens used 92,022 All 211 tests pass, the server starts and responds correctly, and the azlocal CLI works against it.…
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 6 minutes.
- Ran without a GPU, so it does not need one to start.
- Licensed MIT, as reported by its host.
What did not, or is not known
- Hit 3 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 6 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)
azureazure-emulatorci-cdclouddeveloper-toolsdevopsgolanglocalstackterraformtesting
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/miniblue)Questions
- Does miniblue run?
- Yes. miniblue runs. Argusic installed and launched it on a clean machine in 6 minutes, hitting 3 errors on the way, and recorded the session.
- How did Argusic test miniblue?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 22b04dbbf4f3. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test miniblue?
- The run that produced this verdict cost $0.22: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does miniblue take to install?
- 6 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 miniblue need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing miniblue?
- 3 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.
- Where is the evidence for miniblue?
- 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.