Broadcaster
A broadcaster whose staff spend measurable time finding internal guidance that already exists in documentation
Staff waste hours searching internal documentation for answers that already exist - and a general-purpose AI assistant cannot be trusted because it would show people content they are not cleared to see. Custom Knowledge Assistant answers directly from your organisation's documents, enforces per-user access control, and combines hybrid retrieval with a stateful agent so the answers are grounded and the access is governed.

Enter the demo password to launch the interactive demo.
Don't have a password? Ask us for one and we will send it over.
Request demo accessKnowledge is locked inside documents, intranets and wikis that are too large to search manually and too sensitive to hand to an unrestricted AI. Teams resort to asking colleagues, who either know from memory or have to search themselves - the same cost, paid again and again by different people.
A general-purpose assistant solves the retrieval problem but creates a worse one: it cannot distinguish between a document that is public and one that is restricted, so deploying it exposes protected material to whoever asks the right question. The only safe answer is a system that retrieves and answers within the boundaries of what each user is actually allowed to read.
This is relevant if you are:
A broadcaster whose staff spend measurable time finding internal guidance that already exists in documentation
A telco with layered access policies who needs an AI assistant that respects those policies rather than overriding them
Combines FAISS dense retrieval and BM25 keyword search, then fuses the rankings with Reciprocal Rank Fusion before generation.
Runs as a multi-stage StateGraph agent with tool looping, robust state management, guarded message flow, and max-step protection.
Supports knowledge-base retrieval, email and site metadata search, deterministic MBMS/FeMBMS bandwidth calculations, and structured quality feedback.
Synchronizes FAISS indexes from Amazon S3 using ETag-driven cache invalidation to keep the local store aligned with the latest uploaded corpus.
Restricts unauthenticated users to public collections while allowing authenticated users to reach protected private data sources.
Uses a separate zero-temperature LLM pass to review responses and emit structured feedback metrics for monitoring and improvement.
Most enterprise knowledge tools are either open - so they ignore access policy - or siloed per team, so the person who needs an answer from a different department cannot get it. Custom Knowledge Assistant enforces the access boundary at retrieval rather than at the UI, which means the model never sees what the user is not allowed to see. Hybrid retrieval with RRF means it does not choose between keyword precision and semantic recall: it uses both and lets the ranking decide.
Custom Knowledge Assistant is in controlled testing. The demo on this page is available to selected partners on invitation - which is exactly what the Testing status commits us to - and the password gate you passed through is the access control mechanism in practice.
This is an early first-draft deployment intended for initial testing and iteration, and two boundaries follow from that. The current phase has no internet access, so the agent cannot run live web searches or pull real-time external data, and the architecture is text-only: it does not embed or reason over images, which keeps retrieval to text documents and metadata.
The next step is to run the assistant against a customer's actual document corpus and access policy, so quality and boundary enforcement can be measured on real material.
Tell us what you need to keep private, what access structure you have, and we will tell you what a pilot against your corpus would involve.