1. Add approved files
Policies, manuals, SOPs, contracts, and internal guidance stay in the account or deployment you choose.
Documents
Only approved files can answer. Every answer names its source.
Ask a model about your own policies and it answers from whatever it was trained on, or invents a source that sounds right. Tileward Documents confines it to the files you approved: retrieval never leaves that set, and the passage it answered from comes back with the answer. Files stay private to your account, never pooled with another tenant, never used for training. To rule out whole topics rather than sources, Governance locks them before the request reaches the model.
Works with the clients you already run
28 have a recipe to paste, and anything else that speaks MCP works too.
The job
Ground the answer before the model writes it.
Documents is the approved knowledge layer. It does not ask the model to remember policy, invent a source, or cite a file it never saw.
2. Retrieve the passage
For each question, Tileward selects the passage that can answer instead of sending the whole library.
3. Return the citation
The answer carries the source so a person can check it against the document in force.
Isolation
Your documents are not a shared pool.
Hosted accounts are isolated. VPC and air-gapped deployments keep the entire data path on infrastructure you control.
Hosted
Managed service with account-level separation.
Your VPC
Documents, retrieval, and inference remain inside your cloud boundary.
Air-gapped
No document, question, answer, or index reaches Tileward.
Try it on a source you know
Bring one document and one question.
We will show the retrieved passage, the answer, and the citation.