Skip to Content
Sources

Scan the systemsyou already own.

43 connectors across databases, warehouses and lakehouses, streaming, object storage, collaboration tools, analytics, and public content. Every one is scanned for personal data and secrets; tables in PostgreSQL, MySQL, Databricks, ODBC sources, Delta, Iceberg and files in buckets can also be queried with SQL, masks applied.

43 connectors · straight from the schema
Custom Connector
Sandbox
WordPress
Slack
S3-Compatible Storage
Azure Blob Storage
Google Cloud Storage
PostgreSQL
MySQL
Microsoft SQL Server
Oracle
Apache Hive
Databricks
Snowflake
Dremio
MongoDB
Neo4j
Power BI
Tableau
Confluence
Jira
Jira Service Management
Notion
Email
YouTube
Reddit
Iceberg REST Catalog
DuckLake
Trino / Starburst
ODBC
Amazon Athena
Google BigQuery
Amazon Redshift
Apache Kafka
Elasticsearch
OpenSearch
Meilisearch
Mounted Folder
Microsoft 365
Google Workspace
Dropbox
Hugging Face
Git Repository
Custom Connector
Sandbox
WordPress
Slack
S3-Compatible Storage
Azure Blob Storage
Google Cloud Storage
PostgreSQL
MySQL
Microsoft SQL Server
Oracle
Apache Hive
Databricks
Snowflake
Dremio
MongoDB
Neo4j
Power BI
Tableau
Confluence
Jira
Jira Service Management
Notion
Email
YouTube
Reddit
Iceberg REST Catalog
DuckLake
Trino / Starburst
ODBC
Amazon Athena
Google BigQuery
Amazon Redshift
Apache Kafka
Elasticsearch
OpenSearch
Meilisearch
Mounted Folder
Microsoft 365
Google Workspace
Dropbox
Hugging Face
Git Repository
Full catalog

All 43 connectors

Search by name, category, or capability. Every entry links to its configuration reference on the docs site: required fields, auth, and a worked example.

Source Catalog
Pick connector by category
43 Matches

Graph Databases

Graph-native stores with node and relationship traversal.

1 Sources

Streaming

Event streams and message brokers sampled for content.

1 Sources

Web & UGC

Public-facing websites and user-generated content.

1 Sources

Analytics & BI

Dashboards, reports, and business intelligence assets.

2 Sources
By category

Where the evidence comes from

Connectors are grouped by what they are, not by vendor. Counts come straight from the schema, so this page can never drift from what the product actually supports.

CategoryConnectors
  • Warehouse & Lakehouse14

    Analytical compute platforms and catalog-first ingestion.

  • Databases9

    Operational and document stores for row and collection scans.

  • Collaboration9

    Team communication and workspace activity streams.

  • Other3

    Connectors you write yourself, direct file uploads and mounted folders.

  • Social Media2

    Social and video platforms with public posts and transcripts.

  • Analytics & BI2

    Dashboards, reports, and business intelligence assets.

  • Graph Databases1

    Graph-native stores with node and relationship traversal.

  • Code Repositories1

    Version-controlled source, configuration, and documentation.

  • Streaming1

    Event streams and message brokers sampled for content.

  • Web & UGC1

    Public-facing websites and user-generated content.

Every connector

What they all have in common

The system on the other end changes. What Classifyre does with what it reads does not.

Assets, not just rows

Each connector yields assets with source metadata attached (owner, path, timestamps), so a finding always carries where it came from.

Assets & metadata →

Test before you scan

Every source can be dry-run from the app: check the credentials, see what it would read, and only then commit to a full scan.

Testing sources →

Sampling that bounds cost

Large tables and files are read through sampling windows with a per-asset cursor, so a scan reads a bounded slice instead of everything.

Sampling →

Cross-source fingerprints

The same value showing up in two different systems gets linked by identity, which is where most real investigations actually begin.

How it works →

Missing the one you need?

Connectors are plugins, and the project is open source, so the answer is either a pull request or a conversation. Enterprise customers get sources built for their industry's systems by our engineers.