Developers
Connect your
data sources
Every industrial estate contains a system that exists nowhere else. The built in connectors handle the rest, and the interface is the same one they use.
Three ways to connect
Ready made, custom, or your own
Most estates use all three. They land in the same graph.
Ready made connectors
42 below, 70+ in all
Connect common tools and data sources in minutes, permissions included.
See DirectoryConnect any internal system
Developers
Custom connectors for proprietary tools and your own enterprise data.
Learn MoreBuild and extend with APIs
Developers
Feed data and capabilities into your own tools and MCP workflows.
Learn MoreDirectory · 42 systems
Integrations that work where you work
Search by name, or browse by what they hold. Ask us about a system you do not see here.
42 systems
- 01 · 3Communication
- 02 · 5Email
- 03 · 4Productivity
- 04 · 5Project management
- 05 · 5Development
- 06 · 12Storage
- 07 · 5CRM
- 08 · 3Web integrations
No system by that name in this list
This page lists 42 of the 70+ systems Curiosity connects, and a system of your own connects through the same interface. Ask us about the one you need.
Communication
Find every conversation in context.
Slack
Channels, threads and the files shared in them, next to the ticket a decision closed.
Intercom
Customer conversations and the records behind them.
None listed
Every message and attachment, threaded with the records it mentions.
Outlook
Mail, attachments and contacts in one search.
None listed
Gmail
Mail and attachments from Google Workspace.
None listed
Productivity
Organize work around the records it produces.
OneNote
Notebooks, through the OneDrive or SharePoint that holds them.
None listed
Evernote
Notes, images and attachments, searchable by content.
None listed
Project management
Tasks and issues, with the documents that explain them.
Confluence
Spaces, pages and attachments: the specifications and the runbooks.
Asana
Tasks and their attachments.
None listed
Monday
Boards and the items on them.
None listed
Trello
Boards, lists and cards.
None listed
Development
Code, docs and issues, connected.
Storage
Every file, where it already lives.
Dropbox
Files and folders.
None listed
Amazon S3
Buckets and objects, file contents and metadata alike.
None listed
Azure Storage
Containers, blobs and accounts, with their metadata.
None listed
Google Cloud Storage
Stored objects.
None listed
FTP
Files on FTP servers.
None listed
Local folders
File systems on your own servers, read where they are.
None listed
pCloud
Encrypted files, searched without downloading them.
None listed
CRM
Customers, cases and deals, beside the engineering record.
HubSpot
Contacts, emails and deals.
None listed
Pipedrive
Deals and contact records.
None listed
Web integrations
Outside sources, next to your own.
Web crawler
External web content, crawled and retrieved.
None listed
RSS feeds
Content from the feeds you subscribe to.
None listed
Zapier
Your automations and the tasks they run.
None listed
The system nobody else has heard of
Industrial estates always contain one: a DMS, an ERP, a CRM built in house. The connector interface for it is the same one the built in connectors use, so a custom source is not a second class citizen in the graph.
FAQ
Questions about integrations
How long does it take to set up Curiosity?
A developer install runs on a laptop in minutes. A connected pilot against your real systems usually takes weeks, because the connectors and permission sync come with Studio. Larger enterprise projects depend on how much custom work they need.
Which systems does Curiosity connect to?
More than 70, among them SharePoint, Outlook, Teams, Slack, Confluence, Jira and Amazon S3. For the system that only exists in your building there is a connector SDK. It writes records, relationships and permissions into the same graph the built in connectors fill.
Can I connect custom data?
Yes. The connector SDK brings custom sources such as a DMS, an ERP or a CRM system into the same graph as the built in connectors, with their records, relationships and permissions. See Extensibility.
Does connecting a system copy it?
Yes. The records and files you map are copied into Studio and kept in step by the connector. The source system stays the system of record, and each node links back to it.
How are access permissions handled?
Where a source has permissions, Curiosity syncs them, so a person only sees what the source system would show them. A change in the source reaches Curiosity with the next sync. For a source without permissions, such as an S3 bucket, you choose who may see it when you connect it. See Security.
How does Curiosity keep my data safe?
Access is synced from your source systems and checked per record at query time, so a person only sees what the source would show them. Data is encrypted in transit with TLS and at rest with AES-256 under a key you hold, and sign in runs through your SSO or SAML provider. Searches, views and assistant prompts can be written to an audit log. See the Trust Center.
Does Curiosity run on premises?
Yes, and for most of our customers that is the reason they chose it. On premises or in your private cloud, with local model weights if nothing may leave the building. Air gapped deployments are supported, with an offline license, local models and usage reporting switched off.
Which model does Curiosity use?
The one you choose. 19 providers are built into Studio, among them OpenAI, Anthropic, Google, Mistral, Azure OpenAI, AWS Bedrock and Ollama for open weights on your own servers. Changing it is configuration. Curiosity is not the model. It is what gives the model context.
How do people reach Studio?
In the browser, at an internal address you host, inside the environment your organization already has. Teams can also reach it from the command line, or through MCP from their own agents.
How does pricing work?
Two plans. The developer version is free for up to ten test users, with no time limit for development use. Enterprise Studio is priced for your deployment, on your own infrastructure, starting from fifty users. See Pricing.
Security
Built for security
Made in Germany and built for data sovereignty. Your data stays in your environment, encrypted and access controlled down to the individual record.
On premises or private cloud
Deploy on your own infrastructure or in certified data centers in Europe.
Single sign on and enforced MFA
Access synced to your data sources with relationship based permissions.
Full audit trail
Every query, download and data access logged.
Data residency
Your data stays in the region you choose.
Made in Germany
Built in Munich.
GDPR compliant
European data protection standards.
Your data. Your infrastructure.