Runtime Map

Updated 2026-07-07

A runtime is the program that loads a PrismML model's weights and generates text on your hardware, e.g., llama.cpp on a laptop. Use this page to pick the runtime that fits your machine and jump to the steps for running it.

The most reliable path today is llama.cpp. It runs GGUF model files as a local command line tool or a small local server, and we have a written recipe for it that comes from the upstream docs. We have not yet run that recipe on hardware, so treat the steps as source-checked rather than proven. If you are on a Mac, MLX is the Apple Silicon path, and the Bonsai with MLX recipe is a draft that has not been run on hardware yet. Draft recipes also exist for Ollama and LM Studio.

Pick a runtime

Each row tells you whether you can run a PrismML model there today.

RuntimeWhat it isCan you run PrismML on it today?
llama.cppLocal command line tool and server for GGUF models.Yes. Follow the Bonsai on llama.cpp recipe. The commands come from the upstream docs; we have not yet run them on hardware.
MLXApple's framework for running models on Apple Silicon.Probably. Follow the Bonsai with MLX recipe. It is a draft, and we have not run it on hardware.
OllamaLocal model runner with a simple install and pull workflow.Unknown. The Bonsai with Ollama recipe is a draft, and we have not checked whether Ollama can load the current Bonsai GGUF files without conversion.
LM StudioDesktop app for downloading and chatting with local models.Unknown. The Bonsai with LM Studio recipe is a draft, and we have not checked the import flow or model compatibility.
Browser (WebGPU)Running a model inside a web page using the GPU.Not yet. We have only seen social and search mentions, and we have not found an official demo repo or model artifact.
iOS (mlx-swift)Running a model on an iPhone or iPad.Not yet. We have only seen source references, with no device run recorded.
vLLM / SGLangServer-side engines for serving models to many users at once.Not applicable for a laptop. We list them for context and have not confirmed PrismML compatibility.

How we rate the evidence

When a row says "yes" or "not yet", that judgment rests on how much evidence we have. We rate each runtime on a five step scale.

  • discovery. We have only seen social or search mentions.
  • source_checked. Official docs or repos show a working path.
  • locally_run. Someone ran one prompt and recorded the environment.
  • benchmarked. Someone captured standardized latency, throughput, memory, and task results.
  • maintained. The page has an owner and recent passing evidence.

Right now llama.cpp sits at source_checked and every other runtime sits at discovery or below. No runtime on this page has benchmark numbers yet, so this page makes no speed or memory claims.

This scale rates the evidence for a recipe, and the device report schema uses its own benchmark_status values for a recorded run. The two roughly line up, so locally_run matches a benchmark_status of partial, and benchmarked matches reproducible.

Next steps

See something wrong? Fix it.