EU hosted
The default. Your documents are stored and processed in the EU, and they are not used to train models.
How it works
Memory layer
A memory layer sits between your documents and the AI models your organisation uses. It reads your material once and organises it into a structured memory: the sources, summaries built across them, and an index over both. When someone asks a question, nothing searches everything again. The question goes to the memory, and the memory returns the exact material that answers it, with the source attached. One memory serves every person and every agent, so the organisation answers from the same knowledge rather than from a dozen private copies of it.
The problem
Your organisation already knows the answer, but it's spread across thousands of documents that today's AI tools can only read a few of at a time, so they answer from fragments and can't show you where the answer came from.
Use cases
Decision support
Leadership and analysts ask the question a decision rests on and get an answer that quotes the contract, report or policy it came from.
Internal knowledge
The answer no longer depends on finding the one person who knows where to look. Everyone asks the same shared memory, and every answer names its source.
Assistants
A support or copilot chat grounded in your own documents: it answers from the passage it found, and says so when your documents do not cover the question.
Agents
Automated workflows call the API or MCP mid-task and get a cited answer back, limited by the same permissions as a person.
Permissions
Hippocampus has permission controls, allowing organisations to control what documents employees can view. Based on role, function or manual edits.
As the head of procurement: what notice period applies if we end the logistics supplier agreement?
90 days' written notice. Amendment 2, section 7.3, replaced the original 30 days.
amendment-2-2025.pdf, page 2
As a project coordinator: what notice period applies if we end the logistics supplier agreement?
The documents you can read do not include the supplier agreement. The purchasing policy says changes to supplier contracts go through procurement.
purchasing-policy-2025.pdf, page 3
Deployment and security
EU hosted by default, in your own cloud, or fully on-premises. The product is the same in all three, and your documents are not used to train models.
The default. Your documents are stored and processed in the EU, and they are not used to train models.
The same product, run in your organisation's own cloud.
The same product, run fully on your own hardware.
Use the model your organisation already approved: Claude, GPT, Gemini or an open-weight model. Switch without re-ingesting anything.
Fits your stack
Hippocampus supports PDF, DOCX and MD files.
Agents connect over MCP, with streamable HTTP and OAuth, and get cited answers mid-task.
Ask questions and walk the document tree from your own code.
A ready-to-use workspace: add your documents and start asking, with nothing to build or set up.
Customer stories
Purpose: Ensure that care providers follow procedure and law at the point of care. Chat box in staff's phones.
Result: Accurate where their earlier AI tools failed. 50-90% fewer tokens per query at quick response times.
Purpose: Analyze and cross-reference existing external clinical trials to guide their R&D spending.
Result: 16 of 16 questions answered correctly. Traditional AI failed the same corpus.
Questions
Yes, SAML and OIDC single sign-on are part of the Corporate package. Sign-in runs on Google Identity Platform with a separate tenant per workspace, and signed tokens are checked by the application and again by each backend service.
Yes, audit export is part of the Corporate package. Inside the service every security-relevant operation on the document store goes to a numbered, hash-chained audit log, and each answer resolves to a byte range in a named source, so access can be traced to the passage.
Yes, on Corporate the service runs on a shared or a dedicated EU stack, chosen and set up with you; Free and Starter run on the shared EU stack. On any stack each workspace has its own search collections, and its identity is bound into every encryption, so one workspace's data cannot be decrypted as another's.
Yes, every customer is covered by our standard data processing agreement, accepted with the terms of service, and Corporate customers can negotiate a separate one. It meets Article 28 of the GDPR, makes the sub-processor list part of the agreement and commits us to breach notice within 72 hours. Read it on the data processing agreement page.
You bring a set of documents and the questions you want answered, and we run them live during the call. To book one, write to letstalk@thalius.ai.
Yes, Hippocampus can run in your own cloud, fully on-premises or in any other environment you control, as part of the Enterprise package. Own hosting is set up with us, the product is the same as on our EU cloud, and the API and MCP differ only in the base URL. With own hosting, every component including model inference can run inside your environment.
Yes. Hippocampus works with any language model. You choose which model answers, set per workspace; on Corporate you can use your own model key or have administrators choose the models. Changing the answer model needs no re-import.
Bring a set of documents and the questions you want answered, and we will run them live during the call.