Skip to content

Connectors

Your sources stay where they are.
DeepView plugs into them.

Documents, conversations, tickets or databases: DeepView connects to the tools where your information already lives, and answers by citing the original source.

Supported sources

Your company's tools, in a single engine

Documents & files

Libraries, shared drives and network folders, re-read every night: only what changed is processed again.

  • SharePoint
  • Google Drive
  • Box
  • Dropbox
  • Windows network shares
  • Server folders
  • S3 storage
  • Upload from your computer

Messaging & collaboration

Threads, emails and documentation pages, with the files they share.

  • Microsoft Teams
  • Slack
  • Outlook
  • Gmail
  • Confluence
  • Notion

Tracking, support & CRM

Tickets, requests and customer records, with their history and comments.

  • Jira
  • GitHub
  • GitLab
  • Zendesk
  • Salesforce
  • HubSpot

Databases

Queried live and read-only: filters, counts and totals are computed by the database, never estimated.

  • PostgreSQL
  • SQL Server
  • MySQL
  • Oracle

Web & business tools

Your internal or public websites, and any tool exposed through the MCP protocol, allowed function by function.

  • Web crawler
  • MCP tools

Two ways to connect

Index what is read, query what is computed

Synchronised

Read, understood, kept up to date

Documents, pages and conversations are analysed and indexed inside your environment. Sources are re-read automatically; only what changed is processed again.

  • Search across content, tables and figures included
  • Answers cited down to the passage
  • Updated every night
Queried live

Consulted when the question is asked

Databases and MCP tools are queried when a question calls for them, read-only. Nothing is copied.

  • Always current
  • Counts, totals and filters run by the source
  • No write access, ever

Who connects what

An integration set up once, sources chosen per project

The administrator sets up the integration

Once for the whole organisation. Secrets are encrypted and stay in your environment.

The project lead chooses the source

They sign in with their own account, pick the library, folder or table, and share it with their project.

Members ask their questions

Without needing rights on the original tool. Other projects see none of it.

Access is granted as narrowly as possible: site by site for SharePoint, team by team for Teams, mailbox by mailbox for email. A restricted page stays invisible to anyone who cannot see it.

Formats

What DeepView can read

  • PDF, scanned ones included
  • Word
  • PowerPoint
  • Excel and CSV
  • HTML and Markdown
  • XML

Tables, table notes, diagrams and charts are understood with their layout; figures are described so that search can find them.

The other way round

DeepView inside your other assistants

A project can be opened to an MCP-compatible AI assistant: your teams query DeepView without leaving the tool they work in.

  • Off by default, opened project by project
  • Excerpt search only, or full answers
  • Personal tokens, time-limited and revocable
  • Access log the administrator can review

Your tool is not on the list?

Tell us which one: we will work out with you how to connect it, through a dedicated connector or through MCP.