Registry › Compare › Airbyte vs Flowise

Airbyte vs Flowise

Both are Grade C and 2.1 points apart, so choose on what you weigh most. Airbyte leads on maintenance; Flowise leads on supply-chain integrity and adoption, and rests on broader evidence. Note: Airbyte's evidence coverage is thinner (coverage C vs B) — its score rests on fewer independent signal types.

C Airbyte 63.5

Open-source data movement for ELT pipelines and AI agents — from APIs, databases & files to warehouses, lakes, and AI applications. Both self-hosted and Cloud.

airbytehq/airbyte · #599 overall · #13 Workflow Platforms · coverage C (2/5)

Choose Airbyte if maintenance matters most.

  • +14.7Maintenance: last push today, against 101d ago
C Flowise 61.4

Build AI Agents, Visually

FlowiseAI/Flowise · #668 overall · #15 Workflow Platforms · coverage B (3/5)

Choose Flowise if supply-chain integrity and adoption matter most.

  • +9.6Adoption: 55.6k GitHub stars against 22.4k
  • +1.9Safety / Integrity: OSSF Scorecard 6.0 against 4.5
  • +1.3Transparency: OSSF Scorecard 6.0 against 4.5
  • B vs CEvidence coverage: 3 of 5 independent signal types, against 2

Where they differ

10.6
Safety / IntegrityFlowise +1.9
12.5
12.3
TransparencyFlowise +1.3
13.6
20.0
MaintenanceAirbyte +14.7
5.3
10.4
AdoptionFlowise +9.6
20.0
-0.6
Runtime calibrationAirbyte +0.2
-0.8

1 dimension identical: Identity 10.8 · Full evidence table

An independent, evidence-based trust comparison of Airbyte and Flowise, two Workflow Platforms projects in the HVTracker registry. Scores come from public, checkable signals — supply-chain provenance, OSSF Scorecard, maintenance, and adoption — not popularity.

Full evidence

Signal Airbyteairbytehq/airbyte FlowiseFlowiseAI/Flowise
HVTrust score 63.5 61.4
Evidence grade C C
Coverage grade C B
Overall rank #599 #668
Rank in Workflow Platforms #13 #15
GitHub stars 22.4k 55.6k
Last updated today 101d ago
Build provenance No No
OSSF Scorecard 4.5 / 10 6.0 / 10
License NOASSERTION NOASSERTION
Downloads — 7.4M/wk
Trust dimensions (points earned)
Safety / integrity / 25 10.6 12.5
Identity & provenance / 18 10.8 10.8
Transparency / 17 12.3 13.6
Maintenance / 20 20.0 5.3
Adoption / 20 10.4 20.0
Runtime capability surface (full matrix)
MCP server Declared Implemented
External providers — 6 — Anthropic, Google Gemini, OpenAI, …
Requires API keys No No
Plugin surface extensions —
Provenance drift — Unknown
Open in the live compare tool → Airbyte profile Flowise profile More Workflow Platforms →

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption, scaled by an evidence-confidence factor. Grade bands: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Signals refresh daily. Full methodology v4.4 →