Know what your fleet is actually running.
A console for a homelab that grew. It finds what is already serving across your machines, records it as a plan you approve, then keeps checking reality against it.
$ curl -fsSL https://get.abliter8.ai/install.sh | sh
Rather read it first? Sensible.
curl -fsSL https://get.abliter8.ai/install.sh -o install.sh — then read it and run it.
Windows: irm https://get.abliter8.ai/install.ps1 | iex.
Checksums at SHA256SUMS.
Needs Node 22+ and git. It will not install either for you.
The failure it was built for
Your gateway advertises a model. The machine behind it was rebooted, or reconfigured, or quietly loaded something else. The route still resolves. Every caller still gets HTTP 200. Nothing alerts, because from the outside nothing is broken — and you find out from an answer that is subtly worse than it should be.
a8 resolves each route to the machine actually behind it and asks that machine what it is serving. When the two disagree, it says so, and names which one it checked. Where a gateway cannot say where a route points, a8 tells you that too, instead of implying a check it never ran.
What it does
Probes conventional ports and identifies what answers — Ollama, llama.cpp, vLLM, SGLang, oMLX, mlx-lm, LM Studio, Foundry Local, FastFlowLM. On a mesh it reads the host list from your own client instead of scanning a range.
Findings are a proposal, never a fact already applied. You edit it, you confirm it, and that becomes the thing reality is measured against. It is a plain file you can read.
Missing endpoints, unexpected ones, a model that changed underneath a route. Each finding says what was checked and how confident it is.
No models yet? It installs the basics that suit your hardware, shows every command before running it, and confirms the port answers afterwards — because an exit code is not proof.
Start, stop and restart endpoints through systemd, launchd or docker, locally or over SSH. Every action is logged with whether the effect was actually observed.
Benchmarks with anchored interpretation, and recipes that record how a model is served — version-controlled, so you can answer why a config changed and what it cost.
How it behaves