Local model operator

Paddock

Run local models as dependable infrastructure, not a pile of processes.

Paddock manages llama.cpp model lifecycle, OpenAI-compatible routing, downloads, telemetry, and a live operator dashboard on one machine.

Public alpha · Linux x86-64
Paddock
Paddock dashboard showing active local models, aggregate telemetry, and GPU status.
A real Linux and CUDA smoke run: model roles, durable aggregate telemetry, process identity, and GPU state.

Where it fits

The local inference layer

Operators who want a clear, local-first control plane for GGUF models and the applications that depend on them.

Capabilities

What it makes possible.

01

Loads models on demand

Apply deterministic capacity eviction and optional idle unloading across model roles.

02

Presents one local API

Route supported chat, completion, Responses, embedding, and reranking requests through an OpenAI-compatible surface.

03

Owns the model lifecycle

Download, validate, register, start, stop, restart, and inspect GGUF model sets.

04

Keeps operations visible

Watch model, process, request, and GPU behavior without retaining prompts or responses.

Working sequence

A clear path through the system.

  1. 01
    Install the verified alpha

    Use the public bootstrap and review the current compatibility evidence.

  2. 02
    Build the managed runtime

    Let Paddock detect the host and build its pinned llama.cpp baseline.

  3. 03
    Register a model

    Pull a GGUF artifact set and expose it through the local API when requested.

Boundary

What this page is not claiming.

Go deeper

Use the product page for orientation. Use the docs for decisions.

Read Paddock documentation