Written for the person who has to sign off on this. Specifics, not adjectives.
Zero inbound ports: No public IP, no port forwarding, no firewall changes. There is no listening service for anyone to find or scan.
Outbound only: The server reaches out to join your private encrypted network. Nothing reaches in.
Remote work still works: Employees connect from home or the road through that same encrypted network, as if they were in the office.
What travels: The question, the small set of retrieved snippets needed to answer it, and the answer itself.
What never travels: The document library. It is indexed and searched on the server and stays there permanently.
End-to-end encrypted: Everything in transit is protected with WireGuard-class encryption between the device and your server.
Enforced inside retrieval: Permissions are applied within the search itself, not as a filter on the output. Restricted documents never enter the model's context.
Adversarially tested: A test suite has an unauthorized user ask for a private collection's contents across a dozen phrasings. Zero restricted passages are ever retrieved.
Live changes: Granting or revoking access takes effect on that person's very next question. No restart, no reindex.
Nothing to phish: There are no passwords and no shared logins. Access is granted to a specific enrolled device.
Keys stay put: Each device generates its own keypair on enrollment. The private key is sealed in the operating system's keychain and never transmitted.
Instant revocation: A lost laptop is one click. The revoked device is refused on its very next request, regardless of network access.
No phoning home: Licensing is verified offline. The server never contacts us to decide whether you may use your own software.
Never a lockout: A lapsed license degrades gracefully to read-only. Existing conversations keep working. Your data is never held hostage.
Verifiable backups: One archive captures configuration, users, permissions, and the document index, with an integrity manifest checked before any restore writes a byte.
No training on your data: Your documents, questions, and answers are never used to train any model, including ours. There is no cloud backend holding your content.
Minimum permissions, always: Optional integrations are opt-in, use your organization's own accounts, and request the narrowest permission that does the job. Where an integration drafts something, it can create the draft and nothing else.
No usage telemetry in on-premise builds: No product analytics, no consumer billing, no marketing email. None of it is present in a server deployment.
We would rather answer them now than have you find out later. Ask us anything about the architecture.
Speak to sales