Local-first and private
Tharas runs where your code already is. What leaves the machine is an entitlement check and a small set of typed measurements — never a file, never a prompt, never a path.
Where the work happens#
The engine, the memory index, the worktrees and the verification all run on the machine you installed Tharas on, against the repositories already there.
The control plane exists for accounts, subscriptions, entitlements and releases. It is not a place your source goes.
Why a leak is structurally impossible, not merely forbidden#
Telemetry carries numbers, booleans and values from declared enumerations. There is no field that accepts free text.
That distinction matters. A policy saying "do not send file paths" is a promise someone can break by accident. A schema with no string field is a shape in which the mistake cannot be expressed.
The hosted edition keeps the same boundary
Tharas Cloud gives an organisation an isolated office per tenant. It is platform access, never source access — the same line, drawn in the same place.
Common questions
Does Tharas upload my repository?
No. The engine runs locally against your working copy, and the index it builds stays in the project working directory.
What does leave my machine?
An entitlement check so the subscription can be verified, the model calls themselves, and typed telemetry containing no free-form strings.