An assistant that cannot send your members messages to a cloud model
Not a policy, not a setting, not a promise: the process refuses to start against a public AI endpoint.
The question
an AI assistant where the data never leaves my machine
The model runs on hardware you control, and it is enforced at boot rather than configured. Point it at a public endpoint and the process refuses to start, with the reason recorded: so archived member text cannot be sent to a public service by a configuration typo.
Who this is for
Anybody with a contractual, regulatory or plain-stubbornness reason that the conversations cannot leave the building.
A boot check, and the complete list of what does leave
The claim is no AI cloud. It is not no outbound traffic, and the difference is printed rather than glossed.
Only loopback and private addresses are accepted for the model endpoint, and anything else throws before the service is up. What does leave the machine is a list of five things, printed in full on the security page, and a sweep of the source is what produces it rather than a promise. No member message is among them, with one deliberate exception that is not an AI: the search query, when a member explicitly asks for a lookup.
What it will not do
It cannot prove to a member of somebody else deployment that the code running is the code they read. That gap is structural, it is the same gap every hosted service has, and it belongs to one of the three tiers rather than to the product.
What this needs, and what state it is in
Read from the same table the ways-in page renders, so it cannot be current there and stale here.
The doors this touches
Any door at all
This one does not depend on how she is reached. The refusal happens at boot, before any door is open, and it holds under every front path.
Over a web server, as an ordinary web assistantstarted
More than nothing, honestly: a demo route drives the real interaction engine, consent logic and persistence over the fake adapter, with a deterministic rules layer, a 25 message budget and synthetic data. The admin console and the public archive are web surfaces rather than chat ways in
The web door is the one most readers of this page assume they are buying, and it is not finished. The door that is built is a chat network you would have to adopt. That is the honest answer, and it will cost us some readers.
The pages that carry the checks
This page makes no claim of its own. Each one below is where the thing is written down with the way to verify it.
What to read
The security page carries all four claims with the file or command that settles each, and the three tiers with the gap named on the one it applies to.