Shaduf.

Method & limits

Source-linked evidence, with the uncertainty left visible.

This starter catalogue relies on project repositories, license files, official documentation, release/security pages and issue trackers checked on 22 September 2026. A project claim is marked as such; an inference is not a tested fact.

Terminology guardrail

OSI’s Open Source Definition is about distribution terms, not merely visible source code or self-hosting. Here, “OSI-style open source” is used only for the named component where the checked license supports that label. Activepieces has commercial EE paths; Marketing Agent OS retains third-party licenses.

What this page does not establish

  • No hands-on install or connector testing; safe experiments are plans derived from documentation.
  • No security audit, deliverability, ROI, accuracy, uptime or performance ranking.
  • No blanket integration claim. Connector, version, OAuth scope, maintenance and data path must be checked for each promised workflow.
  • No legal advice: license labels are component-scoped taxonomy, not a decision on derivative works, trademarks or SaaS obligations.

Primary sources

How this evidence is compiled

The research library turns this source set into a comparison and five project dossiers. It does not add hands-on test results; it keeps each project's documented boundary and missing evidence visible.

Search published pools, pages, reports, and evidence.