Data Integration (ELT connectors and data governance)

Where this market publishes its structure

• Airbyte connector registry (connectors.airbyte.com/files/registries/v0/cloud_registry.json + oss_registry.json) machine-readable, 647 connectors (source 592, destination 55; certified 82, community 565); 70 with no dominant vendor domain; 393 linked -> 360 providers; 49 providers Airbyte-certified
• Fivetran connectors (fivetran.com/docs-sitemap.xml -> docs/connectors/{applications,databases,files,events}/*; partner-built-program) machine-readable, 753 connector pages + 8 partner-built destination pages; 38 with no vendor link; 497 linked -> 463 providers; 13 Partner-Built (7 linked)
• Meltano Hub (github.com/meltano/hub _data/meltano extractors + loaders @6098c53ac4) machine-readable, 1,129 plugin variants; 37 without domain_url; 696 linked -> 358 providers; 8 provider-maintained. The hub API omits domain_url, so the data repo is read
• dbt package hub (hub.getdbt.com/api/v1 index + package JSON; publisher website from api.github.com/users/) machine-readable, 379 packages / 113 GitHub owners; 44 dbt Labs' own, 40 individuals, 7 orgs with no website; 13 publishers linked, 5 held
• OpenLineage ecosystem (openlineage.io/ecosystem, OpenLineage/website contents/basepages/ecosystem/index.mdx) machine-readable, 11 hand-written consumer / producer rows, mostly open-source projects: a mention list, not a register (not read)
• Egeria adopters not machine-readable: no adopter or conformance register published (odpi/egeria repo, egeria-project.org)
• Fivetran connector availability / release stage not machine-readable: not in the docs pages; the connector metadata API (api.fivetran.com/v1/metadata/connectors) needs an account key

Own = declares at least one integration itself; covered = visible only because an aggregator, standards body, regulator or partner contract names it; distribution-only = listed only on cloud marketplaces it sells through, a channel reported beside, never counted as its own declared integrations; undeclared = nothing we can read, so no number; declares_compatibility = providers with a `compatible` shape vote, report only (kin, 2026-10-13): never counted as own, never in depth or position.

Taxonomy how this market maps onto apis.io

Derived 2026-10-23 from the 76 providers in this market we could resolve in the catalog. The percentage is the share of those providers carrying each one; it describes the market, not the tag or industry. Tag groups have no page of their own yet, so they are listed unlinked.

share of resolved cohort carrying it; tags >=0.20 & >=3 members (max 12, junk dropped), tag_groups >=0.20 (cooccurrence, non-cross-cutting; max 8), industries >=0.20 (max 6), areas >=0.10 (max 6; areas are keyword-matched and sparse), capabilities L1 >=0.20 (max 8); derive-market-taxonomy.py

Leaders by position (provisional)

Provisional: grouped by position, depth compared within a position only. Distribution (cloud marketplaces) and iPaaS bridges are counted beside position, never inside it. Unknown-builder listings are left out of position shares and counted here.

gravity 2 · other companies invest to build on it

builds-on 29 · publishes apps on other platforms' stores

coverage 5 · reaches banks, carriers, systems or channels (an aggregator)

covered 3 · reached mainly through aggregators

standard 5 · listed by a voluntary standard's own directory

mixed 2 · no single mode dominates

long-tail 1 · reached only through iPaaS bridges

distribution 8 · only sells through cloud marketplaces

undeclared 21 · declares nothing we can read: no number