Why docdex exists
A permission-aware knowledge layer, built because the alternatives were expensive, ungoverned, or both.
Every option was expensive, hosted outside the EU, or blind to who was allowed to see what.
docdex started from a simple, annoying problem: every team wanted an AI assistant that actually knew their documents, and every option came with a catch.
Knowledge bases with real permission enforcement existed, but they came with enterprise sales cycles attached. Cheaper alternatives skipped permissions entirely: connect a shared drive, and every document becomes visible to every question, regardless of who is asking.
docdex closes that gap. Connect the documents you already have, whether uploaded directly or synced through a connector, and docdex keeps the exact permissions those source systems already enforce. Everything is hosted in the EU. Any AI client can query it natively, and every answer is filtered to what the asker is actually allowed to see, not what is technically reachable.
docdex is not a new access-control system to configure from scratch. The boundary was already drawn in your source systems. docdex just respects it.
A decade-plus building and shipping software for companies that needed it to just work. docdex grew out of watching teams either overpay for permission-aware search, or quietly give up on permissions altogether.
Four commitments that don’t move.
Not marketing language - the things we optimize for before anything else.
Customer first, not roadmap-first
The people who built docdex answer your support tickets. We ship what makes retrieval more correct for the teams using it, not what fills a slide.
EU sovereignty, by default
Hosted entirely in the EU. Documents, embeddings, and query logs stay on EU infrastructure - not an optional region toggle.
No watered-down free tier
Free runs the same permission-aware retrieval as every paid tier: real ACL sync, real governed answers, not a stripped demo meant to upsell you.
Data protection, not an afterthought
Encrypted in transit and at rest, GDPR-compliant by design, and every answer still filtered to the asker's real permissions.