ModelsBenchmarks ReleasesDocumentation
Documentation

One binary, fourteen verbs.

The same command surface on every backend. It is a published contract: verbs, options and exit codes do not change meaning without a version change.

Install

Apple Silicon

veizik.availability

Early access. The 2026.09.20 Metal build is being handed out directly while the signed download path is finished. Write to support@veizik.com with the Mac you are on and we will send it.

zsh
# 1. verify what you were given
$ shasum -a 256 -c SHA256SUMS
  14 files OK

# 2. install (pure shell, nothing compiled)
$ ./install.sh

# 3. check the installation
$ veizik doctor
  backend    Apple
  integrity  sealed · .text intact
  status     ready

The installer places the CLI at ~/.local/bin/veizik and one core per model under ~/.local/lib/veizik. Set VEIZIK_PREFIX to put them elsewhere, or VEIZIK_ROOT to point an installed CLI at a different tree.

Nothing is compiled on your machine, no interpreter is used, and no system file is touched. To uninstall, delete those two paths.

You supply model weights. In this release the runtime reads your Hugging Face cache in place — it downloads nothing and writes nothing back.

Command surface

The fourteen verbs

VerbFormWhat it does
runrun <model> "<prompt>" [tokens]Generate once and exit.
chatchat <model> [tokens]An interactive session.
serveserve <model> [--port N]Answer over HTTP, locally.
modelsmodelsList what is installed here, with each model's catalogue tier and disk state.
pullpull <model>[@<revision>]Fetch a model into the cache.
removeremove <model>[@<revision>]Delete it from the cache.
convertconvert <source> [-o <file>]Prepare a checkpoint you already have.
inspectinspect <model>Show what a model is: status, context, geometry, where it lives, whether it is runnable.
benchbench <model>Measure this machine.
cachecache info | cleanInspect or tidy the download cache.
configconfig show | set | unsetSee and change settings.
completioncompletion zsh | bash | fishEmit a shell completion script.
doctordoctorCheck this installation: backend, catalogue and integrity.
versionversionShow version and backend.
Profiles

You choose an intent; the engine chooses the path

Each profile selects a verified execution path for the model, device and requested objective. How that path is built is ours to decide and is not part of the interface — what you choose is what you want more of.

auto is the default, and it is the right answer almost always.

auto
Default. A verified path chosen for this model and this device.
fastest
Throughput first.
balanced
The middle of the range.
quality
Numerical quality first.
smallest
Least memory on the device.

In the current experimental release every model runs the single published path; profile selection arrives with the calibrated packs.

Exit codes

Scriptable, and frozen

CodeMeaning
0Success.
2Usage error — no arguments, unknown verb, missing prompt.
4Model not found or not resolvable.
5Artifact integrity or anti-tamper failure. Fail-closed: nothing runs.
6No device or runtime available here.

Once the runtime has started, its own exit code passes through unchanged — a wrapper that rewrote it would be lying to your script. Codes that arrive with a veizik: message on stderr are the front end's; codes without one came from the runtime.

Limits

What this release does not do

Behaviour

What it does on the network, and to your disk

No network at inference

Generation makes no outbound call. Prompts and outputs never leave the machine, and the engine works with the network off.

No writes

No converted artifact, no weight cache, no temporary model files. Quantisation happens in device memory during load.

No telemetry in the runtime

The engine does not phone home. Anything about your usage that we do not measure is something we cannot know.