Lizard Native
The resident-GPU path for supported hardware. It keeps the model lifecycle under Lizard’s control and uses cached GPU shaders after the first warm-up.
Product 01 / Local AI runtime
Product profile
After account activation and model setup, inference happens on the Windows PC. Prompts, answers, and model weights used for inference stay on the device. The built-in chat and local OpenAI-compatible API provide two ways to use the active model.
Execution paths
The native engines remain distinct in the architecture and in benchmark evidence.
The resident-GPU path for supported hardware. It keeps the model lifecycle under Lizard’s control and uses cached GPU shaders after the first warm-up.
A separate engine built around a typed execution graph, reused activation arena, and pre-compiled compute plan.
Official resources
The specialist Lizard site remains the authoritative source for downloads, architecture, benchmarks, support, and legal information.
Hardware planning, local privacy, model onboarding, and included capabilities.
Open overviewNative engines, routing boundaries, graph-plan execution, and fallbacks.
Read architectureProvider-separated results measured on the computer running the model.
Review evidenceA local chat workspace with saved conversations, document questions, MCP plugins, and charts the model decides to draw.
See the chatMeasure a second Windows PC over an outbound-only relay, with key-fingerprint approval and a returned evidence artifact.
See remote runsLizard LLM / Windows