Integrations
It connects to what you already own.
Storage stays where it is, identity stays where it is, and you choose the assistant. Nothing here requires a migration, a re-permissioning project or a new interface for your staff to learn.
Storage and content
Connected in place, zero-copy
K-Lake reads your document estate where it lives. Nothing is migrated, copied or modified.
Protocols
Connect by protocol, so platform choice is not a constraint.
Platforms tested
Common enterprise storage estates, plus anything speaking the protocols above.
Microsoft 365
Cloud content alongside on-premises shares, in one index.
Content types
Including the formats that usually defeat keyword search.
Identity
Your access model, enforced at query time
Existing permissions are honoured and trimmed when the question is asked. No account remapping, no re-permissioning, no second access model to keep in sync.
Identity providers
Using your existing users and groups.
AI assistants and models
Model-agnostic, over the open MCP standard
Where you use a cloud model, only the retrieved, permission-checked snippet is sent, under your own agreement with that vendor. Where you require full isolation, run a local model and nothing crosses at all.
Cloud assistants
Connected under your own vendor agreement.
Private and local models
For fully sovereign and air-gapped deployments.
Do not see what you need? The protocol and standards-based approach means most gaps are a configuration question rather than a roadmap question. Ask us at [email protected].