1 · Traceable
Answers are designed to cite the document passages they used — for your verification.
We turn your document corpus into a private search-and-answer base: answers link to the passages they came from, and return "not found" when your documents don't support them.
your documents · traceable answers · founding-client rates
THE DIFFERENCE
Answers are designed to cite the document passages they used — for your verification.
Citation coverage is verified programmatically. It helps reduce hallucinations; it does not guarantee accuracy.
When the system cannot find support in the indexed sources, it returns a not-found answer instead of an unsupported one.
SAMPLE CORPUS PREVIEW
Try a sample question below against a small fictional document set. This preview shows how the system finds and cites an answer — not a live connection to your documents.
Response will appear here once you send a request.
SAMPLE ANSWERS
The useful part is not that the system answers quickly. It is that the answer shows where it came from, and refuses to answer when the documents do not support it.
CITED ANSWER
Knowledge Studio · risk: LOW
Found in 2 of 6 indexed agreements (sample corpus):
• 60-day written notice, either party. [msa-2025.md, §11.2]
• 30-day notice during the pilot period. [pilot-addendum.md, §4]
The other four agreements contain no termination clause in the indexed text.
HONEST NOT FOUND
Knowledge Studio · risk: LOW
Not found in the indexed sources (sample corpus).
Nothing in these documents covers a remote-work policy. The system returns "not found" rather than assembling an answer the sources don't support — that is the intended behaviour, not a failure.
Acceptance checks before delivery
Illustrative sample corpus, not a fake client archive. A real knowledge base is tested on your documents and your real questions before acceptance.
WHO THIS IS FOR
Teams sitting on documents nobody can search — contracts, procedures, technical archives, years of internal know-how.
Answers exist somewhere in the archive; finding them takes an afternoon.
In regulated or audited work, an answer without a reference is worthless.
New people re-ask the same questions the documents already answer.
Documents you would not paste into a public AI tool.
Working with legally protected secrets (secret professionnel)? Those need network isolation — see the Private AI Workstation.
WHAT YOU GET
WHERE IT RUNS
On your machine
Local-first by default: the corpus and the index stay on infrastructure you control.
On an existing setup
If you already have suitable infrastructure, we deploy there. Scope confirmed on the call.
"Infrastructure you control" is not the same as network isolation. Any external service, update channel or support access is documented before work starts. If you need a fully isolated, air-gapped setup, that is the Private AI Workstation.
PRICE & ACCEPTANCE TEST
Small corpus pilot from 1 900€ · most complete deployments 2 900-4 500€ after corpus review
OCR, unusual formats, integrations or extra access controls can change the scope — the quote is fixed once the corpus is reviewed.
Founding-client rates — reduced while we build the public portfolio. Limited slots.
Before we build, we agree an acceptance test in writing, with a verifiable criterion — for example: on a set of your real questions, the answers cite the correct source document. If it doesn't meet the agreed criterion, you don't pay the implementation fee. Accuracy of every future answer is not guaranteed — that's why answers are traceable.
FAQ
The default design is local-first: the corpus and index stay on infrastructure you control. Any external service or support access is documented before work starts.
It returns "not found". The system is built to report the absence of support rather than produce an unsupported answer, and citation coverage is checked programmatically before acceptance.
Yes. You remain the data controller: we implement deletion of specific documents or records from the index on your request, and the procedure is written into the DPA we sign before any work on your data.
Text documents index directly; scanned files go through OCR where the quality allows. We confirm what's feasible on your actual corpus during the review — before the quote is fixed.
No tool makes an organisation GDPR-compliant by itself. It can support data minimisation and local processing; you remain the data controller and must have a lawful basis for the personal data in your documents. Castel Studio acts as a data processor under a DPA signed before any work.
Access is configured for the users you approve on your own system; the final access control depends on the agreed deployment. We don't host your corpus.
Prefer email? contact@castel.studio
Indexing may involve personal data. You are the data controller; Castel Studio acts as processor under a DPA signed before any work on your documents. You must have a lawful basis for processing the personal data they contain. Deletion from the index is supported on request.