goes into searching for answers
56% of employees say some information can only be obtained by asking a colleague. Survey of 12,000 people.
Atlassian, State of Teams 2025ENCLAVE · corporate AI
ENCLAVE answers employees in plain words from company documents and shows the exact passages of your policies, not the “model’s opinion”. Access rights from source systems are applied before the answer is built. It is a corporate alternative to public AI chatbots that your security team can sign off on — inside your perimeter, air-gapped included.
Interface
Employees ask in their own words — ENCLAVE answers with footnotes to source fragments, shows what was hidden by access rights and honestly says “insufficient data” when there is no basis.
Demo data.
Why now
Knowledge is scattered across wikis, trackers, drives and chats. Search returns links, colleagues give different versions, and public AI brings leak risks and made-up answers. Banning it doesn’t work: you need a corporate alternative that is easier to use.
56% of employees say some information can only be obtained by asking a colleague. Survey of 12,000 people.
Atlassian, State of Teams 2025Only 20–24% of respondents have corporate access to AI — the rest take work tasks to public services.
RBC School of Management, 8 October 2026That is the average for a single organisation. And in August 2025, more than 370,000 Grok chats and 4,500 ChatGPT chats ended up in Google search results.
Netskope 2026, ITPro, 12 January 2026How it works
Connectors pull permitted content from Confluence, Jira, SharePoint, Git, S3 and network shares into an index inside your perimeter.
Access rights from source systems come along with the documents. A document with unclear permissions is shown to no one.
For each question, ENCLAVE finds the relevant passages and drops everything the employee is not allowed to see — before the answer is built.
The gist in plain words, footnotes [1][2] to exact passages and document cards. No grounds for an answer — an honest “not enough data”.
Capabilities
Every statement carries a footnote to a specific part of a document: file, system, quote and a link to the original. No precise answer — a list of documents that may help.
Access rights from source systems are applied before the answer is built. A test of 100,000 “employee × document” combinations: 0 unauthorised exposures and 0 wrongly hidden documents.
When you need a document rather than an answer: semantic search returns documents and passages, with no model involved.
Word, Excel and PowerPoint files built from what was found — a summary, a table, a deck for management.
16 connection slots: DeepSeek, OpenAI, Claude, Grok, Gemini, local Ollama and more, plus your own model with an OpenAI-compatible API inside your perimeter.
Overwrites are blocked at the storage level; SIEM export in CSV, CEF, syslog and NDJSON. “View as employee” mode for the security team — recorded in the log.
A graph of topics and entities shows what the knowledge base covers, and benchmark questions show how answer quality changes over time.
The Mac and Windows app connects an employee’s local folders — with the same access rules and audit.
Every build checks that there are no outbound connections. An external model is connected only if you choose one.
Who benefits
Chats and answers with citations, smart passage search, one click to the original source, a desktop app for Mac and Windows.
Connectors and sync, the index, models and platform health, answer quality and alerts, licence, updates and single sign-on.
Fail-closed permissions, “view as employee” mode, an immutable log, SIEM export, air-gapped deployment.
Deployment
enclavectl up; the licence comes as a file4-week pilot
Installation inside your perimeter and connection of the first knowledge system.
Single sign-on, account mapping and a “what does the employee see” check.
Second and third systems, questions from the pilot group, a review of unanswered questions.
Demand, quality, knowledge base gaps, a permissions report for the security team — and a decision.
A closed environment adds one preparation week.
Questions
They shouldn’t: access rights from source systems are applied before the answer is built, and a document with unclear permissions is shown to no one. The permission check has been run on 100,000 “employee × document” combinations — zero unauthorised exposures. In the pilot, we separately check “what the employee sees” on your own accounts.
Yes. ENCLAVE runs in an air-gapped environment with local models, and every build checks that there are no outbound connections. An external model is connected only if you decide so.
ENCLAVE will honestly say “not enough data” and show documents that may help. Such questions are collected into a report — a ready-made list of gaps in your knowledge base.
For up to 25 users, a CPU server with 16–32 cores and 64–128 GB of memory is enough. More users need a GPU — we will size the configuration to the load.
Accuracy depends on your documents, so we don’t promise it in words — we measure it in the pilot on your corpus, with benchmark questions and a review of unanswered ones.
Questions and documents never leave your perimeter, answers rely only on your sources and come with footnotes, permissions are checked before answering, and the log cannot be rewritten.
Not yet — they are on the roadmap. For your own system, you can write a connector with the SDK or upload files.
No. For audit, there is an immutable log, SIEM export and “view as employee” mode, recorded in the log.
ENCLAVE pilot
Leave a request — we’ll agree on the first knowledge system, the pilot group and success criteria.
We’ll contact you at the email you provided to arrange your ENCLAVE pilot.
Other OpenZTA platforms