One place for every document. One rule for who sees it.
Browse, search, or just ask. One access rule governs all three — and it runs on your servers.
Model proposes; an administrator confirms
Clearance confidential · member
33 of 82 documents
Every refusal, with its reason
public, internal, confidential, restricted
your tier sets the ceiling, the grant opens the folder
written once, used by the application and the database
the same rule decides all three
Every screen your team works in.
Twelve screens. The menu shows only the ones your role can reach.
Library
Folders you are cleared to enter. Each document shows its classification.
Search
Search everything you are cleared to read. You are told how much was held back.
Ask KhojAI
Ask in plain language. The answer comes only from passages you were shown.
Upload
Every stage runs in the open. A person confirms the proposed classification.
Administrators only
People & Access
Clearance tiers and folder grants in one place, with the requests a refusal produces.
Invitations
Invite somebody with a clearance and their grants. No mail relay? The link comes back to you.
Administrators only
Audit Log
Every read, and every refusal with its reason.
Answer Records
Every answer leaves a record you can cite.
Retention
The schedule proposes, a separate person approves. Legal hold outranks both.
Administrators only
Recertification
Proof that access is still right, folder by folder.
Attestations
Proof that a policy was read, person by person.
Settings
Mail and security for the installation. Changes apply on the next request.
System administrators only
Clearance and grant, checked on every request.
Clearance sets the ceiling. Grants say what sits beneath it. No role overrides either.
- Written once. The application and the database both use that same rule.
- It runs inside the search, so documents you cannot see are never candidates.
- They never reach the AI, so no clever question can talk it into revealing them.
- Tests run on every change to prove browse, search and ask still agree.
Identical clearance, opposite outcome. Clearance is a ceiling, never a key.
What happens when you upload a document.
Every stage is shown live, and every stage leaves a record. No overnight batch.
Text out of the file
PDF, Word, Excel, PowerPoint, CSV, Markdown, images.
Pictures described
A scan with no text is read by a vision model, not skipped.
Classification proposed
The model proposes a tier. An administrator confirms it.
Indexed the way people actually search
By meaning, keyword, full text and spelling — so wording you half-remember still finds it.
Revisions stay answerable
Old versions stay searchable but leave everyday results. A revised figure never competes with the one it replaced.
Search that finds the paragraph, not just the document.
Meaning, keywords and exact wording, all searched together. Nobody picks a mode.
- Every statement links to the paragraph it came from.
- Follow-ups are understood in context, so "and the Trishuli one?" works.
- You are told how much was held back, never what it was.
- Text read from a scan says so, and names its page.
Type it with four typos and it still comes back first.
An audit request becomes a lookup, not an investigation.
Every read, answer and permission change is written down.
Every read, and every refusal with its reason.
- Reads, downloads, searches, questions, permission changes, emergency access — every kind of event.
- Nothing is ever edited or removed. People with history are suspended, not deleted.
- Filter to refusals and "who looked at this" takes seconds.
Checking the rules is a job of its own.
KhojAI Niyam applies your compliance rules to every record and returns a result per rule.
- Rules are written as plain sentences by the people who own them.
- Every result carries the rows it was reached from.
- Licensed as an add-on, for organisations that need it.
Niyam never closes a record. A person decides.
Runs on your infrastructure, with your models.
Each model role points at its own endpoint. Where the thinking happens is a setting.
- Roles: chat, fast, planner, vision, embedding. vLLM, Ollama, LiteLLM, OpenRouter or your own.
- Move the answering model in-house first. Changing the index model means a rebuild, and a mismatch is refused.
- PostgreSQL. Argon2id passwords, and sessions you can revoke instantly.
- In production it refuses to start rather than run insecurely.
Deployed on your infrastructure. Not a subscription service.
Each role is set separately. Only the embedding role costs a rebuild.
Common questions about KhojAI.
Where the system stands today, answered in plain terms.
Does it do SSO or MFA?
Can it run as more than one replica?
How does it handle bulk ingestion?
Can we change the classification tiers?
Could someone prompt-inject past the access rule?
What happens when someone leaves or changes department?
Bring us a real set of documents.
A working session, not a slide deck. Tell us what your people need to find — and what they must not see.
A 45-minute working session · a deployment shape on paper · a pilot against your own documents, under NDA.