Download
No account, no card, no telemetry. The script works out your platform,
verifies what it downloads against the release's SHA256SUMS,
and sets up a service that starts at login.
Loading the latest release…
macOS 13 Ventura or later
The one-liner takes the Metal build on Apple Silicon and the portable
one on Intel. It installs llamay to
/usr/local/bin and a LaunchAgent that runs as you, so the
server is there after a reboot.
Then the server is on http://127.0.0.1:11435.
Read the script before you run it — it is
served from the repository it lives in.
glibc · x86-64 and arm64
Installs a systemd service running as its own llamay user,
with the binary at /usr/bin/llamay. Set
LLAMAY_NO_SERVICE=1 beforehand to install only the CLI.
The script refuses rather than continuing if the machine has no
sha256sum or shasum: an installer that skips
the check is one that runs whatever it was handed.
Removing the package keeps your models: they can be tens of gigabytes, and reinstalling does not bring them back.
Windows 10 or later
Per user, so it needs no administrator prompt. Adds
llamay to PATH and registers a logon task, so
the server is there after a reboot.
Paste it in PowerShell. Read the script. The installers are Authenticode signed through Azure Trusted Signing.
Go 1.26
The default build has no cgo and nothing outside the standard library,
which is what makes make cross six targets from one
machine rather than six machines.
$ make build # ./bin/llamay, portable, no cgo $ make build-metal # + Metal $ make build-fast # + Metal and Accelerate $ make build-cuda # + CUDA — no toolkit, no card needed to build $ make build-vulkan # + Vulkan — no SDK, no loader needed to build $ make check # fmt, vet, tests, and the invariants
Before you install
On an M4, llamay decodes at about 68% of llama.cpp's rate and 64% of Ollama's. Its x86 prefill is 1.4× to 2× llama.cpp's on three of four models. Both columns, every round, are on the throughput page.
gpt-oss and phi3-mini exceed the quality bound under vq8. Run them with -kv f32. llamay verify tells you per file, rather than leaving you to notice.
Where every other architecture tested is inside 1.3%. It is a known defect in that block, not a rounding difference, and it is written up rather than omitted.
The chat window is macOS only today. Elsewhere llamay is a CLI and a server — which is the whole surface for anyone who wanted that anyway.
The server listens on loopback, and no provider is configured until you add one. If you put it on 0.0.0.0, set LLAMAY_API_KEY in the same breath.
llamay.com/install.sh is deployed from packaging/install.sh on every push, which is the only way to keep the reviewed script and the executed one from drifting.