Security
The boundary is the product.
Privacy promises are usually paper. This page is what one looks like built into hardware, and how your own team verifies it.
What stays and what leaves
Two columns, no footnotes.
Stays on your hardware
Everything.
- Document text, indexes, and embeddings
- Models and every inference they run
- Conversations and memory
- Identities and access rules
- The audit chain itself
Leaves your network
Telemetry.
- Usage totals and latency figures
- Error rates and version info
- License status and update checks
- Never content, a document name, or who asked
The exceptions are yours to grant.
Every appliance ships with one posture: nothing leaves the box. Two features can reach beyond it. Both arrive shut, only your administrator can open them, and every use of either lands in the audit chain.
- 01 Cloud passthroughAn administrator can permit queries to an external cloud model. Before anything leaves, the box scrubs identifying and confidential material from the query. The answer returns to the box, the redacted material is restored there, and the user sees the whole. The original never left.
- 02 Deep researchA research mode can reach beyond your walls for outside sources, driven by the models on the box. The same administrative gate holds it, and the same scrubbing stands between your documents and the wire.
What your team can inspect
The boundary holds because the parts can be checked. Five mechanisms carry it.
- 01 Pull-only managementDura OS calls out for licenses and updates. Nothing outside can call in.
- 02 The audit chainEvery question, answer, and tool call lands in a hash-linked, tamper-evident chain. Anchor it in write-once storage and export it to your SIEM. Your compliance officer can read it whole.
- 03 Permissions in the databaseRetrieval respects who may see what, enforced in the database itself, not in a prompt. Every user’s access is isolated down to the database row.
- 04 Signed updatesUpdates arrive signed, and they wait for your review.
- 05 Support on your termsSupport sessions happen only when you start them, and they land in your audit chain.
Inside the walls, still fenced
The same discipline holds inside the walls, between your own users.
- 01 Memory with oversightMemory is scoped to each user alone. Material tagged sensitive is never remembered, and nothing becomes shared knowledge without an administrator’s review.
- 02 Enterprise sign-inSingle sign-on through the identity provider you already run (OIDC), or local accounts kept on the appliance.
Bring your security team. The architecture review is part of the demonstration, and the management link is theirs to inspect.
Request a private demo at onpremintelligence.com.