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 →39 connectors across databases, warehouses and lakehouses, streaming, object storage, collaboration tools, analytics, and public content, all feeding one evidence stream.
39 connectors · straight from the schemaSearch by name, category, or capability. Every entry links to its configuration reference on the docs site: required fields, auth, and a worked example.
Operational and document stores for row and collection scans.
Graph-native stores with node and relationship traversal.
Analytical compute platforms and catalog-first ingestion.
Version-controlled source, configuration, and documentation.
Event streams and message brokers sampled for content.
Public-facing websites and user-generated content.
Social and video platforms with public posts and transcripts.
Team communication and workspace activity streams.
Dashboards, reports, and business intelligence assets.
Sources discovered in schema that have not been categorized yet.
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.
Analytical compute platforms and catalog-first ingestion.
Operational and document stores for row and collection scans.
Team communication and workspace activity streams.
Social and video platforms with public posts and transcripts.
Dashboards, reports, and business intelligence assets.
Graph-native stores with node and relationship traversal.
Version-controlled source, configuration, and documentation.
Event streams and message brokers sampled for content.
Public-facing websites and user-generated content.
Sources discovered in schema that have not been categorized yet.
The system on the other end changes. What Classifyre does with what it reads does not.
Each connector yields assets with source metadata attached (owner, path, timestamps), so a finding always carries where it came from.
Assets & metadata →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 →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 →The same value showing up in two different systems gets linked by identity, which is where most real investigations actually begin.
How it works →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.