lucascs@proton.me Lucas C.S. Lemonade runs large language models locally and exposes them over an OpenAI-compatible HTTP API, so any client that speaks that API can talk to a model on the machine instead of a hosted service. It ships two programs: lemond, the server daemon, and lemonade, the command line client used to pull, run, benchmark and manage models. The inference backends themselves — llama.cpp, whisper.cpp, vLLM, ONNX Runtime GenAI, Ryzen AI (the AMD NPU stack), stable-diffusion.cpp, Kokoro and the others — are not compiled into this package. lemond knows about each of them through a registry compiled into the binary and downloads the matching prebuilt backend at runtime, picking one suited to the hardware it finds: NVIDIA and AMD GPUs, Intel GPUs, AMD NPUs or plain CPU. That is why app-arch/unzip is a runtime dependency and why no acceleration backend appears among the build dependencies. The daemon runs as the dedicated lemonade user and keeps its models and its config.json under /var/lib/lemonade. Both a systemd unit (system and user scope, installed by upstream) and an OpenRC service are provided. Not built here: the Tauri desktop shell and the AppIndicator system tray, which upstream builds from separate npm and cargo dependency sets. With USE=webapp the browser UI that lemond serves is bundled from a pre-populated node_modules distfile, since upstream's build otherwise runs npm ci and the sandbox has no network. Link against sys-libs/libcap so lemond can pass capabilities on to the backend processes it spawns Bundle the browser UI that lemond serves, using a pre-populated node_modules distfile instead of a networked npm install lemonade-sdk/lemonade https://github.com/lemonade-sdk/lemonade/issues https://lemonade-server.ai/docs/ https://github.com/lemonade-sdk/lemonade/releases