#0424
AgentSqliteContainers
The agent product's transcripts live on your metal, not a vendor dashboard
Each firm gets a container on your bare metal server. hoody-agent runs inside it; session history and the firm's working files sit on that container's disk. Hoody's API sees that the container exists; it can't see the prompts, the responses, or the documents, because the proxy serving them runs on your server.
The model path is yours to name. Route through the Hoody AI gateway and it logs no prompt or response content, though the paid upstream provider receives what it's sent. Point the firm's container at a local model on the same box and nothing leaves at all.
Forty firms, forty containers, idle ones costing nothing, one answer to the first question.
The transcript exists in one place, and that place is a disk you rent.