01
Manual folder digging
Critical answers are often trapped behind shared-drive memory, inconsistent naming, and too many near-duplicate files.
DERICai is designed to reduce these retrieval risks before they become operational mistakes.
Local-first, security-centric retrieval
Secure operational intelligence, grounded in your files
DERICai indexes the files your organisation already holds, finds the strongest supporting source, and returns answers that stay grounded in evidence.
Local AI as standard. Optional external API use only where trusted. Single machine, LAN, or controlled internet deployment.
Trust boundarySecurity layer
Local AI
Default reasoning path
Admin controls
Access, policy, and deployment
Optional external API
Only outside the trust boundary
Local-first by default
Evidence-grounded answers
Source confirmation when needed
Flexible deployment
Administrative controls built in
Operational friction
Operational knowledge is often buried in files, folders, and fragmented records
Teams waste time searching shared drives, relying on filename memory, opening the wrong document, or manually piecing together answers from service records, assessments, invoices, and certificates. In environments where compliance, maintenance, and operational accuracy matter, bad retrieval is more than inconvenient - it creates risk.
02
Weak or unverified answers
When retrieval is poor, teams either get no answer or an answer they still have to manually verify before acting.
DERICai is designed to reduce these retrieval risks before they become operational mistakes.
03
Poor visibility into the source
Even when someone finds the right document, the path from question to evidence is rarely clean, repeatable, or auditable.
DERICai is designed to reduce these retrieval risks before they become operational mistakes.
Retrieval path
A controlled path from question to evidence
DERICai does not simply generate an answer. It follows a structured retrieval path through indexed files, checks source strength, and can request source confirmation before it continues.
Trust boundarySecurity layer
Local AI
Default reasoning path
Admin controls
Access, policy, and deployment
Optional external API
Only outside the trust boundary
Ask or Explore
Use Ask for guided retrieval and answering, or Explore for a faster file-first path by file, folder, or context.
Search intelligently
DERICai searches indexed operational drives for the strongest supporting source instead of relying on manual memory or folder digging.
Confirm the source if needed
If several files are plausible, DERICai can present the strongest match or a shortlist and let the user confirm the correct source before continuing.
Return a grounded answer
Once the source is strong enough, DERICai answers from the evidence inside the selected file, helping keep results traceable and defensible.
Two working paths
Choose the right path for the job
DERICai supports a guided answer path and a faster file-first path. Both stay close to the source, but they serve different working moments.
Ask
Use Ask when the user wants DERICai to interpret the request, search for the strongest supporting source, and answer from the evidence.
- Guided question flow
- Best when the user wants an answer
- Can request source confirmation
- Optimised for grounded retrieval
Explore
Use Explore when the user wants a faster file-first path by folder, file, or context while staying oriented to the source material.
- Faster file-first path
- Best when the user wants to navigate by folder, file, or context
- Keeps user orientation close to the source material
Security and deployment
Security is part of the product, not a layer added later
DERICai is built for operational environments where control, traceability, and trust matter. Local-first operation is the standard. External model access stays optional and deliberate.
Local-first operation
Local AI is the standard path, keeping core retrieval and reasoning closer to the environment where files live.
Optional external API use
External model access can be enabled only where it is deliberately trusted and appropriate.
Flexible deployment
Run on a single machine, across a LAN, or through controlled internet access.
Administrative and system controls
Controls are built into the platform to support governance, oversight, and controlled operation.
Trust boundary
Optional external API
Outside the default trust boundary and only enabled where deliberately trusted.
User layer
Ask and Explore entry points for guided or file-first retrieval.
Retrieval layer
Controlled search through indexed files, chunks, records, and labels.
Indexed files layer
Operational records, invoices, certificates, assessments, and service evidence.
Admin and controls
Access modes, maintenance, governance, and system-level controls.
Example questions
Example questions DERICai is built to support
Representative operational questions, answered from selected evidence rather than a generic model response.
1 / 5
Closed beta
Designed for operational environments where retrieval needs to be trusted
DERICai is currently offered through a controlled demonstration environment using representative sample data. The goal is to let organisations assess the platform without exposing live operational records.
Privacy handling
Contact submissions are used only to review access requests, respond to enquiries, and maintain an audit trail of contact.
Closed beta note
Demonstration access is limited and reviewed case by case. Outputs should still be verified before being relied upon operationally.
Example environments
Estates and facilities
Housing and property management
Compliance-heavy operations
Contractors and service environments
Teams managing fragmented operational records
Contact us
Contact us
Use this form for general enquiries or to request closed beta access. If you are requesting beta access, add a little context about the environment you want DERICai to support.