VeizikNVIDIA, Apple Silicon and edge builds are available now.Release notes →
Engineering

Grouped by what it changes for you.

Not a wall of claims — researched pages in a consistent style, grouped by the axis they move: what the problem is, how veizik handles it at a reader’s level, the figures measured, and a reproduction guide. Every figure is veizik’s own, measured and reproducible; a more specialised engine may do better on a given case, and that is said where it applies.

Where veizik stands

The axes the field competes on — and where veizik leads.

Local-inference engines compete on a handful of axes: fitting a big model on a small card, how few bits at what quality, load time, long-context decode, video memory, dependencies and reliability. Here is the usual path on each, next to veizik’s own measured result.

35BMoE model resident on one 24 GB card
~6 sa 122B model ready to answer (one RTX 3090)
128Ktokens — decode measured at length, not a spec sheet
< 24 GB720p 14B video, every step, no spike
0Python, frameworks or numeric libraries
512 MBa generative model on a Raspberry Pi Zero 2 W
What the field competes onThe usual pathveizik, measured
Model vs cardA model bigger than the card is sharded onto a second GPU or streamed from CPU memory.A 35-billion mixture-of-experts model resident on one 24 GB card — about 21 GiB, no second GPU and no offload, decoding at 194 tok/s.
PrecisionA separate quantized file is produced and stored per bit-width, offline, before the model will run.The original checkpoint is read in place; precision is chosen in-engine from a large, growing catalogue of sub-byte formats, mixed per layer — no conversion, no second copy.
Model loadA large model is loaded cold on every start — seconds to minutes before the first token.A prepared, resident model is restored from hypercache: a 122B answers in about 6 s on one RTX 3090; a small language model in 14 ms on a phone.
Long contextA maximum context length is quoted on a spec sheet; the decode rate at that length is rarely shown.Decode holds near-flat to 16K tokens on a consumer card and past 128K on a datacenter one — a rate measured at each length.
Video memoryA 720p diffusion-video job can climb past a 24 GB card mid-render; the usual advice is to drop resolution or move work off the GPU.Peak VRAM holds under the 24 GB card from the first step to the last — a 14B video model at 1280×720, 81 frames.
DependenciesA Python runtime, a deep-learning framework, a numeric library and a GPU toolkit — any one of them can break the run.One self-contained binary and the driver already on the machine — no Python, no framework, no numeric library. Verifiable in three commands.
InterruptionA render that is cut off restarts from the beginning.A render resumes from its last step and finishes to the identical latent hash — proven across five interruptions, two of them host crashes.
Hardware reachGenerative models assume a GPU and gigabytes of memory.The same engine runs language, image and video on a Raspberry Pi CPU alone — down to a 512 MB Zero 2 W.

The left column is the common path these systems take, stated as a widely documented convention — no engine is named and no other engine’s figure is quoted. The right column is veizik’s own measured result, each one reproduced on the capability page it links to. These are strengths, not verdicts: a more specialised engine may do better on a given model or card, and that is said where it applies.

What the engine makes

One runtime, across the fleet.

The same native engine drawing on a datacentre card, a Jetson and a Raspberry Pi.

A tranquil alpine lake at sunrise with mirror reflections of snow-capped peaks and a pine-forest shoreline — AI-generated with FLUX.1-schnell on veizik (NVIDIA RTX 3090).
FLUX.1-schnellNVIDIA RTX 3090
A lone lighthouse on a rocky cliff in a dramatic storm with a shaft of light through moody clouds — AI-generated with SD3.5-large on veizik (NVIDIA RTX 3090).
SD3.5-largeNVIDIA GeForce RTX 3090
A delicate botanical watercolour of a flowering magnolia branch, antique herbarium-plate style, blush-pink petals on cream paper — AI-generated with FLUX.1-schnell on veizik, rendered on an NVIDIA Jetson AGX Orin.
FLUX.1-schnellNVIDIA Jetson AGX Orin
A cozy Tokyo alley at night with neon reflections on wet pavement, rendered by veizik on a Raspberry Pi 5 with Stable Diffusion 1.5 and a few-step LCM-LoRA.
Stable Diffusion 1.5 + LCM-LoRARaspberry Pi 5

Drawn natively by Veizik on an NVIDIA RTX 3090, a Jetson AGX Orin and a Raspberry Pi 5 — output, not a benchmark. Powered by Stability AI.

Pages are published as each is researched and measured. No competitor is named, and no implementation detail is given — only what a reader can hold and reproduce.