Comparison · Enterprise search
Curiosity and iFinder by IntraFind
Two German answers to the same constraint
Curiosity adds a context graph and AI layer to secure German enterprise search.
Your data · your environment
Who each tool is for
Different problems, honestly stated
Curiosity
For industrial and regulated teams whose knowledge sits in engineering systems and structured records, where the answer depends on how those records connect, and where the deployment has to run on their own infrastructure.
iFinder by IntraFind
An enterprise search product from IntraFind, a Munich company with more than twenty years in the market. Made in Germany, aligned with GDPR, and deployable on premises, hybrid or in sovereign environments, with search that respects each source’s access rights.
How Curiosity compares
Where the boundary falls
Sovereignty and search that respects access rights are common ground here, and iFinder does them well. Curiosity differs in modeling a typed context graph over structured records rather than concentrating on search itself.
A context graph, not document search
Document retrieval ranks files. Curiosity models the entities and relationships in your data, so what a model reasons over is the connected structure.
Structured records, not just text
Industrial knowledge lives in part data, revisions and serial numbers as much as in documents. Flattening it to text discards the part that matters.
Your infrastructure, your model
Runs where your data lives, with the language model you choose rather than a bundled one.
Side by side
Feature comparison
The same five questions, answered for both.
Deployment
Cloud or self-hosted, ready to use
On premises, hybrid or sovereign
Data model
Managed context layer and knowledge graph
Enterprise search that keeps source rights
Industrial fit
Built for industrial and enterprise teams
German and EU enterprises
Data reach
70+ systems connected, and yours through a connector you write
Many source systems
Residency
EU hosted, or entirely your own infrastructure
Germany and EU
Customization
What your team can change
Your own code, interface, data model and configuration. iFinder by IntraFind as its own documentation described it in October 2026. Where it says Not available, the vendor documents no such capability.
Your own code
C# endpoints, AI tools and tasks, compiled in Studio
JavaScript plugins in web components, custom sources via API
Your own interface
Your own front end in C#, deployed from git
iFinder 6 UI as embeddable web components
Data model
Typed node and edge schemas you define
Not in public documentation
Configuration as code
Every change committed to git, pushed to your remote
Not in public documentation
APIs and SDKs
REST API, C# and Python library, connector SDK
Documented APIs and MCP on the index
AI integration
What AI can build and reach
Whether AI can build on it, who reviews the result, and which models it runs. iFinder by IntraFind as its own documentation described it in October 2026.
AI that builds
Sudo drafts endpoints, tools, schemas and screens
Not in public documentation
Review before it applies
Every change a diff a person approves, in a sandbox
Not in public documentation
Model choice
Any major provider, or an OpenAI compatible endpoint
On premises or cloud LLMs, several models per use
Models on your servers
Open weights on your servers, or air gapped
On premises LLMs, air gapped deployment possible
Assistant permissions
Built in tools search as the user, per record
Answers only from content the user may access
Agent protocols
MCP server and an OpenAI compatible API
MCP server for your own assistants
At Airbus, we developed the next generation of customer support AI assistance tools with Curiosity, enhancing our technical support’s ability to access and navigate vast data from multiple sources, including millions of documents.
Services Innovation Team
Airline Services at Airbus
Enterprise search
Other comparisons in this group
Your data. Your infrastructure.