Design
application / serving layer
│
┌──────────▼───────────┐
│ Praecise Engine │ speculation policy, drafter selection,
│ uniform interface │ request shaping, sampling, KV strategy
└──────────┬───────────┘
│ pluggable backends
┌─────────────┴───────────────┐
▼ ▼
llama.cpp vLLM · SGLang · transformers an inference API
linked (FFI) TensorRT-LLM · OpenVINO GenAI remote (opt-in)
hosted (confined runtime host)
│ │
└──────────────┬──────────────┘
▼
praecise-hardware: which accelerators the machine has,
which backend drives each, what a confined engine needs
to reach them, and the decode ceiling their memory setsPraecise Engine is the acceleration layer — not a model server on its own, and not a fork of any single engine. Each backend is an adapter. Optimizations that can be expressed generically live in the engine layer; backend-specific work lives in that backend's adapter.