Skip to content

Integrations

Connect your knowledge
without rebuilding
the stores.

souveraen.ai reads the stores you already have, carries over their permissions and makes the contents searchable together. The documents stay where they are, and every change is picked up.

  • Use the systems you already have
  • Permissions carried over automatically
  • Set up in minutes
SharePoint, OneDrive, Exchange, databases and file servers flow into a shared knowledge collection and from there become searchable, permission-based and always current

How an integration works

How a store
becomes a source.

You approve a store, souveraen.ai reads it together with its permissions. After that it appears in answers, but only for the people who may already open it.

More about the set-up
  1. 1

    Connect a source

    A service account with read permissions and the approved path or tenant are enough. The store stays where it is.

  2. 2

    Carry over the permissions

    The source's permissions are read in with it: NTFS permissions, store and area permissions, mailbox access.

  3. 3

    Index the contents

    Text, tables and structure are lifted out of the document and given a title, version, author and period of validity.

  4. 4

    Link them together

    Keyword search, vector search and local re-ranking work together across every source in the hybrid index.

  5. 5

    Use it at once

    Your team asks questions and gets sourced answers with the exact passage, as far as the permissions that already apply will allow.

Your enterprise ecosystem

Connected to the stores you already have.

souveraen.ai reads the systems where your knowledge already sits, whether on-premises, in the cloud or in hybrid environments.

See every integration

Documents & collaboration

SharePoint, OneDrive, Exchange, Nextcloud and more. Permissions, versions and structures are carried over in full.

Databases

PostgreSQL, MSSQL and more. Connected through a read replica or approved views, so only data you have deliberately opened reaches the search.

File servers (SMB)

Network drives and file stores. NTFS permissions, folder structures and changes are taken into account.

Further systems over MCP

Over the open MCP standard you connect any tools and line-of-business applications. Build your own connectors or use ones from the Marketplace.

An open standard, reviewed servers.

MCP for your company.

With open MCP support you connect souveraen.ai to any tools, data sources and line-of-business applications. Ready-made integrations sit in our MCP Marketplace. Every approved server runs through an internal broker: one way in instead of many endpoints, every call logged.

  • An open standard
  • Your own MCP servers
  • Live only after approval
Internal tools, line-of-business applications, your own data sources, external services and community integrations run through a shared MCP broker to agents, search, analysis and automations

Benefits at a glance

More impact from the systems you already have.

Without rebuilding and without a migration, the stores you already have deliver the answers.

No data migration

Your data stays in the systems it already lives in. Structure, location and permissions do not change.

Permissions are carried over

What someone may access is checked again on every query.

Information that stays current

Changes in the source systems are kept in sync continuously; deleted content disappears with them.

New systems can join

Connectors, the Connector-SDK and the open MCP standard attach another system in minutes.

Technical details

Which sources souveraen.ai reads.

Each of these sources arrives with its own permissions, from the cloud store to the network drive.

See every integration

SharePoint & OneDrive

  • Cloud
  • Permission-based
  • Incremental

Exchange

  • Cloud
  • Permission-based
  • Automatic

File servers (SMB)

  • On-premises
  • NTFS
  • Secure

Databases

  • On-premises
  • Approved views
  • Flexible

Confluence

  • Cloud
  • REST API
  • Automatic

Further systems (MCP)

  • Open standard
  • Marketplace
  • Your own servers

Before the first full run, a test run on ten files checks access, permission carry-over and extraction. Every integration meets the same conformance test for permission carry-over and for change and deletion handling.

Set-up and control

The collection stays current and checkable.

Adding a source is an administrative task of minutes, not a project of its own. What happens afterwards stays visible.

  • New versions replace the old one; documents still in force and those superseded stay distinguishable.
  • If a source is deleted, its passages, vectors, caches and derived memory entries disappear with the next run.
  • Every run reports far-reaching read permissions and flags stores that have been opened unusually widely.
  • Content you are not permitted to see does not appear at all, not as a title, not as a preview and not as a hit count.
  • Path, service account and scope are maintained in administration; the state of every source is visible there.
  • Errors are logged per source and so stay visible; no run fails quietly.

Systems often mentioned

The systems we talk about most often.

These marks show which stores come up in conversations. What binds is the table of source systems.

  • SharePoint
  • OneDrive
  • Exchange
  • Teams
  • Confluence
  • Jira
  • Notion

Product marks of the respective vendors, here only for orientation. They are not partnerships, certifications or confirmed compatibilities. Which permissions are carried over and how the set-up works is in the table above.

Common questions

What your IT team wants to know before the first run.

Do we have to rebuild our stores?

No. souveraen.ai reads the stores you already have through a service account with read permissions. Structure, location and permissions stay as they are.

Are documents sent to an external service?

No. Extraction, embedding and the answer all run on the appliance in your own building. There is no model interface at an external provider.

What happens if someone is removed from a group?

The next query checks group membership again. Content for which the permission has lapsed no longer appears, without waiting for an index run.

How does the Microsoft 365 integration work?

In the introduction project we set up a service account in your tenant and you grant it approval for read access. After a test run on ten files, the sync with SharePoint, OneDrive and Exchange runs.

Can we connect a system of our own?

Yes, through the Connector-SDK. Every integration reads only by default, works with a dedicated service account and must meet the conformance test for permission carry-over and for change and deletion handling.

Can anyone in the company connect tools from the MCP Marketplace?

No. The Marketplace shows reviewed integrations; one of them goes live only after your approval. Every approved server runs through the internal broker, and every call is logged. There is no self-service shop from which someone can connect something unnoticed.

Integrations

Connect your knowledge.

We look at your stores, permissions and systems and tell you what can be given a sourced answer on day one.