Fivetran vs Dagster

Agent access

1. ai-native userPoint an agent at llms.txt or agent-oriented docs

   weight 2 · round to Dagster
   Fivetran✓fullprobed8/10

   Direct probe evidence confirms Fivetran serves a working llms.txt at the root domain (HTTP 200) with structured content describing the platform, letting an agent be pointed directly at it. Missing for 10: no additional agent-oriented docs format (e.g., docs.md returned 404) or broader llms-full.txt coverage beyond the single file.

   • [probe] “PROBE llms.txt: HTTP 200 at https://fivetran.com/llms.txt # Fivetran Documentation > Fivetran is a fully managed data movement platform tha…”
   • [probe] “PROBE docs-md: HTTP 404 at https://fivetran.com/docs.md”

   proof ↗⚑ flag

   Dagster✓fullprobed9/10

   Dagster confirms a live llms.txt file (probe returned HTTP 200 with structured doc links) and also publishes agent-oriented docs like a dedicated AI skill for coding agents and an MCP server for Dagster+. missing for 10: no independent/community corroboration that agents successfully use the llms.txt file in practice.

   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.dagster.io/llms.txt # Dagster Docs ## Docs - [Changelog](about/changelog): Review detailed update…”
   • [claimed-docs] “Dagster maintains an AI skill that gives coding agents better context and patterns for building Dagster projects.”
   • [claimed-docs] “The Dagster+ MCP server allows you to access information and take actions in your Dagster+ deployment within an AI session.”

   proof ↗⚑ flag

2. ai-native userRun the product headlessly / in CI for automation

   weight 2 · round to Dagster
   Fivetran✓fullprobed7/10

   Fivetran exposes a documented REST API for managing pipelines/connectors programmatically and a Connector SDK for deploying custom connectors as code, both of which are usable headlessly (e.g., in CI/CD pipelines); a runtime probe confirms the API is live and functioning with key-based auth, supporting non-interactive automation. missing for 10: no explicit CI/CD pipeline examples, official CLI tool, or Terraform/IaC provider documentation demonstrating end-to-end headless orchestration.

   • [claimed-docs] “Set up and scale your data pipeline, and manage your Fivetran account programmatically using the Fivetran REST API.”
   • [claimed-docs] “Fivetran REST API”
   • [claimed-docs] “Fivetran’s Connector SDK allows you to develop a custom data connector using Python and deploy it as an extension of Fivetran.”
   • [probe] “PROBE runtime (recorded 2026-09-08): Fivetran's documented REST API is live and cleanly auth-gated — a keyless GET https://api.fivetran.com/…”

   proof ↗⚑ flag

   Dagster✓fullprobed8/10

   Dagster ships a CLI (dg, dagster) and Docker deployment options with a webserver/daemon architecture designed for scheduled, sensor-driven, or CI-triggered runs, and probe evidence confirms the CLI installs and scaffolds/runs projects keylessly end-to-end. missing for 10: no first-party doc excerpt specifically describing a CI/CD pipeline integration (e.g. GitHub Actions example) or headless-run flags beyond dev server, and no independent report of running Dagster fully headless in a CI pipeline.

   • [claimed-docs] “A typical Dagster Docker deployment includes a several long-running containers: one for the webserver, one for the daemon, and one for each …”
   • [claimed-docs] “Schedules enable automated execution of jobs at specified intervals.”
   • [claimed-docs] “Sensors enable you to take action in response to events that occur either internally within Dagster or in external systems.”
   • [probe] “PROBE runtime (recorded 2026-09-08): the full agent-builds-a-project path ran keylessly end to end — `uvx create-dagster@latest project pa-p…”
   • [probe] “PROBE runtime (recorded 2026-09-08): the official dagster CLI installed keylessly from pypi via uvx and printed 'dagster, version 1.13.21'.”
   • [probe] “official CLI documented at https://docs.dagster.io/api/clis/dg-cli/dg-cli-configuration”

   proof ↗⚑ flag

3. ai-native userConnect an agent via an official MCP server

   weight 3 · round drawn
   Fivetran✓fullclaimed7/10

   Fivetran ships an official MCP server (github.com/fivetran/fivetran-mcp) that lets an agent query sync status read-only, and optionally unlock write/delete operations via FIVETRAN_SCOPE, plus manage connections — squarely matching the story. Missing for 10: independent/hands-on verification of the MCP server, and richer first-party documentation (e.g., official docs page rather than just a README) describing setup and supported clients.

   • [claimed-docs] “It allows you to ask read-only questions like "when was the last time my postgres connection completed a sync?" and "are any of my connectio…”
   • [claimed-docs] “Set `FIVETRAN_SCOPE` to `read/write` or `read/write/delete` to unlock write and delete operations”
   • [claimed-docs] “Copy existing Fivetran connections to a new destination. Keep their configs and schemas intact or modify them as you like.”

   proof ↗⚑ flag

   Dagster✓fullprobed7/10

   Dagster is not itself an agent but a data orchestration platform, so an official MCP server is a valid axis; Dagster documents a first-party 'Dagster+ MCP server' that lets AI sessions access and act on a Dagster+ deployment, confirmed by both docs and a probe hit. Missing for 10: independent/hands-on verification of the MCP server working, and clarity on whether it covers OSS Dagster or only the paid Dagster+ tier.

   • [claimed-docs] “The Dagster+ MCP server allows you to access information and take actions in your Dagster+ deployment within an AI session.”
   • [probe] “official MCP server documented at https://docs.dagster.io/getting-started/ai-tools/dagster-mcp”

   proof ↗⚑ flag

4. ai-native userUse an official CLI

   weight 2 · round to Dagster
   Fivetran—none0/10

   No evidence of an official Fivetran CLI; the evidence pack only documents a REST API, Connector SDK (Python), and MCP server, none of which constitute a CLI tool. Since a data-integration platform could plausibly ship a CLI (as many do for connector/config management), the axis applies but is unmet.

   • [claimed-docs] “Set up and scale your data pipeline, and manage your Fivetran account programmatically using the Fivetran REST API.”
   • [claimed-docs] “Fivetran’s Connector SDK allows you to develop a custom data connector using Python and deploy it as an extension of Fivetran.”
   • [claimed-docs] “Fivetran REST API”

   proof ↗⚑ flag

   Dagster✓fullprobed9/10

   Dagster ships official CLIs (`dagster`, `create-dagster`, `dg`) documented and verified to work keylessly end-to-end via runtime probes, including scaffolding, project dev server, and CLI version output — directly supporting agentic/CLI-driven workflows, further reinforced by a dedicated AI skill and MCP server for agent integration. Missing for 10: no independent third-party review specifically praising CLI usability for AI-native/agentic workflows beyond Dagster's own docs and probes.

   • [claimed-docs] “you can scaffold a new project with the create-dagster CLI (recommended)”
   • [claimed-docs] “Dagster maintains an AI skill that gives coding agents better context and patterns for building Dagster projects.”
   • [claimed-docs] “The Dagster+ MCP server allows you to access information and take actions in your Dagster+ deployment within an AI session.”
   • [claimed-docs] “uvx create-dagster@latest project my-project”
   • [probe] “official CLI documented at https://docs.dagster.io/api/clis/dg-cli/dg-cli-configuration”
   • [probe] “PROBE runtime (recorded 2026-09-08): the full agent-builds-a-project path ran keylessly end to end — `uvx create-dagster@latest project pa-p…”
   • [probe] “PROBE runtime (recorded 2026-09-08): the official dagster CLI installed keylessly from pypi via uvx and printed 'dagster, version 1.13.21'.”

   proof ↗⚑ flag

5. ai-native userDrive the product through a documented public API

   weight 3 · round to Fivetran
   Fivetran✓fullprobed8/10

   Fivetran documents a full REST API for provisioning and managing connectors/pipelines programmatically, corroborated by a live runtime probe showing the API is reachable and correctly auth-gated. There's also an official Connector SDK and community-referenced MCP server enabling agentic interaction. Missing for 10: independent developer corroboration of full API coverage/reliability and a published OpenAPI spec (probe found none), and one community comment notes API unreliability.

   • [claimed-docs] “Set up and scale your data pipeline, and manage your Fivetran account programmatically using the Fivetran REST API.”
   • [claimed-docs] “Fivetran REST API”
   • [claimed-docs] “Connect Cards”
   • [probe] “PROBE runtime (recorded 2026-09-08): Fivetran's documented REST API is live and cleanly auth-gated — a keyless GET https://api.fivetran.com/…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://fivetran.com/openapi.json, https://fivetran.com/swagger.json, https://fivetran.com/api/opena…”
   • [community] “Unrelated to the article itself but Fivetran has the worst possible product from a developer perspective, their APIs are unreliable and will…”

   proof ↗⚑ flag

   Dagster~partialprobed6/10

   Dagster exposes a documented CLI (dg/dagster CLI, verified runtime-installable) and Python API for defining/running assets, plus a Dagster+ GraphQL/MCP surface for AI agents, and even a first-party AI skill for coding agents. However, there is no evidence of a general documented public REST/OpenAPI API (probe found only 404s for openapi/swagger endpoints), so 'driving the product' programmatically is limited to CLI/Python SDK and Dagster+-specific interfaces rather than a universal documented public API. missing for 10: a documented REST/OpenAPI-style public API, independent confirmation of API stability/coverage, and evidence of non-Dagster+ users driving core OSS orchestration purely via API without UI.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.dagster.io/openapi.json, https://docs.dagster.io/swagger.json, https://docs.dagster.io/…”
   • [probe] “official MCP server documented at https://docs.dagster.io/getting-started/ai-tools/dagster-mcp”
   • [probe] “official CLI documented at https://docs.dagster.io/api/clis/dg-cli/dg-cli-configuration”
   • [probe] “PROBE runtime (recorded 2026-09-08): the full agent-builds-a-project path ran keylessly end to end — `uvx create-dagster@latest project pa-p…”
   • [probe] “PROBE runtime (recorded 2026-09-08): the official dagster CLI installed keylessly from pypi via uvx and printed 'dagster, version 1.13.21'.”
   • [claimed-docs] “The Dagster+ MCP server allows you to access information and take actions in your Dagster+ deployment within an AI session.”
   • [claimed-docs] “Dagster maintains an AI skill that gives coding agents better context and patterns for building Dagster projects.”

   proof ↗⚑ flag

6. ai-native userIssue scoped/least-privilege API credentials for an agent

   weight 2 · round to Fivetran
   Fivetran~partialprobed5/10

   Fivetran's MCP server supports a FIVETRAN_SCOPE setting (read-only vs read/write vs read/write/delete) letting operators limit what an agent-facing credential can do, and Fivetran also documents role-based access control and API-key authentication for its REST API. However, there's no documented fine-grained, per-agent scoped credential issuance (e.g., token minting with custom permission sets) beyond this coarse read/write/delete toggle. Missing for 10: granular least-privilege credential scoping beyond three tiers, agent-specific credential lifecycle/rotation docs, and independent verification of RBAC granularity.

   • [claimed-docs] “Set `FIVETRAN_SCOPE` to `read/write` or `read/write/delete` to unlock write and delete operations”
   • [claimed-docs] “Role-based access control”
   • [claimed-docs] “Fivetran REST API”
   • [probe] “PROBE runtime (recorded 2026-09-08): Fivetran's documented REST API is live and cleanly auth-gated — a keyless GET https://api.fivetran.com/…”

   proof ↗⚑ flag

   Dagster—none0/10

   No evidence of scoped or least-privilege API credential/token issuance for agents; the MCP server and CLI docs describe access/action capabilities but not credential scoping or permission management. Missing for 10: any mention of API tokens, scoped credentials, RBAC for agent access, or least-privilege key issuance mechanisms.

   ⚑ flag

7. ai-native userBuild against official SDKs

   weight 2 · round to Dagster
   Fivetran✓fullprobed7/10

   Fivetran documents an official Connector SDK for building custom Python connectors, a full REST API for programmatic pipeline management, and a first-party MCP server (fivetran-mcp) enabling AI agents to query and manage connections — directly supporting AI-native, agentic build patterns. Missing for 10: broader official client libraries in multiple languages, independent hands-on validation of the SDK/MCP server's agentic reliability, and detailed docs on SDK versioning/support commitments.

   • [claimed-docs] “Fivetran’s Connector SDK allows you to develop a custom data connector using Python and deploy it as an extension of Fivetran.”
   • [claimed-docs] “Set up and scale your data pipeline, and manage your Fivetran account programmatically using the Fivetran REST API.”
   • [claimed-docs] “Fivetran REST API”
   • [claimed-docs] “It allows you to ask read-only questions like "when was the last time my postgres connection completed a sync?" and "are any of my connectio…”
   • [claimed-docs] “Set `FIVETRAN_SCOPE` to `read/write` or `read/write/delete` to unlock write and delete operations”
   • [claimed-docs] “Copy existing Fivetran connections to a new destination. Keep their configs and schemas intact or modify them as you like.”
   • [probe] “PROBE runtime (recorded 2026-09-08): Fivetran's documented REST API is live and cleanly auth-gated — a keyless GET https://api.fivetran.com/…”

   proof ↗⚑ flag

   Dagster✓fullprobed8/10

   Dagster ships a well-documented Python SDK (`dagster`/`dg` CLI, asset/job/schedule APIs) plus AI-specific tooling — a dedicated AI skill for coding agents and an official MCP server — and runtime probes confirm the SDK/CLI actually installs and scaffolds/runs projects keylessly end-to-end. Missing for 10: independent third-party corroboration of SDK ergonomics for AI agents specifically, and no documented OpenAPI/REST spec (probe found only 404s) to complement the Python SDK.

   • [claimed-docs] “Dagster maintains an AI skill that gives coding agents better context and patterns for building Dagster projects.”
   • [claimed-docs] “The Dagster+ MCP server allows you to access information and take actions in your Dagster+ deployment within an AI session.”
   • [claimed-docs] “You can scaffold Dagster Component definitions in your project from the command line with the dg scaffold defs command”
   • [claimed-docs] “import dagster as dg@dg.assetdef hello(context: dg.AssetExecutionContext): context.log.info("Hello!")@dg.asset(deps=[hello])”
   • [claimed-docs] “uvx create-dagster@latest project my-project”
   • [probe] “official MCP server documented at https://docs.dagster.io/getting-started/ai-tools/dagster-mcp”
   • [probe] “official CLI documented at https://docs.dagster.io/api/clis/dg-cli/dg-cli-configuration”
   • [probe] “PROBE runtime (recorded 2026-09-08): the full agent-builds-a-project path ran keylessly end to end — `uvx create-dagster@latest project pa-p…”
   • [probe] “PROBE runtime (recorded 2026-09-08): the official dagster CLI installed keylessly from pypi via uvx and printed 'dagster, version 1.13.21'.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.dagster.io/openapi.json, https://docs.dagster.io/swagger.json, https://docs.dagster.io/…”

   proof ↗⚑ flag

8. ai-native userSubscribe to events via webhooks

   weight 2 · round drawn
   Fivetran—none0/10

   The evidence pack contains no mention of webhooks or event subscription mechanisms for Fivetran; it covers connectors, REST API, transformations, MCP server, and pricing but never webhooks. Since Fivetran is a data platform where webhook-based event notifications (e.g., sync completion, failure alerts) would be a plausible feature, this axis applies but is unevidenced.

   ⚑ flag

   Dagster—none0/10

   Dagster documents sensors (event-driven triggers) and Dagster+ alerts, but no evidence describes an actual webhook subscription mechanism for external systems to receive event notifications from Dagster. This is a fair capability to expect from an orchestration platform aiming for agentic integrations, so absence of evidence yields 'none' rather than 'na'.

   • [claimed-docs] “Sensors enable you to take action in response to events that occur either internally within Dagster or in external systems.”
   • [claimed-docs] “Dagster+ alerts can notify you of critical events occurring in your deployment so you can catch potential issues early”

   proof ↗⚑ flag

Agentic features

1. ai-native userGet AI-generated insights and suggestions from my data inside the product

   weight 2 · round drawn
   Fivetran—none0/10

   Fivetran's evidence shows a data unification/context layer meant to help external AI tools answer questions (fivetran-docs-7) and an MCP server for asking meta-questions about pipeline/sync status (fivetran-docs-28), but there is no evidence of Fivetran itself generating AI-driven insights or suggestions about the data's content inside the product.

   • [claimed-docs] “Create a unified context layer that enables your AI tools to answer questions more accurately.”
   • [claimed-docs] “It allows you to ask read-only questions like "when was the last time my postgres connection completed a sync?" and "are any of my connectio…”

   proof ↗⚑ flag

   Dagster—none0/10

   Dagster's AI features are aimed at helping coding agents build and manage pipelines (an AI skill for context, a Dagster+ MCP server for accessing deployment info) rather than generating insights or suggestions from the underlying data assets themselves. No evidence shows in-product AI analyzing data content, flagging anomalies, or suggesting insights to end users. missing for 10: any evidence of AI-generated insights/suggestions about data content, in-product analytics copilot, or anomaly detection surfaced to users.

   • [claimed-docs] “Dagster maintains an AI skill that gives coding agents better context and patterns for building Dagster projects.”
   • [claimed-docs] “The Dagster+ MCP server allows you to access information and take actions in your Dagster+ deployment within an AI session.”
   • [probe] “official MCP server documented at https://docs.dagster.io/getting-started/ai-tools/dagster-mcp”

   proof ↗⚑ flag

2. ai-native userSet up automations that run autonomously in the background

   weight 2 · round to Dagster
   Fivetran✓fullcommunity7/10

   Fivetran's core product automatically syncs data, handles schema changes, and orchestrates transformations on a schedule without manual pipeline maintenance, which is the definition of an autonomous background automation, and docs confirm this for both pre-built and custom (SDK) connectors as well as dbt-based transformations. However, missing for 10: independent evidence of complex conditional/event-triggered workflows beyond scheduled syncs, and community reports of occasional sync failures/reliability hiccups (fivetran-comm-4, fivetran-comm-10) that add real-world caveats to 'runs autonomously.'

   • [claimed-docs] “Fivetran provides pre-built data connectors that automatically sync data from your applications, databases, event streams, and files to your…”
   • [claimed-docs] “Orchestrate pre-built and custom data transformations in your destination with Fivetran.”
   • [claimed-docs] “Use the Fivetran-hosted dbt Core integration or our third-party dbt Cloud and Coalesce orchestration to centralize and manage all your trans…”
   • [claimed-docs] “Each connector handles schema changes, API updates, and incremental syncs automatically — no data pipelines to maintain.”
   • [claimed-docs] “Fivetran provides pre-built data connectors that automatically sync data from your applications, databases, event streams, and files to your…”
   • [claimed-docs] “1-minute syncs”
   • [community] “I've used Fivetran at VC funded startups... I understand the value of not having to build this piece of common infrastructure... we did expe…”
   • [community] “fivetran is fantastic for not having to deal with a boatload of third parties constant API updates and changes. If your core competency is s…”

   proof ↗⚑ flag

   Dagster✓fullprobed8/10

   Dagster natively supports autonomous background automation via Schedules, Sensors, and Declarative Automation, which trigger asset materializations without manual intervention, backed by a long-running daemon/webserver deployment model; this is corroborated by runtime probes confirming the platform actually runs (dagster dev, daemon container). This directly satisfies the 'AI-native user sets up automations that run autonomously in the background' story, and is further extended by an AI skill and MCP server for agent-driven setup. missing for 10: independent hands-on validation specifically of sensors/schedules firing unattended over time, and more detail on failure/retry handling for long-running autonomous automations.

   • [claimed-docs] “Schedules enable automated execution of jobs at specified intervals.”
   • [claimed-docs] “Sensors enable you to take action in response to events that occur either internally within Dagster or in external systems.”
   • [claimed-docs] “Declarative Automation is a framework that uses information about the status of your assets and their dependencies to launch executions of y…”
   • [claimed-docs] “A typical Dagster Docker deployment includes a several long-running containers: one for the webserver, one for the daemon, and one for each …”
   • [claimed-docs] “Dagster maintains an AI skill that gives coding agents better context and patterns for building Dagster projects.”
   • [claimed-docs] “The Dagster+ MCP server allows you to access information and take actions in your Dagster+ deployment within an AI session.”
   • [probe] “PROBE runtime (recorded 2026-09-08): the full agent-builds-a-project path ran keylessly end to end — `uvx create-dagster@latest project pa-p…”

   proof ↗⚑ flag

3. ai-native userDelegate tasks to a built-in AI assistant inside the product

   weight 3 · round drawn
   Fivetran—none0/10

   Evidence shows Fivetran as a data movement platform with an MCP server that lets external AI assistants query Fivetran (fivetran-docs-28/29/30) and doc content about feeding a 'unified context layer' to external AI tools (fivetran-docs-7), but no evidence of a built-in AI assistant inside Fivetran's own product that a user can delegate tasks to.

   • [claimed-docs] “Create a unified context layer that enables your AI tools to answer questions more accurately.”
   • [claimed-docs] “It allows you to ask read-only questions like "when was the last time my postgres connection completed a sync?" and "are any of my connectio…”
   • [claimed-docs] “Set `FIVETRAN_SCOPE` to `read/write` or `read/write/delete` to unlock write and delete operations”
   • [claimed-docs] “Copy existing Fivetran connections to a new destination. Keep their configs and schemas intact or modify them as you like.”

   proof ↗⚑ flag

   Dagster—none0/10

   Evidence shows Dagster ships an AI skill and an MCP server so that external coding agents (e.g., Claude, Copilot) can build/manage Dagster projects, but this is the inverse of the story — it makes Dagster controllable by agents, not a built-in assistant living inside Dagster's own UI/product that a user can delegate tasks to. No evidence of an embedded chat/assistant feature within Dagster's webserver or CLI.

   • [claimed-docs] “Dagster maintains an AI skill that gives coding agents better context and patterns for building Dagster projects.”
   • [claimed-docs] “The Dagster+ MCP server allows you to access information and take actions in your Dagster+ deployment within an AI session.”
   • [probe] “official MCP server documented at https://docs.dagster.io/getting-started/ai-tools/dagster-mcp”

   proof ↗⚑ flag

4. ai-native userOperate the product with natural-language commands

   weight 2 · round drawn
   Fivetran~partialclaimed6/10

   Fivetran ships an official MCP server (fivetran-mcp) that lets users ask natural-language questions like 'when was the last time my postgres connection completed a sync?' and perform read/write/delete operations via configured scope, which is genuine natural-language operation of the product through an AI agent interface. However, this is documented in a single README with no independent hands-on corroboration, and the scope of NL-controllable actions (sync status, connection copying) is narrower than the full breadth of Fivetran's product surface (e.g., transformations, deployment models, RBAC). Missing for 10: independent/hands-on verification of the MCP server, broader coverage of NL commands across all product features, first-party docs (not just GitHub README) detailing the natural-language interface.

   • [claimed-docs] “It allows you to ask read-only questions like "when was the last time my postgres connection completed a sync?" and "are any of my connectio…”
   • [claimed-docs] “Set `FIVETRAN_SCOPE` to `read/write` or `read/write/delete` to unlock write and delete operations”
   • [claimed-docs] “Copy existing Fivetran connections to a new destination. Keep their configs and schemas intact or modify them as you like.”

   proof ↗⚑ flag

   Dagster~partialprobed6/10

   Dagster ships an official Dagster+ MCP server and a maintained AI skill giving coding agents context/patterns for building Dagster projects, and hands-on probes confirm agent-driven scaffolding/running of projects works end-to-end. However, this is agent-assisted development (via CLI/MCP tools), not evidence of a natural-language command interface within Dagster itself (e.g., chat-driven asset creation or NL-to-pipeline translation). Missing for 10: direct evidence of natural-language command execution inside the product UI/runtime, broader independent validation of the MCP server's NL capabilities beyond docs.

   • [claimed-docs] “Dagster maintains an AI skill that gives coding agents better context and patterns for building Dagster projects.”
   • [claimed-docs] “The Dagster+ MCP server allows you to access information and take actions in your Dagster+ deployment within an AI session.”
   • [probe] “official MCP server documented at https://docs.dagster.io/getting-started/ai-tools/dagster-mcp”
   • [probe] “PROBE runtime (recorded 2026-09-08): the full agent-builds-a-project path ran keylessly end to end — `uvx create-dagster@latest project pa-p…”

   proof ↗⚑ flag

Api quality

1. ai-native userExplore an interactive API reference with runnable examples

   weight 2 · round drawn
   Fivetran—none0/10

   Evidence shows Fivetran has a REST API and developer docs, but there is no mention of an interactive API reference with runnable examples, and probes for openapi.json/swagger.json all returned 404, suggesting no interactive spec is exposed.

   • [claimed-docs] “Set up and scale your data pipeline, and manage your Fivetran account programmatically using the Fivetran REST API.”
   • [claimed-docs] “Fivetran REST API”
   • [probe] “PROBE openapi: all candidate paths 404 (https://fivetran.com/openapi.json, https://fivetran.com/swagger.json, https://fivetran.com/api/opena…”
   • [probe] “PROBE docs-md: HTTP 404 at https://fivetran.com/docs.md”

   proof ↗⚑ flag

   Dagster—none0/10

   Evidence shows only static documentation with code snippets and an llms.txt for LLM consumption, but explicit probes for an OpenAPI/interactive API reference (Swagger UI, runnable playground) all returned 404, and no evidence of runnable in-browser examples exists.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.dagster.io/openapi.json, https://docs.dagster.io/swagger.json, https://docs.dagster.io/…”
   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.dagster.io/llms.txt # Dagster Docs ## Docs - [Changelog](about/changelog): Review detailed update…”
   • [claimed-docs] “import dagster as dg@dg.assetdef hello(context: dg.AssetExecutionContext): context.log.info("Hello!")@dg.asset(deps=[hello])”

   proof ↗⚑ flag

2. ai-native userDownload a machine-readable API spec (OpenAPI or equivalent)

   weight 2 · round drawn
   Fivetran—none0/10

   Fivetran documents a REST API but the probe evidence explicitly shows no OpenAPI/swagger spec is available at any standard location (all candidate paths 404), and no docs page offers a downloadable machine-readable spec.

   • [probe] “PROBE openapi: all candidate paths 404 (https://fivetran.com/openapi.json, https://fivetran.com/swagger.json, https://fivetran.com/api/opena…”
   • [claimed-docs] “Set up and scale your data pipeline, and manage your Fivetran account programmatically using the Fivetran REST API.”
   • [claimed-docs] “Fivetran REST API”

   proof ↗⚑ flag

   Dagster—none0/10

   A direct probe for OpenAPI/Swagger spec files at docs.dagster.io returned 404 on all candidate paths, and no other evidence shows a downloadable machine-readable API spec (Dagster exposes a GraphQL API but no documented OpenAPI equivalent).

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.dagster.io/openapi.json, https://docs.dagster.io/swagger.json, https://docs.dagster.io/…”

   proof ↗⚑ flag

3. ai-native userTest against a sandbox environment without touching production data

   weight 1 · round to Dagster
   Fivetran—none0/10

   No evidence of a sandbox/test environment separate from production for testing connectors, transformations, or MCP operations without touching live production data; deployment models and MCP scope docs mention read/write/delete modes but no dedicated sandbox environment. Missing for 10: any mention of a sandbox/staging deployment, test data environment, or isolated non-production instance.

   ⚑ flag

   Dagster~partialprobed6/10

   Dagster's architecture supports separating business logic from environment via resource mocking and a distinct local dev workflow ('laptop to CI to dev to prod'), and the runtime probe confirms `dagster dev` boots a fully local, self-contained instance with no external/production dependencies. However, there's no dedicated documentation of a formal 'sandbox mode' or built-in production-data isolation guarantees (e.g., explicit dev/prod resource configs, data masking) beyond the general resource-abstraction pattern. Missing for 10: explicit sandbox/staging environment docs, first-party guidance on isolating production data access, and independent confirmation of safe separation in real deployments.

   • [community] “Dagster team response: goals include (1) Local development - seamless end-to-end dev experience from laptop to CI to dev to prod, (2) managi…”
   • [probe] “PROBE runtime (recorded 2026-09-08): the full agent-builds-a-project path ran keylessly end to end — `uvx create-dagster@latest project pa-p…”
   • [claimed-docs] “Ensure a particular column doesn't contain null values * Verify that a tabular asset adheres to a specified schema * Check if an asset's…”

   proof ↗⚑ flag

4. ai-native userRely on versioned APIs with a documented deprecation policy

   weight 2 · round drawn
   Fivetran—none0/10

   There is a documented REST API and API SDK, but no evidence of API versioning scheme or a documented deprecation policy anywhere in the pack; the community and comm data instead flag reliability/pricing issues unrelated to versioning. missing for 10: documented API version numbering, changelog/deprecation policy, migration timelines, sunset notices for old API versions.

   • [claimed-docs] “Set up and scale your data pipeline, and manage your Fivetran account programmatically using the Fivetran REST API.”
   • [claimed-docs] “Fivetran REST API”
   • [probe] “PROBE openapi: all candidate paths 404 (https://fivetran.com/openapi.json, https://fivetran.com/swagger.json, https://fivetran.com/api/opena…”

   proof ↗⚑ flag

   Dagster—none0/10

   Evidence shows Dagster has versioned releases (e.g., 1.13.21) and a changelog of feature updates, but no documentation of an explicit API deprecation policy, versioning guarantees, or migration/support timelines is present in the evidence pack.

   • [claimed-docs] “Automation condition evaluations now explain history-dependent conditions (since, newly_true, newly_missing) by showing the remembered value…”
   • [claimed-docs] “wiping and deleting dynamic partitions in a single action now also supports multi-partitioned assets that use the dynamic partitions definit…”
   • [probe] “PROBE runtime (recorded 2026-09-08): the full agent-builds-a-project path ran keylessly end to end — `uvx create-dagster@latest project pa-p…”
   • [probe] “PROBE runtime (recorded 2026-09-08): the official dagster CLI installed keylessly from pypi via uvx and printed 'dagster, version 1.13.21'.”

   proof ↗⚑ flag

Ai build

1. ai-native userA coding agent can scaffold, configure, and run a complete pipeline headlessly through the CLI or API

   weight 3 · round to Dagster
   Fivetran~partialprobed7/10

   Fivetran exposes a REST API for programmatic pipeline setup, a Connector SDK for scaffolding custom Python connectors, and a dedicated MCP server that supports read/write/delete operations (e.g., copying connections, checking sync status), which together let an agent configure and run pipelines headlessly. However, there's no documented standalone CLI, and community reports flag API reliability issues, so the full 'scaffold+configure+run' loop isn't shown end-to-end in one hands-on example. Missing for 10: a first-party CLI tool, an end-to-end agent-run pipeline case study, and independent confirmation of reliable headless API/MCP execution.

   • [claimed-docs] “Set up and scale your data pipeline, and manage your Fivetran account programmatically using the Fivetran REST API.”
   • [claimed-docs] “Fivetran’s Connector SDK allows you to develop a custom data connector using Python and deploy it as an extension of Fivetran.”
   • [claimed-docs] “It allows you to ask read-only questions like "when was the last time my postgres connection completed a sync?" and "are any of my connectio…”
   • [claimed-docs] “Set `FIVETRAN_SCOPE` to `read/write` or `read/write/delete` to unlock write and delete operations”
   • [claimed-docs] “Copy existing Fivetran connections to a new destination. Keep their configs and schemas intact or modify them as you like.”
   • [probe] “PROBE runtime (recorded 2026-09-08): Fivetran's documented REST API is live and cleanly auth-gated — a keyless GET https://api.fivetran.com/…”
   • [community] “Unrelated to the article itself but Fivetran has the worst possible product from a developer perspective, their APIs are unreliable and will…”

   proof ↗⚑ flag

   Dagster✓fullprobed8/10

   Dagster provides an official CLI (create-dagster, dg) to scaffold a project, define assets/jobs, and run them headlessly (`uv run dagster dev`), and this was independently verified end-to-end by a runtime probe that scaffolded a project, booted the webserver, and confirmed version info — plus a documented AI skill and MCP server specifically for coding agents. missing for 10: deeper evidence of a first-class programmatic/GraphQL API run path (vs CLI) and independent third-party confirmation beyond the single runtime probe.

   • [claimed-docs] “you can scaffold a new project with the create-dagster CLI (recommended)”
   • [claimed-docs] “uvx create-dagster@latest project my-project”
   • [claimed-docs] “You can scaffold Dagster Component definitions in your project from the command line with the dg scaffold defs command”
   • [claimed-docs] “Dagster maintains an AI skill that gives coding agents better context and patterns for building Dagster projects.”
   • [claimed-docs] “The Dagster+ MCP server allows you to access information and take actions in your Dagster+ deployment within an AI session.”
   • [probe] “PROBE runtime (recorded 2026-09-08): the full agent-builds-a-project path ran keylessly end to end — `uvx create-dagster@latest project pa-p…”
   • [probe] “PROBE runtime (recorded 2026-09-08): the official dagster CLI installed keylessly from pypi via uvx and printed 'dagster, version 1.13.21'.”
   • [probe] “official CLI documented at https://docs.dagster.io/api/clis/dg-cli/dg-cli-configuration”

   proof ↗⚑ flag

2. ai-native userAI drafts a working connector from API documentation — auth, pagination, streams — that I review and ship

   weight 3 · round drawn
   Fivetran—none0/10

   Fivetran's Connector SDK lets developers write custom Python connectors, and there's a read-only MCP server for managing connections, but no evidence shows an AI drafting a working connector (auth, pagination, streams) from API documentation for review and shipping.

   • [claimed-docs] “Fivetran’s Connector SDK allows you to develop a custom data connector using Python and deploy it as an extension of Fivetran.”
   • [claimed-docs] “Develop a custom data connector using Python and deploy it as an extension of Fivetran.”
   • [claimed-docs] “It allows you to ask read-only questions like "when was the last time my postgres connection completed a sync?" and "are any of my connectio…”

   proof ↗⚑ flag

   Dagster—none0/10

   Dagster's evidence shows AI coding-agent skills, an MCP server, and CLI scaffolding for generic Dagster projects/components, plus integrations with connector tools (Airbyte, Fivetran, dlt), but there is no evidence of an AI feature that drafts a working connector (auth, pagination, streams) directly from API documentation for review and shipping.

   • [claimed-docs] “Dagster maintains an AI skill that gives coding agents better context and patterns for building Dagster projects.”
   • [claimed-docs] “The Dagster+ MCP server allows you to access information and take actions in your Dagster+ deployment within an AI session.”
   • [claimed-docs] “provides a FivetranAccountComponent which can be used to easily represent Fivetran connectors as assets in Dagster”
   • [claimed-docs] “provides a DltLoadCollectionComponent which can be used to easily represent a collection of dlt sources and pipelines as assets in Dagster”

   proof ↗⚑ flag

Ai destinations

1. ai-native userPipelines load into vector stores and LLM-ready formats so my agents can retrieve what was synced

   weight 1 · round drawn
   Fivetran—none0/10

   Fivetran's docs describe syncing to data warehouses/lakes and a vague 'unified context layer for AI tools' claim, but there is no evidence of actual vector-store destinations, embedding generation, or LLM-ready output formats that would let an agent retrieve synced data. Missing for 10: named vector database connectors (e.g., Pinecone, Weaviate, pgvector), embedding/chunking pipeline support, and any documentation of LLM-ready format outputs.

   • [claimed-docs] “Create a unified context layer that enables your AI tools to answer questions more accurately.”
   • [claimed-docs] “Automatically sync query‑ready, fully‑managed data to your data lake in open table formats.”

   proof ↗⚑ flag

   Dagster—none0/10

   Dagster orchestrates data pipelines and has integrations for dbt, Airbyte, Fivetran, dlt, etc., but there is no evidence of any built-in or documented capability to load data into vector stores or LLM-ready formats (e.g., embeddings, chunking, vector DB connectors) for agent retrieval. The evidence pack covers general orchestration, automation, and AI-agent-assist tooling (MCP server, AI skill for coding agents) but nothing about vector store integration or LLM-ready output formats.

   ⚑ flag

Ai operate

1. ai-native userAn agent can check sync status, diagnose a failed run, and re-trigger it through an API or MCP server

   weight 2 · round drawn
   Fivetran~partialclaimed6/10

   Fivetran has a documented MCP server that lets an agent ask read-only questions like sync status and whether connections are broken, and can unlock write/delete operations via scope config, plus a REST API for programmatic management — covering status-check and diagnosis well. However, no evidence explicitly documents a 're-trigger sync' action/endpoint via the MCP server or REST API, only generic write-scope and connection-copy examples. missing for 10: explicit documentation of a sync re-trigger/force-sync API or MCP tool, and any hands-on confirmation of an end-to-end check→diagnose→retrigger workflow.

   • [claimed-docs] “It allows you to ask read-only questions like "when was the last time my postgres connection completed a sync?" and "are any of my connectio…”
   • [claimed-docs] “Set `FIVETRAN_SCOPE` to `read/write` or `read/write/delete` to unlock write and delete operations”
   • [claimed-docs] “Copy existing Fivetran connections to a new destination. Keep their configs and schemas intact or modify them as you like.”
   • [claimed-docs] “Set up and scale your data pipeline, and manage your Fivetran account programmatically using the Fivetran REST API.”
   • [claimed-docs] “Fivetran REST API”

   proof ↗⚑ flag

   Dagster~partialprobed6/10

   Dagster documents an official Dagster+ MCP server explicitly for accessing deployment info and taking actions within an AI session, which plausibly covers checking status and re-triggering runs, and Dagster's core APIs/CLI (dg, dagster) provide programmatic run inspection and re-execution. However, no evidence specifically documents diagnosing a *failed run* or granular sync-status checks via the MCP server, nor is there hands-on confirmation of this exact workflow. Missing for 10: documented MCP tool list showing failed-run diagnostics, hands-on example of re-triggering a run via MCP/API, independent corroboration of the MCP server's action scope.

   • [claimed-docs] “The Dagster+ MCP server allows you to access information and take actions in your Dagster+ deployment within an AI session.”
   • [probe] “official MCP server documented at https://docs.dagster.io/getting-started/ai-tools/dagster-mcp”
   • [claimed-docs] “Dagster+ alerts can notify you of critical events occurring in your deployment so you can catch potential issues early”

   proof ↗⚑ flag

1. ai-native userPerform bulk operations across many items at once

   weight 2 · round to Dagster
   Fivetran~partialclaimed4/10

   Fivetran's REST API and MCP server allow programmatic management of connectors, including copying existing connections to new destinations and read/write/delete operations at scale, which supports some multi-item automation. However, there is no explicit documentation of true bulk operations (e.g., batch create/update/delete across many items in a single call) beyond individual connector-level actions. missing for 10: explicit batch/bulk API endpoints, evidence of processing many items in one operation, and independent confirmation of bulk workflows working at scale.

   • [claimed-docs] “Set `FIVETRAN_SCOPE` to `read/write` or `read/write/delete` to unlock write and delete operations”
   • [claimed-docs] “Copy existing Fivetran connections to a new destination. Keep their configs and schemas intact or modify them as you like.”
   • [claimed-docs] “Fivetran REST API”
   • [claimed-docs] “Set up and scale your data pipeline, and manage your Fivetran account programmatically using the Fivetran REST API.”

   proof ↗⚑ flag

   Dagster~partialprobed5/10

   Dagster supports some bulk operations natively — e.g. backfills/subsetting dbt models across many assets at once (dagster-docs-7), and bulk wiping/deleting of dynamic partitions across multi-partitioned assets in a single action (dagster-docs-25) — and these can be triggered programmatically or via AI-agent tooling (MCP server, CLI). However, there is no dedicated documentation of a general-purpose bulk API/operation framework for arbitrary bulk actions across items (e.g. bulk asset materialization, bulk run cancellation, bulk metadata edits) accessible to AI agents specifically. Missing for 10: comprehensive bulk-operation API docs, AI-agent-specific bulk action examples, independent corroboration of bulk workflows at scale.

   • [claimed-docs] “Use Dagster's UI or APIs to run subsets of your dbt models, seeds, and snapshots.”
   • [claimed-docs] “wiping and deleting dynamic partitions in a single action now also supports multi-partitioned assets that use the dynamic partitions definit…”
   • [probe] “official MCP server documented at https://docs.dagster.io/getting-started/ai-tools/dagster-mcp”
   • [claimed-docs] “The Dagster+ MCP server allows you to access information and take actions in your Dagster+ deployment within an AI session.”

   proof ↗⚑ flag

2. ai-native userDefine rules that trigger actions automatically on events

   weight 3 · round to Dagster
   Fivetran~partialclaimed3/10

   Fivetran provides some automation primitives — scheduled/automatic connector syncs, orchestrated transformations, and a documented 'Fivetran Alerts' feature — but there's no evidence of user-definable event-condition-action rules (e.g., webhooks firing custom actions on data events) that would satisfy an AI-native automation story. missing for 10: documented rule/trigger definition UI or API, event-based webhook/action framework, examples of custom conditional automations beyond scheduled syncs and generic alerts.

   • [claimed-docs] “Fivetran Alerts”
   • [claimed-docs] “Orchestrate pre-built and custom data transformations in your destination with Fivetran.”
   • [claimed-docs] “Fivetran provides pre-built data connectors that automatically sync data from your applications, databases, event streams, and files to your…”

   proof ↗⚑ flag

   Dagster✓fullprobed8/10

   Dagster provides Sensors (event-driven triggers from internal/external systems), Schedules (time-based triggers), and Declarative Automation conditions to automatically launch asset executions based on state/dependency changes — directly matching the 'rules that trigger actions on events' story. This is corroborated by runtime probes confirming the platform actually runs, and changelog entries showing active refinement of automation conditions. Missing for 10: no independent hands-on evidence specifically exercising sensors/declarative-automation end-to-end (only docs+general runtime probes), and no AI-native-specific example combining automation rules with agent-driven triggers.

   • [claimed-docs] “Schedules enable automated execution of jobs at specified intervals.”
   • [claimed-docs] “Sensors enable you to take action in response to events that occur either internally within Dagster or in external systems.”
   • [claimed-docs] “Declarative Automation is a framework that uses information about the status of your assets and their dependencies to launch executions of y…”
   • [claimed-docs] “Automation condition evaluations now explain history-dependent conditions (since, newly_true, newly_missing) by showing the remembered value…”
   • [probe] “PROBE runtime (recorded 2026-09-08): the full agent-builds-a-project path ran keylessly end to end — `uvx create-dagster@latest project pa-p…”

   proof ↗⚑ flag

3. ai-native userSchedule recurring jobs or workflows

   weight 2 · round to Dagster
   Fivetran✓fullcommunity7/10

   Fivetran's core product is scheduled, recurring data syncs (down to 1-minute intervals) plus orchestrated transformations, and its REST API/MCP server let an AI-native user programmatically manage, trigger, and monitor these recurring pipelines (e.g., checking sync status, copying connections, write/delete operations). This directly satisfies 'schedule recurring jobs/workflows' for the data-pipeline domain. Missing for 10: explicit documentation of arbitrary cron-style custom job scheduling beyond connector sync frequency, and independent hands-on confirmation that scheduled syncs run reliably (community reports mention occasional sync drift/re-sync needs).

   • [claimed-docs] “Fivetran provides pre-built data connectors that automatically sync data from your applications, databases, event streams, and files to your…”
   • [claimed-docs] “Orchestrate pre-built and custom data transformations in your destination with Fivetran.”
   • [claimed-docs] “1-minute syncs”
   • [claimed-docs] “Set up and scale your data pipeline, and manage your Fivetran account programmatically using the Fivetran REST API.”
   • [claimed-docs] “It allows you to ask read-only questions like "when was the last time my postgres connection completed a sync?" and "are any of my connectio…”
   • [claimed-docs] “Set `FIVETRAN_SCOPE` to `read/write` or `read/write/delete` to unlock write and delete operations”
   • [claimed-docs] “Copy existing Fivetran connections to a new destination. Keep their configs and schemas intact or modify them as you like.”
   • [community] “I've used Fivetran at VC funded startups... I understand the value of not having to build this piece of common infrastructure... we did expe…”

   proof ↗⚑ flag

   Dagster✓fullprobed8/10

   Dagster's Schedules feature explicitly enables automated execution of jobs at specified intervals, complemented by Sensors and Declarative Automation for event-driven triggers, all backed by first-party docs and confirmed runnable via probe evidence of a working local deployment. Missing for 10: no independent/hands-on confirmation specifically of schedule-based (cron-style) recurring execution in production, and no community corroboration of scheduling reliability at scale.

   • [claimed-docs] “Schedules enable automated execution of jobs at specified intervals.”
   • [claimed-docs] “Sensors enable you to take action in response to events that occur either internally within Dagster or in external systems.”
   • [claimed-docs] “Declarative Automation is a framework that uses information about the status of your assets and their dependencies to launch executions of y…”
   • [probe] “PROBE runtime (recorded 2026-09-08): the full agent-builds-a-project path ran keylessly end to end — `uvx create-dagster@latest project pa-p…”

   proof ↗⚑ flag

4. ai-native userVersion, review, and roll back my automations

   weight 1 · round to Dagster
   Fivetran—none0/10

   Fivetran's evidence covers connectors, transformations, dbt integration, and REST API management, but nothing describes version history, review workflows, or rollback capability for connector configs or transformations themselves; dbt integration allows external git versioning but that's not a Fivetran-native capability documented here.

   • [claimed-docs] “Orchestrate pre-built and custom data transformations in your destination with Fivetran.”
   • [claimed-docs] “Use the Fivetran-hosted dbt Core integration or our third-party dbt Cloud and Coalesce orchestration to centralize and manage all your trans…”
   • [claimed-docs] “We created data models that transform your data into analytics-ready tables. You can either add the models in the Fivetran dashboard (Quicks…”
   • [claimed-docs] “Fivetran REST API”

   proof ↗⚑ flag

   Dagster~partialcommunity4/10

   Dagster's automations are defined as code (asset/job definitions), which implicitly supports versioning and rollback via standard git workflows, and community evidence notes Dagster has figured out 'development branches' for review workflows; the changelog also shows automation condition evaluations exposing history-dependent state for review. However, there is no first-party documentation of a built-in version-history UI, diff/review workflow, or one-click rollback mechanism specific to automations. missing for 10: explicit built-in versioning/audit UI for automation definitions, a documented review/approval workflow, and a documented rollback mechanism beyond generic git revert.

   • [claimed-docs] “An asset definition is a description, in code, of an asset that should exist and how to produce and update that asset.”
   • [claimed-docs] “Automation condition evaluations now explain history-dependent conditions (since, newly_true, newly_missing) by showing the remembered value…”
   • [community] “I believe Dagster is hitting the right chord: they focus on the pain points in DX for Airflow and similar solutions, they have figured out h…”

   proof ↗⚑ flag

Code first

1. data engineerMy pipelines are plain code and config in my own repository — versioned, reviewed, and portable like any software

   weight 2 · round to Dagster
   Fivetran~partialclaimed4/10

   Fivetran offers a Python Connector SDK for custom connectors, a REST API for programmatic management, and dbt Core integration for code-based transformations, giving some code/version-control surface. However, the core connector configurations and sync pipelines are managed through Fivetran's hosted dashboard/cloud service rather than stored as plain files in the user's own repo, so full pipeline-as-code portability is not demonstrated. Missing for 10: evidence of pipeline definitions expressed as declarative config files checked into a repo, git-based review workflows for connector/pipeline changes, and confirmation that Fivetran-managed syncs can be fully defined/reproduced from code without the SaaS UI.

   • [claimed-docs] “Fivetran’s Connector SDK allows you to develop a custom data connector using Python and deploy it as an extension of Fivetran.”
   • [claimed-docs] “Set up and scale your data pipeline, and manage your Fivetran account programmatically using the Fivetran REST API.”
   • [claimed-docs] “Use the Fivetran-hosted dbt Core integration or our third-party dbt Cloud and Coalesce orchestration to centralize and manage all your trans…”
   • [claimed-docs] “We created data models that transform your data into analytics-ready tables. You can either add the models in the Fivetran dashboard (Quicks…”
   • [claimed-docs] “Fivetran REST API”

   proof ↗⚑ flag

   Dagster✓fullprobed8/10

   Dagster pipelines are defined as plain Python code (asset definitions, `dg.asset` decorators) scaffolded via CLI into a standard project structure (pyproject.toml, src, tests) that lives in a normal repo, confirmed by hands-on probes showing the CLI scaffolds and runs a project end-to-end. This is inherently version-controllable, code-reviewable, and portable across environments (local, CI, Docker deployment docs confirm portability). missing for 10: no explicit documentation/discussion of git-based review workflows or portability testimonials from independent/community sources beyond docs and CLI probes.

   • [claimed-docs] “An asset definition is a description, in code, of an asset that should exist and how to produce and update that asset.”
   • [claimed-docs] “you can scaffold a new project with the create-dagster CLI (recommended)”
   • [claimed-docs] “import dagster as dg@dg.assetdef hello(context: dg.AssetExecutionContext): context.log.info("Hello!")@dg.asset(deps=[hello])”
   • [claimed-docs] “uvx create-dagster@latest project my-project”
   • [claimed-docs] “A typical Dagster Docker deployment includes a several long-running containers: one for the webserver, one for the daemon, and one for each …”
   • [probe] “PROBE runtime (recorded 2026-09-08): the full agent-builds-a-project path ran keylessly end to end — `uvx create-dagster@latest project pa-p…”
   • [probe] “PROBE runtime (recorded 2026-09-08): the official dagster CLI installed keylessly from pypi via uvx and printed 'dagster, version 1.13.21'.”

   proof ↗⚑ flag

Destinations

1. data engineerI load to the major warehouses and lakes — Snowflake, BigQuery, Databricks, Postgres, object storage — without changing pipelines

   weight 2 · round to Fivetran
   Fivetran✓fullcommunity8/10

   Fivetran's core value prop is loading via pre-built connectors to major warehouses/lakes (Snowflake, BigQuery, Databricks, Postgres) and object storage/data lakes in open table formats, with schema/API changes handled automatically so pipelines don't need to change per destination, plus multiple deployment models (SaaS/hybrid) supporting portability across environments. Community feedback corroborates reliability of syncing as a strength even amid pricing complaints, which are off-topic to this axis. Missing for 10: no explicit named list of exact warehouse/lake destinations or independent benchmark proving zero pipeline changes when switching destinations.

   • [claimed-docs] “Fivetran provides pre-built data connectors that automatically sync data from your applications, databases, event streams, and files to your…”
   • [claimed-docs] “Automatically sync query‑ready, fully‑managed data to your data lake in open table formats.”
   • [claimed-docs] “Each connector handles schema changes, API updates, and incremental syncs automatically — no data pipelines to maintain.”
   • [claimed-docs] “Fivetran provides pre-built data connectors that automatically sync data from your applications, databases, event streams, and files to your…”
   • [claimed-docs] “These solutions include the following deployment models: SaaS Deployment... Hybrid Deployment”
   • [community] “Fivetran's syncing has been very reliable (compared to others we tried) but the "active row" based pricing is unpredictable and can have hug…”
   • [community] “fivetran is fantastic for not having to deal with a boatload of third parties constant API updates and changes. If your core competency is s…”

   proof ↗⚑ flag

   Dagster~partialclaimed4/10

   Dagster's asset framework and its dbt/Airbyte/Fivetran/dlt integrations imply pipelines can load into various warehouses/lakes via pluggable tooling, but the evidence pack has no direct mention of first-class I/O managers or connectors for Snowflake, BigQuery, Databricks, Postgres, or object storage, nor documentation of the 'swap destination without changing pipeline code' abstraction the story requires. missing for 10: explicit warehouse/lake connector docs (Snowflake, BigQuery, Databricks, Postgres, S3), evidence of I/O-manager-based portability across these targets, and any hands-on confirmation of switching destinations without code changes.

   • [claimed-docs] “Use Dagster's UI or APIs to run subsets of your dbt models, seeds, and snapshots.”
   • [claimed-docs] “Using this integration, you can trigger Airbyte syncs and orchestrate your Airbyte connections from within Dagster”
   • [claimed-docs] “provides a FivetranAccountComponent which can be used to easily represent Fivetran connectors as assets in Dagster”
   • [claimed-docs] “provides a DltLoadCollectionComponent which can be used to easily represent a collection of dlt sources and pipelines as assets in Dagster”
   • [claimed-docs] “An asset definition is a description, in code, of an asset that should exist and how to produce and update that asset.”

   proof ↗⚑ flag

Catalog

1. data engineerI pick from a broad catalog of maintained connectors for the SaaS APIs, databases, and files my company actually uses

   weight 3 · round to Fivetran
   Fivetran✓fullcommunity8/10

   Fivetran's docs explicitly describe a catalog of pre-built connectors spanning apps, databases, event streams, and files, with automatic handling of schema drift and incremental syncs, plus a Connector SDK for building custom ones; community comments corroborate this reduces ETL maintenance burden ('not having to deal with a boatload of third parties constant API updates'). missing for 10: no explicit enumeration of connector count/catalog breadth or independent verification of specific connector coverage, and some community reports note occasional connector reliability/sync issues.

   • [claimed-docs] “Fivetran provides pre-built data connectors that automatically sync data from your applications, databases, event streams, and files to your…”
   • [claimed-docs] “Fivetran’s Connector SDK allows you to develop a custom data connector using Python and deploy it as an extension of Fivetran.”
   • [claimed-docs] “Each connector handles schema changes, API updates, and incremental syncs automatically — no data pipelines to maintain.”
   • [claimed-docs] “Fivetran provides pre-built data connectors that automatically sync data from your applications, databases, event streams, and files to your…”
   • [community] “The fundamental challenge of open-source ETL is that high-quality connectors require understanding and working around all kinds of corner ca…”
   • [community] “fivetran is fantastic for not having to deal with a boatload of third parties constant API updates and changes. If your core competency is s…”

   proof ↗⚑ flag

   Dagster~partialcommunity6/10

   Dagster documents integrations for several major ingestion tools (dbt, Airbyte, Fivetran, dlt) with components that represent connectors as assets, giving a real but narrow catalog rather than a broad marketplace of SaaS/database/file connectors. Community evidence even notes Airflow has a maturity/integrations advantage over Dagster, suggesting the catalog breadth is a known gap. Missing for 10: a large enumerated catalog of maintained SaaS/API/database connectors (e.g. hundreds like Fivetran/Airbyte offer natively), evidence of connector maintenance/versioning cadence, and independent confirmation of catalog breadth beyond a handful of named integrations.

   • [claimed-docs] “Use Dagster's UI or APIs to run subsets of your dbt models, seeds, and snapshots.”
   • [claimed-docs] “Using this integration, you can trigger Airbyte syncs and orchestrate your Airbyte connections from within Dagster”
   • [claimed-docs] “provides a FivetranAccountComponent which can be used to easily represent Fivetran connectors as assets in Dagster”
   • [claimed-docs] “provides a DltLoadCollectionComponent which can be used to easily represent a collection of dlt sources and pipelines as assets in Dagster”
   • [community] “Dagster natively isolates tasks in the DAG into separate Kubernetes pods... I find Dagster's approach is more Pythonic than Airflow's standa…”

   proof ↗⚑ flag

2. data engineerThe catalog tells me each connector's maturity, support level, and maintainer before I depend on it

   weight 1 · round drawn
   Fivetran—none0/10

   The evidence pack shows Fivetran's connector docs describe functionality (schema handling, SDK, REST API) but nowhere provides a catalog exposing per-connector maturity level, support tier, or maintainer identity that a data engineer could check before depending on a connector.

   ⚑ flag

   Dagster—none0/10

   Evidence shows Dagster has an integrations library (dbt, Airbyte, Fivetran, dlt, etc.) but none of the docs pages cite maturity labels, support tiers, or maintainer attribution for these connectors — no catalog page or metadata addressing this story's specific asks is shown.

   • [claimed-docs] “Use Dagster's UI or APIs to run subsets of your dbt models, seeds, and snapshots.”
   • [claimed-docs] “Using this integration, you can trigger Airbyte syncs and orchestrate your Airbyte connections from within Dagster”
   • [claimed-docs] “provides a FivetranAccountComponent which can be used to easily represent Fivetran connectors as assets in Dagster”
   • [claimed-docs] “provides a DltLoadCollectionComponent which can be used to easily represent a collection of dlt sources and pipelines as assets in Dagster”

   proof ↗⚑ flag

Custom connectors

1. data engineerI build a custom connector for a long-tail API with a supported framework or low-code builder, not a fork

   weight 2 · round to Fivetran
   Fivetran✓fullclaimed7/10

   Fivetran documents a first-party Connector SDK for building custom connectors in Python and deploying them as an extension of Fivetran, directly matching the 'supported framework, not a fork' requirement (fivetran-docs-2, fivetran-docs-17). No independent/hands-on evidence specifically validates the SDK's ease-of-use or long-tail API coverage, and no low-code builder option is documented. Missing for 10: independent/hands-on validation of the Connector SDK experience, and evidence of a low-code builder alternative.

   • [claimed-docs] “Fivetran’s Connector SDK allows you to develop a custom data connector using Python and deploy it as an extension of Fivetran.”
   • [claimed-docs] “Develop a custom data connector using Python and deploy it as an extension of Fivetran.”

   proof ↗⚑ flag

   Dagster~partialclaimed6/10

   Dagster's core primitives (asset definitions, resources, IO managers) let engineers write plain Python code to hit any long-tail API, and the dlt integration explicitly exposes a supported framework (DltLoadCollectionComponent) for building custom connectors/sources as Dagster assets — not a fork of existing connector code. However, there's no dedicated 'build a custom connector' guide or low-code builder in the evidence, and the featured integrations (Airbyte, Fivetran, dbt) are pre-built connectors rather than a long-tail custom-connector workflow. Missing for 10: an explicit tutorial/guide for authoring a new API connector via dlt or resources, and independent/hands-on corroboration of someone building a long-tail custom connector this way.

   • [claimed-docs] “An asset definition is a description, in code, of an asset that should exist and how to produce and update that asset.”
   • [claimed-docs] “provides a DltLoadCollectionComponent which can be used to easily represent a collection of dlt sources and pipelines as assets in Dagster”
   • [claimed-docs] “DltLoadCollectionComponent which can be used to easily represent a collection of dlt sources and pipelines as assets in Dagster.”
   • [claimed-docs] “import dagster as dg@dg.assetdef hello(context: dg.AssetExecutionContext): context.log.info("Hello!")@dg.asset(deps=[hello])”
   • [claimed-docs] “You can scaffold Dagster Component definitions in your project from the command line with the dg scaffold defs command”

   proof ↗⚑ flag

Freshness

1. analytics engineerTell how fresh each destination table is and get warned when a pipeline misses its expected cadence

   weight 1 · round drawn
   Fivetran~partialcommunity6/10

   Fivetran's dashboard has a documented 'Alerts' feature (fivetran-docs-15) and an MCP tool explicitly supports querying 'when was the last time my postgres connection completed a sync?' and 'are any of my connections broken?' (fivetran-docs-28), which directly maps to freshness/cadence monitoring. However, docs give no detail on configuring cadence-based SLAs or alert thresholds, and community reports mention syncs occasionally falling out of sync (fivetran-comm-10), suggesting reliability of the underlying freshness signal isn't airtight. Missing for 10: detailed docs on setting expected-cadence thresholds/SLAs, per-table freshness dashboards, and independent confirmation that alerts reliably fire on missed schedules.

   • [claimed-docs] “Fivetran Alerts”
   • [claimed-docs] “It allows you to ask read-only questions like "when was the last time my postgres connection completed a sync?" and "are any of my connectio…”
   • [community] “I've used Fivetran at VC funded startups... I understand the value of not having to build this piece of common infrastructure... we did expe…”

   proof ↗⚑ flag

   Dagster~partialclaimed6/10

   Dagster's asset checks and freshness-check features directly support telling how fresh a destination table is, and Declarative Automation/schedules/sensors combined with Dagster+ alerts can flag when a pipeline misses expected cadence. However, evidence doesn't show a dedicated, end-to-end 'freshness SLA' dashboard or explicit cadence-miss alerting workflow tied specifically to destination tables, only generic building blocks. missing for 10: explicit freshness-policy/SLA UI documentation, concrete example of cadence-miss alert configuration, independent/hands-on confirmation that these features work together as described.

   • [claimed-docs] “Ensure a particular column doesn't contain null values * Verify that a tabular asset adheres to a specified schema * Check if an asset's…”
   • [claimed-docs] “Ensure a particular column doesn't contain null values”
   • [claimed-docs] “Declarative Automation is a framework that uses information about the status of your assets and their dependencies to launch executions of y…”
   • [claimed-docs] “Schedules enable automated execution of jobs at specified intervals.”
   • [claimed-docs] “Sensors enable you to take action in response to events that occur either internally within Dagster or in external systems.”
   • [claimed-docs] “Dagster+ alerts can notify you of critical events occurring in your deployment so you can catch potential issues early”
   • [claimed-docs] “Automation condition evaluations now explain history-dependent conditions (since, newly_true, newly_missing) by showing the remembered value…”

   proof ↗⚑ flag

Monitoring

1. data engineerI see run status, logs, and row counts per sync, and failures alert me in Slack, email, or a webhook

   weight 3 · round to Fivetran
   Fivetran~partialcommunity5/10

   Docs confirm a dedicated 'Fivetran Alerts' feature and an MCP tool that can query sync status/connection health, plus a dashboard for monitoring, but the evidence never specifies row-count reporting, log detail, or the actual Slack/email/webhook alert channels the story asks about. Community reports of syncs randomly failing or needing re-syncs concern reliability, not the observability tooling itself, so this isn't a contradiction. Missing for 10: explicit documentation of row-count-per-sync display, log detail granularity, and confirmation of Slack/email/webhook delivery channels for alerts.

   • [claimed-docs] “Fivetran Alerts”
   • [claimed-docs] “It allows you to ask read-only questions like "when was the last time my postgres connection completed a sync?" and "are any of my connectio…”
   • [community] “I've used Fivetran at VC funded startups... I understand the value of not having to build this piece of common infrastructure... we did expe…”

   proof ↗⚑ flag

   Dagster~partialclaimed4/10

   Dagster provides run status/logs via its webserver UI (dagster-docs-12) and a Dagster+ alerting feature for critical events (dagster-docs-11), plus asset checks that can validate data quality (dagster-docs-3/20). However, the evidence never specifies that alerts can be routed to Slack, email, or webhook, nor does it show row-count-per-sync reporting. missing for 10: explicit documentation of Slack/email/webhook alert channels, and evidence of row-count metrics per sync.

   • [claimed-docs] “Dagster+ alerts can notify you of critical events occurring in your deployment so you can catch potential issues early”
   • [claimed-docs] “A typical Dagster Docker deployment includes a several long-running containers: one for the webserver, one for the daemon, and one for each …”
   • [claimed-docs] “Ensure a particular column doesn't contain null values * Verify that a tabular asset adheres to a specified schema * Check if an asset's…”
   • [claimed-docs] “Ensure a particular column doesn't contain null values”

   proof ↗⚑ flag

Recovery

1. data engineerTransient failures retry automatically and interrupted syncs resume from checkpoints instead of restarting

   weight 2 · round drawn
   Fivetran—none0/10

   No documentation or community evidence directly addresses automatic retry on transient failures or checkpoint-based resume of interrupted syncs; the closest docs only mention 'incremental syncs automatically' and schema-change handling, not failure/resume mechanics. One community report even describes needing a full re-sync after sync got 'out of sync' (fivetran-comm-10), which is not evidence of checkpointed resume. Missing for 10: explicit documentation of retry logic on transient errors, explicit checkpoint/resume mechanism description, and independent confirmation that interrupted syncs resume rather than restart.

   • [claimed-docs] “Fivetran provides pre-built data connectors that automatically sync data from your applications, databases, event streams, and files to your…”
   • [claimed-docs] “Each connector handles schema changes, API updates, and incremental syncs automatically — no data pipelines to maintain.”
   • [community] “I've used Fivetran at VC funded startups... I understand the value of not having to build this piece of common infrastructure... we did expe…”

   proof ↗⚑ flag

   Dagster—none0/10

   The evidence pack contains no mention of retry policies, automatic retry-on-failure, checkpointing, or resuming interrupted runs from partial state — topics like assets, schedules, sensors, and integrations are covered, but reliability/retry mechanics are absent. Missing for 10: any documentation or example of RetryPolicy/op retries, run re-execution from failure, or checkpoint-based resume behavior.

   ⚑ flag

1. ai-native userDo everything through the API that I can do in the UI

   weight 2 · round to Fivetran
   Fivetran~partialprobed6/10

   Fivetran's REST API is documented to let users set up, scale, and manage the account programmatically, and a live probe confirms it is a real, auth-gated API; there's also an official MCP server for connector management. However, no evidence explicitly confirms full UI/API parity (e.g., alerts configuration, RBAC/SCIM setup, dashboard-only features) — missing for 10: explicit parity claim or documentation enumerating every UI feature exposed via API, independent confirmation of no UI-only gaps, and coverage of admin/security features (RBAC, SCIM, alerts) through the API.

   • [claimed-docs] “Set up and scale your data pipeline, and manage your Fivetran account programmatically using the Fivetran REST API.”
   • [claimed-docs] “Fivetran REST API”
   • [claimed-docs] “Connect Cards”
   • [probe] “PROBE runtime (recorded 2026-09-08): Fivetran's documented REST API is live and cleanly auth-gated — a keyless GET https://api.fivetran.com/…”
   • [claimed-docs] “It allows you to ask read-only questions like "when was the last time my postgres connection completed a sync?" and "are any of my connectio…”
   • [claimed-docs] “Set `FIVETRAN_SCOPE` to `read/write` or `read/write/delete` to unlock write and delete operations”

   proof ↗⚑ flag

   Dagster~partialprobed5/10

   Dagster exposes a CLI (dg), a Dagster+ MCP server for taking actions, and mentions using 'UI or APIs' to run dbt subsets, suggesting some parity between UI and programmatic control, but there is no documented comprehensive REST/GraphQL API spec (an OpenAPI probe returned 404 on all candidate endpoints) confirming full feature parity with the UI. missing for 10: an explicit comprehensive API reference (OpenAPI/GraphQL schema) enumerating all UI capabilities, and evidence that every UI action (scheduling, sensors, asset catalog browsing, alerts, etc.) is achievable purely via API/CLI without the UI.

   • [claimed-docs] “Use Dagster's UI or APIs to run subsets of your dbt models, seeds, and snapshots.”
   • [claimed-docs] “The Dagster+ MCP server allows you to access information and take actions in your Dagster+ deployment within an AI session.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.dagster.io/openapi.json, https://docs.dagster.io/swagger.json, https://docs.dagster.io/…”
   • [probe] “official MCP server documented at https://docs.dagster.io/getting-started/ai-tools/dagster-mcp”
   • [probe] “official CLI documented at https://docs.dagster.io/api/clis/dg-cli/dg-cli-configuration”

   proof ↗⚑ flag

2. ai-native userExport all of my data in open formats and leave

   weight 3 · round to Fivetran
   Fivetran~partialclaimed5/10

   Fivetran's core function lands data into the customer's own warehouse/lake, and docs claim data lakes are synced in open table formats, meaning the underlying data isn't locked in Fivetran's own proprietary store. However, there is no documentation addressing exporting pipeline configs, transformation logic, or connector setups in open/portable formats, nor any guidance for fully leaving the platform. Missing for 10: explicit data/config export or migration tooling, documentation on open-format guarantees across all connectors (not just lake sync), and any community confirmation of successful platform exit without lock-in.

   • [claimed-docs] “Automatically sync query‑ready, fully‑managed data to your data lake in open table formats.”
   • [claimed-docs] “Fivetran provides pre-built data connectors that automatically sync data from your applications, databases, event streams, and files to your…”
   • [claimed-docs] “These solutions include the following deployment models: SaaS Deployment... Hybrid Deployment”

   proof ↗⚑ flag

   Dagster~partialclaimed4/10

   Dagster's pipelines are defined as plain Python code (asset definitions, dg CLI scaffolding) and can be self-hosted via Docker, so pipeline logic itself isn't locked into a proprietary format and can be moved off the platform. However, there is no explicit documentation on exporting run history, metadata, or lineage data from Dagster+ (the hosted product) in an open format, and Dagster+ pricing/plan structure implies some cloud-side data may not be portable. Missing for 10: explicit data/metadata export tooling or docs, and evidence on exporting Dagster+ hosted run/lineage history rather than just code definitions.

   • [claimed-docs] “An asset definition is a description, in code, of an asset that should exist and how to produce and update that asset.”
   • [claimed-docs] “A typical Dagster Docker deployment includes a several long-running containers: one for the webserver, one for the daemon, and one for each …”
   • [claimed-docs] “uvx create-dagster@latest project my-project”
   • [claimed-docs] “Solo Plan $10 per month Personal projects and simple pipelines ... 30-day free trial”

   proof ↗⚑ flag

3. ai-native userSelf-host the core product

   weight 3 · round to Dagster
   Fivetran—none0/10

   Fivetran is documented as a SaaS platform with only 'SaaS' and 'Hybrid' deployment models (hybrid refers to deploying local agents for on-prem source connectivity, not self-hosting the core platform); there is no evidence of an open-source or self-hostable core product.

   • [claimed-docs] “Fivetran offers two deployment solutions to facilitate efficient data integration for various business environments.”
   • [claimed-docs] “These solutions include the following deployment models: SaaS Deployment... Hybrid Deployment”

   proof ↗⚑ flag

   Dagster✓fullprobed9/10

   Dagster is open-source and explicitly documents Docker-based self-hosted deployment (webserver, daemon, code location containers), and a runtime probe confirms an agent can scaffold and run a full local Dagster instance end-to-end without any vendor keys. This directly satisfies self-hosting the core product. Missing for 10: no independent third-party audit of production self-hosted deployments at scale beyond docs/probe.

   • [claimed-docs] “A typical Dagster Docker deployment includes a several long-running containers: one for the webserver, one for the daemon, and one for each …”
   • [claimed-docs] “uvx create-dagster@latest project my-project”
   • [probe] “PROBE runtime (recorded 2026-09-08): the full agent-builds-a-project path ran keylessly end to end — `uvx create-dagster@latest project pa-p…”
   • [probe] “PROBE runtime (recorded 2026-09-08): the official dagster CLI installed keylessly from pypi via uvx and printed 'dagster, version 1.13.21'.”

   proof ↗⚑ flag

Dev loop

1. data engineerI run and test a pipeline locally against a lightweight destination before it touches production

   weight 2 · round to Dagster
   Fivetran—none0/10

   No evidence describes any local development or testing mode for Fivetran pipelines against a lightweight/local destination — Fivetran is presented purely as a cloud-hosted, managed SaaS sync platform with deployment models (SaaS/Hybrid) but no local sandbox or dry-run testing workflow.

   • [claimed-docs] “Fivetran offers two deployment solutions to facilitate efficient data integration for various business environments.”
   • [claimed-docs] “These solutions include the following deployment models: SaaS Deployment... Hybrid Deployment”

   proof ↗⚑ flag

   Dagster✓fullprobed7/10

   Dagster explicitly supports a full local dev loop: `uvx create-dagster` scaffolds a project and `dagster dev`/`uv run dagster dev` boots a local webserver, verified in a live runtime probe, and asset checks let engineers validate data before promotion. Community evidence also confirms real-world local dev-to-prod use with lightweight destinations like DuckDB (Dagster+dbt+DuckDB stack) and Dagster's own stated goal of 'seamless end-to-end dev experience from laptop to CI to dev to prod.' Missing for 10: explicit first-party documentation on swapping resources/IO managers between a lightweight local destination and production, and independent hands-on confirmation of that specific swap pattern.

   • [probe] “PROBE runtime (recorded 2026-09-08): the full agent-builds-a-project path ran keylessly end to end — `uvx create-dagster@latest project pa-p…”
   • [claimed-docs] “Ensure a particular column doesn't contain null values * Verify that a tabular asset adheres to a specified schema * Check if an asset's…”
   • [claimed-docs] “Ensure a particular column doesn't contain null values”
   • [community] “I've been working with this stack (Dagster, dbt, DuckDB) for a few months and am super happy with how well everything plays together.”
   • [community] “Dagster team response: goals include (1) Local development - seamless end-to-end dev experience from laptop to CI to dev to prod, (2) managi…”
   • [claimed-docs] “uvx create-dagster@latest project my-project”

   proof ↗⚑ flag

Lineage

1. data engineerI see end-to-end lineage of my datasets — which sources, steps, and transformations produced each table

   weight 2 · round to Dagster
   Fivetran—none0/10

   The evidence pack shows connectors, transformations, and dbt integration but contains no mention of a lineage graph, catalog, or end-to-end visualization tracing sources through transformations to output tables — a capability a data movement/ELT platform could plausibly offer. Missing for 10: any lineage/catalog feature documentation, column-level or table-level lineage visualization, and evidence of tracing transformation steps end-to-end.

   • [claimed-docs] “Orchestrate pre-built and custom data transformations in your destination with Fivetran.”
   • [claimed-docs] “Use the Fivetran-hosted dbt Core integration or our third-party dbt Cloud and Coalesce orchestration to centralize and manage all your trans…”
   • [claimed-docs] “We created data models that transform your data into analytics-ready tables. You can either add the models in the Fivetran dashboard (Quicks…”

   proof ↗⚑ flag

   Dagster~partialclaimed6/10

   Dagster's asset-based model explicitly encodes dependencies between assets (dagster-docs-1, dagster-docs-17 show deps=[hello]) and integrations (dbt, Airbyte, Fivetran, dlt) represent upstream data sources as assets in the same graph (dagster-docs-7/8/9/10), which together constitute an end-to-end lineage graph from source to transformation. However, the evidence pack never explicitly names or shows the Asset Graph/lineage UI itself, nor independent confirmation that lineage visualization works well in practice. Missing for 10: explicit documentation/screenshot of the lineage/asset-graph visualization UI, and independent/hands-on corroboration of viewing end-to-end lineage across tools.

   • [claimed-docs] “An asset definition is a description, in code, of an asset that should exist and how to produce and update that asset.”
   • [claimed-docs] “import dagster as dg@dg.assetdef hello(context: dg.AssetExecutionContext): context.log.info("Hello!")@dg.asset(deps=[hello])”
   • [claimed-docs] “Use Dagster's UI or APIs to run subsets of your dbt models, seeds, and snapshots.”
   • [claimed-docs] “Using this integration, you can trigger Airbyte syncs and orchestrate your Airbyte connections from within Dagster”
   • [claimed-docs] “provides a FivetranAccountComponent which can be used to easily represent Fivetran connectors as assets in Dagster”
   • [claimed-docs] “provides a DltLoadCollectionComponent which can be used to easily represent a collection of dlt sources and pipelines as assets in Dagster”

   proof ↗⚑ flag

Orchestration

1. data engineerI define dependencies between pipeline steps and datasets, and the platform orchestrates runs in the right order

   weight 2 · round to Dagster
   Fivetran~partialclaimed4/10

   Fivetran documents orchestrating transformations after connector syncs complete (e.g., triggering dbt Core/Cloud/Coalesce transformations once ingestion finishes), which is a basic dependency-based run ordering between sync and transform steps. However, there is no evidence of a general-purpose DAG/dependency model across arbitrary pipeline steps and datasets, cross-connector dependency definition, or explicit scheduling controls beyond built-in sync/transform triggers. Missing for 10: explicit dependency graph definition across multiple connectors/datasets, custom step ordering, and independent evidence of complex multi-stage orchestration beyond the sync-then-transform pattern.

   • [claimed-docs] “Orchestrate pre-built and custom data transformations in your destination with Fivetran.”
   • [claimed-docs] “Use the Fivetran-hosted dbt Core integration or our third-party dbt Cloud and Coalesce orchestration to centralize and manage all your trans…”
   • [claimed-docs] “We created data models that transform your data into analytics-ready tables. You can either add the models in the Fivetran dashboard (Quicks…”

   proof ↗⚑ flag

   Dagster✓fullprobed9/10

   Dagster's core model is asset/job definitions with explicit dependencies (deps=[...]) that the platform resolves into execution order, backed by schedules/sensors/declarative automation for orchestrating runs, and this is corroborated by hands-on runtime probes confirming a working project actually runs (dagster dev boots, webserver responds). Community feedback also affirms the asset-dependency approach as a core differentiator vs task-based tools. Missing for 10: independent large-scale production case study detailing complex DAG ordering at scale.

   • [claimed-docs] “An asset definition is a description, in code, of an asset that should exist and how to produce and update that asset.”
   • [claimed-docs] “import dagster as dg@dg.assetdef hello(context: dg.AssetExecutionContext): context.log.info("Hello!")@dg.asset(deps=[hello])”
   • [claimed-docs] “Schedules enable automated execution of jobs at specified intervals.”
   • [claimed-docs] “Sensors enable you to take action in response to events that occur either internally within Dagster or in external systems.”
   • [claimed-docs] “Declarative Automation is a framework that uses information about the status of your assets and their dependencies to launch executions of y…”
   • [community] “Dagster natively isolates tasks in the DAG into separate Kubernetes pods... I find Dagster's approach is more Pythonic than Airflow's standa…”
   • [community] “I believe Dagster is hitting the right chord: they focus on the pain points in DX for Airflow and similar solutions, they have figured out h…”
   • [probe] “PROBE runtime (recorded 2026-09-08): the full agent-builds-a-project path ran keylessly end to end — `uvx create-dagster@latest project pa-p…”

   proof ↗⚑ flag

Pricing

1. data platform leadThe pricing model is published and predictable — I can estimate what a new source costs before connecting it

   weight 2 · round to Fivetran
   Fivetran!disputedcontradicted4/10

   Fivetran publishes a usage-based pricing model (MAR - monthly active rows) with a public pricing page, so pricing is documented and formulaic (fivetran-docs-9, fivetran-docs-21, fivetran-docs-27). However, multiple independent accounts concretely contradict the 'predictable/estimable' claim: users report unpredictable billing spikes, being billed for inflated row counts due to Fivetran's join logic, and needing to closely monitor usage during a 2-week trial to avoid surprise costs — meaning a lead often cannot accurately estimate a new source's cost before connecting it. Missing for 10: a documented pre-connection cost calculator/estimator tool, and resolution of the inflated-row-count billing disputes.

   • [claimed-docs] “Fivetran’s pricing model involves four basic principles: _Pricing is usage-based_. You are charged based on what you use each month.”
   • [claimed-docs] “Pricing is usage-based. You are charged based on what you use each month.”
   • [claimed-docs] “500,000 monthly active rows (MAR) for connections”
   • [community] “Fivetran's syncing has been very reliable (compared to others we tried) but the "active row" based pricing is unpredictable and can have hug…”
   • [community] “Be careful with fivetran - they inflate your data and then bill you for it. In our case, they inflated by ~10x the record count by doing a j…”
   • [community] “Fivetran's free plan has met my needs to sync data from different ad platforms to BigQuery pretty well. One of their pitfalls is charging by…”

   proof ↗⚑ flag

   Dagster—none0/10

   The only pricing evidence is a generic plan listing (Solo Plan $10/month) with no unit economics tied to data sources, connectors, or compute usage that would let a platform lead estimate the cost impact of connecting a new source before doing so. Missing for 10: any documented cost driver (e.g., per-asset, per-run, or per-source pricing), usage calculator, or worked example showing how adding a new connector/source changes the bill.

   • [claimed-docs] “Solo Plan $10 per month Personal projects and simple pipelines ... 30-day free trial”

   proof ↗⚑ flag

1. ai-native userControl data retention and deletion

   weight 2 · round to Fivetran
   Fivetran~partialclaimed5/10

   Fivetran documents delete capture, soft delete/history modes, data blocking/column hashing, and an MCP scope that can be restricted to read-only or expanded to read/write/delete, giving some control over data lifecycle and access. However, there is no explicit documentation of a data retention policy, configurable TTLs, or an end-to-end account/data deletion workflow for AI-native/API-driven use. Missing for 10: documented data retention/TTL controls, explicit account-level or dataset-level deletion API/workflow, and independent confirmation that deletion requests are honored.

   • [claimed-docs] “Fivetran captures deletes whene”
   • [claimed-docs] “Data Blocking and Column Hashing”
   • [claimed-docs] “Soft Delete Mode ... Live Mode ... History Mode”
   • [claimed-docs] “Set `FIVETRAN_SCOPE` to `read/write` or `read/write/delete` to unlock write and delete operations”

   proof ↗⚑ flag

   Dagster~partialclaimed3/10

   Dagster docs mention a feature for 'wiping and deleting dynamic partitions in a single action,' which gives some control over deleting specific partition data, but there is no documentation of broader data-retention policies (e.g., run history/log retention, PII deletion, GDPR controls) that an AI-native user could configure. missing for 10: retention policy configuration for run/event logs, documented data-deletion/export workflows, compliance-oriented retention settings, independent corroboration of these controls in practice.

   • [claimed-docs] “wiping and deleting dynamic partitions in a single action now also supports multi-partitioned assets that use the dynamic partitions definit…”

   proof ↗⚑ flag

2. ai-native userOpt out of telemetry and usage tracking

   weight 2 · round drawn
   Fivetran—none0/10

   No evidence in the pack addresses telemetry or usage-tracking opt-out settings for Fivetran; the docs cover connectors, transformations, pricing, and API access but never mention privacy controls for AI-native usage tracking.

   ⚑ flag

   Dagster—none0/10

   No evidence pack item mentions telemetry, usage tracking, or opt-out settings for Dagster; this is an applicable axis for a data orchestration platform but no documentation or community evidence addresses it.

   ⚑ flag

Reverse etl

1. analytics engineerI sync modeled warehouse data back into SaaS tools (CRM, ads, support) to activate it where teams work

   weight 2 · round drawn
   Fivetran—none0/10

   All evidence describes Fivetran connectors moving data INTO the warehouse/data lake from applications, databases, and event streams — the opposite direction from what this story requires. There is no mention of syncing modeled warehouse data back out to CRM, ads, or support SaaS tools (reverse ETL/activation use case).

   • [claimed-docs] “Fivetran provides pre-built data connectors that automatically sync data from your applications, databases, event streams, and files to your…”
   • [claimed-docs] “Each connector handles schema changes, API updates, and incremental syncs automatically — no data pipelines to maintain.”
   • [claimed-docs] “Fivetran provides pre-built data connectors that automatically sync data from your applications, databases, event streams, and files to your…”

   proof ↗⚑ flag

   Dagster—none0/10

   Dagster's integrations documented here (dbt, Airbyte, Fivetran, dlt) are for ingesting/transforming warehouse data, not for syncing modeled data back out to CRM/ads/support SaaS tools; no reverse-ETL connector or activation-specific capability (e.g., Census/Hightouch equivalent, Salesforce/HubSpot writers) appears anywhere in the evidence pack.

   ⚑ flag

Evolution

1. data engineerUpstream schema changes are detected and propagated by a policy I choose, instead of silently breaking loads

   weight 3 · round drawn
   Fivetran~partialclaimed5/10

   Fivetran docs confirm connectors automatically handle upstream schema changes without pipelines breaking, plus sync modes (soft delete, history mode) that give some control over how changes propagate, but there is no evidence of a configurable policy (e.g., block/notify/allow options for schema drift, column additions/removals) that lets a data engineer choose how changes propagate versus being auto-applied. missing for 10: documented schema-change policy options (block vs auto-propagate vs alert), granular control over new columns/tables, and independent confirmation that this prevents silent breakage in practice.

   • [claimed-docs] “Fivetran provides pre-built data connectors that automatically sync data from your applications, databases, event streams, and files to your…”
   • [claimed-docs] “Each connector handles schema changes, API updates, and incremental syncs automatically — no data pipelines to maintain.”
   • [claimed-docs] “Soft Delete Mode ... Live Mode ... History Mode”
   • [claimed-docs] “Fivetran Alerts”

   proof ↗⚑ flag

   Dagster~partialclaimed5/10

   Dagster provides generic primitives that could be composed into a schema-change policy: asset checks can 'verify that a tabular asset adheres to a specified schema' (dagster-docs-3, dagster-docs-20), sensors can react to internal/external events (dagster-docs-5), and Declarative Automation can launch downstream runs based on asset/dependency status (dagster-docs-6). However, there is no first-party feature specifically for detecting upstream schema drift and applying a chosen propagation policy (e.g., automatic column mapping, contract versioning, or schema-diff alerts) — engineers would need to hand-build this from checks+sensors themselves. missing for 10: a dedicated schema-change-detection/propagation feature, docs showing schema diffing across runs, and independent/hands-on confirmation that this composed approach reliably prevents silent breakage.

   • [claimed-docs] “Ensure a particular column doesn't contain null values * Verify that a tabular asset adheres to a specified schema * Check if an asset's…”
   • [claimed-docs] “Ensure a particular column doesn't contain null values”
   • [claimed-docs] “Sensors enable you to take action in response to events that occur either internally within Dagster or in external systems.”
   • [claimed-docs] “Declarative Automation is a framework that uses information about the status of your assets and their dependencies to launch executions of y…”

   proof ↗⚑ flag

Normalization

1. analytics engineerLoaded data lands as typed, deduplicated destination tables ready to query, not raw JSON blobs

   weight 1 · round to Fivetran
   Fivetran✓fullcommunity7/10

   Fivetran docs describe connectors that land data as structured destination tables with automatic schema handling and type mapping (docs-18, docs-33), history/soft-delete sync modes that manage deduplication and deletes (docs-35, docs-13), and transformation layers producing 'analytics-ready tables' (docs-25). This directly supports typed, deduplicated tables rather than raw JSON blobs. Missing for 10: independent hands-on verification of deduplication correctness, and community evidence (comm-10) notes occasional out-of-sync issues requiring re-syncs, which slightly tempers confidence.

   • [claimed-docs] “Each connector handles schema changes, API updates, and incremental syncs automatically — no data pipelines to maintain.”
   • [claimed-docs] “Custom Data Type Mapping”
   • [claimed-docs] “Soft Delete Mode ... Live Mode ... History Mode”
   • [claimed-docs] “Fivetran captures deletes whene”
   • [claimed-docs] “We created data models that transform your data into analytics-ready tables. You can either add the models in the Fivetran dashboard (Quicks…”
   • [community] “I've used Fivetran at VC funded startups... I understand the value of not having to build this piece of common infrastructure... we did expe…”

   proof ↗⚑ flag

   Dagster~partialclaimed5/10

   Dagster provides asset checks to validate schema and null constraints on tabular assets, and integrates with dbt/Fivetran/Airbyte/dlt which perform the actual typing/deduplication of loaded data, but Dagster itself is an orchestrator, not the engine producing typed/deduplicated destination tables. Missing for 10: direct evidence of Dagster performing deduplication logic, native typed-table materialization, and hands-on confirmation that end-to-end loaded tables are clean and query-ready rather than requiring the coupled dbt/Fivetran/dlt tooling to do the real work.

   • [claimed-docs] “Ensure a particular column doesn't contain null values * Verify that a tabular asset adheres to a specified schema * Check if an asset's…”
   • [claimed-docs] “Use Dagster's UI or APIs to run subsets of your dbt models, seeds, and snapshots.”
   • [claimed-docs] “provides a FivetranAccountComponent which can be used to easily represent Fivetran connectors as assets in Dagster”
   • [claimed-docs] “provides a DltLoadCollectionComponent which can be used to easily represent a collection of dlt sources and pipelines as assets in Dagster”
   • [claimed-docs] “Ensure a particular column doesn't contain null values”

   proof ↗⚑ flag

Backfill

1. data engineerBackfill history or resync a single table without rebuilding the whole pipeline

   weight 2 · round to Dagster
   Fivetran~partialcommunity4/10

   Docs mention granular sync modes (Soft Delete, Live, History Mode) and automatic incremental syncs, which imply some ability to manage sync behavior at a table level, but no evidence explicitly documents a self-serve 'resync single table' or 'backfill history' UI/API action. Community evidence only shows a full pipeline re-sync handled by Fivetran support, not a self-service single-table resync. Missing for 10: explicit documentation of a per-table resync/backfill feature, API/dashboard control to trigger it, and independent confirmation it works without rebuilding the whole connector.

   • [claimed-docs] “Soft Delete Mode ... Live Mode ... History Mode”
   • [claimed-docs] “Each connector handles schema changes, API updates, and incremental syncs automatically — no data pipelines to maintain.”
   • [community] “I've used Fivetran at VC funded startups... I understand the value of not having to build this piece of common infrastructure... we did expe…”

   proof ↗⚑ flag

   Dagster~partialclaimed6/10

   Dagster's asset-based model supports partitioned assets and explicitly supports wiping/deleting dynamic partitions (including multi-partitioned assets) for re-materialization, and asset checks can detect if an asset needs refreshing — both enabling backfill/resync of a single table without rerunning the whole pipeline. However, evidence doesn't show a dedicated 'backfill single partition/table' UI walkthrough or hands-on confirmation of partition-level backfill workflows in practice. missing for 10: explicit documentation/example of the backfill UI/CLI workflow for a single partition or asset, independent/hands-on validation of backfill behavior in production use.

   • [claimed-docs] “wiping and deleting dynamic partitions in a single action now also supports multi-partitioned assets that use the dynamic partitions definit…”
   • [claimed-docs] “Ensure a particular column doesn't contain null values * Verify that a tabular asset adheres to a specified schema * Check if an asset's…”
   • [claimed-docs] “Ensure a particular column doesn't contain null values”
   • [claimed-docs] “An asset definition is a description, in code, of an asset that should exist and how to produce and update that asset.”

   proof ↗⚑ flag

Cdc

1. data engineerI replicate databases with log-based CDC (binlog/WAL) so I capture updates and deletes without hammering the source

   weight 3 · round to Fivetran
   Fivetran~partialclaimed4/10

   Docs confirm Fivetran captures deletes and offers incremental, automated syncs without manual pipeline maintenance (fivetran-docs-13, fivetran-docs-18, fivetran-docs-35 sync modes), which is consistent with CDC-style replication, but the evidence pack never explicitly names log-based CDC, binlog, or WAL mechanisms for database connectors. Missing for 10: explicit documentation of binlog/WAL-based CDC mechanism, evidence of low source-load impact, and independent/hands-on confirmation of CDC behavior for specific databases.

   • [claimed-docs] “Fivetran captures deletes whene”
   • [claimed-docs] “Each connector handles schema changes, API updates, and incremental syncs automatically — no data pipelines to maintain.”
   • [claimed-docs] “Soft Delete Mode ... Live Mode ... History Mode”
   • [claimed-docs] “1-minute syncs”

   proof ↗⚑ flag

   Dagster—none0/10

   Dagster's evidence shows it orchestrates and triggers syncs via Airbyte/Fivetran/dlt integrations, but nothing in the pack describes Dagster itself (or these integrations, as documented) performing log-based CDC (binlog/WAL) capture of inserts/updates/deletes. The story's specific mechanism—low-impact log-based replication—is unaddressed; Dagster is positioned as an orchestrator that calls out to these tools, not as the CDC engine itself.

   • [claimed-docs] “Using this integration, you can trigger Airbyte syncs and orchestrate your Airbyte connections from within Dagster”
   • [claimed-docs] “provides a FivetranAccountComponent which can be used to easily represent Fivetran connectors as assets in Dagster”
   • [claimed-docs] “FivetranAccountComponent can be used to easily represent Fivetran connectors as assets in Dagster.”
   • [claimed-docs] “provides a DltLoadCollectionComponent which can be used to easily represent a collection of dlt sources and pipelines as assets in Dagster”
   • [claimed-docs] “DltLoadCollectionComponent which can be used to easily represent a collection of dlt sources and pipelines as assets in Dagster.”

   proof ↗⚑ flag

Incremental

1. data engineerSyncs move only new and changed records — cursor and state management handled for me, not full reloads

   weight 3 · round to Fivetran
   Fivetran~partialcommunity7/10

   Fivetran's docs explicitly describe automated incremental syncs (cursor/state handled per connector) with delete-capture and multiple sync modes (Soft Delete/Live/History) so users don't need to manage full reloads themselves. However, a hands-on community report describes occasional (roughly bimonthly) ETL desync incidents requiring a full re-sync, showing the incremental mechanism isn't always flawless in practice. Missing for 10: technical detail on how cursors/state are stored/exposed, and independent benchmarking confirming incremental-only data movement at scale without periodic full-reload fallbacks.

   • [claimed-docs] “Fivetran provides pre-built data connectors that automatically sync data from your applications, databases, event streams, and files to your…”
   • [claimed-docs] “Each connector handles schema changes, API updates, and incremental syncs automatically — no data pipelines to maintain.”
   • [claimed-docs] “Fivetran provides pre-built data connectors that automatically sync data from your applications, databases, event streams, and files to your…”
   • [claimed-docs] “Fivetran captures deletes whene”
   • [claimed-docs] “Soft Delete Mode ... Live Mode ... History Mode”
   • [community] “I've used Fivetran at VC funded startups... I understand the value of not having to build this piece of common infrastructure... we did expe…”

   proof ↗⚑ flag

   Dagster—none0/10

   Dagster orchestrates external sync tools (Fivetran, Airbyte, dlt) and represents their connectors as assets, but the evidence never shows Dagster itself managing cursors/incremental-state for syncs — that logic lives in the underlying EL tools, not in Dagster's own asset/partition framework. No documentation shows Dagster performing incremental-only data movement or state tracking on its own.

   • [claimed-docs] “Using this integration, you can trigger Airbyte syncs and orchestrate your Airbyte connections from within Dagster”
   • [claimed-docs] “provides a FivetranAccountComponent which can be used to easily represent Fivetran connectors as assets in Dagster”
   • [claimed-docs] “provides a DltLoadCollectionComponent which can be used to easily represent a collection of dlt sources and pipelines as assets in Dagster”
   • [claimed-docs] “FivetranAccountComponent can be used to easily represent Fivetran connectors as assets in Dagster.”
   • [claimed-docs] “DltLoadCollectionComponent which can be used to easily represent a collection of dlt sources and pipelines as assets in Dagster.”

   proof ↗⚑ flag

Scheduling

1. data engineerI control sync frequency per pipeline — from sub-hour schedules to cron expressions and manual triggers

   weight 2 · round to Dagster
   Fivetran~partialclaimed4/10

   Docs confirm configurable sync frequency down to 1-minute syncs on higher tiers and REST API access to manage pipelines programmatically, implying some control over scheduling, but there is no evidence of cron-expression scheduling or explicit manual trigger functionality per connector. missing for 10: cron expression scheduling, documented manual/on-demand sync trigger, per-pipeline frequency configuration details beyond pricing tier mention.

   • [claimed-docs] “1-minute syncs”
   • [claimed-docs] “Fivetran REST API”
   • [claimed-docs] “Set up and scale your data pipeline, and manage your Fivetran account programmatically using the Fivetran REST API.”

   proof ↗⚑ flag

   Dagster✓fullprobed8/10

   Dagster natively supports cron-based schedules for sub-hour or any interval, event-driven sensors, declarative automation conditions, and manual/ad-hoc job runs, giving fine-grained per-pipeline sync control; this is corroborated by docs and a runtime probe confirming the platform actually runs. missing for 10: no independent case study specifically demonstrating sub-hour scheduling in production or explicit per-asset frequency override examples.

   • [claimed-docs] “Schedules enable automated execution of jobs at specified intervals.”
   • [claimed-docs] “Sensors enable you to take action in response to events that occur either internally within Dagster or in external systems.”
   • [claimed-docs] “Declarative Automation is a framework that uses information about the status of your assets and their dependencies to launch executions of y…”
   • [probe] “PROBE runtime (recorded 2026-09-08): the full agent-builds-a-project path ran keylessly end to end — `uvx create-dagster@latest project pa-p…”

   proof ↗⚑ flag

Dbt

1. analytics engineerDbt transformations run against freshly loaded data as part of the pipeline, not on a blind timer

   weight 2 · round to Dagster
   Fivetran~partialclaimed6/10

   Fivetran docs confirm built-in orchestration of dbt transformations (hosted dbt Core integration, dbt Cloud/Coalesce orchestration) that runs after data loads rather than a separate scheduled job, and pre-built Quickstart/dbt data models are triggered as part of the pipeline. However, the docs don't explicitly describe the trigger mechanism (e.g., 'runs immediately after each successful sync') or confirm it isn't timer-based in some configurations, and there's no independent/hands-on confirmation of this exact behavior. Missing for 10: explicit documentation of the sync-completion trigger mechanism, and community/hands-on validation that transformations reliably fire post-sync rather than on a schedule.

   • [claimed-docs] “Orchestrate pre-built and custom data transformations in your destination with Fivetran.”
   • [claimed-docs] “Use the Fivetran-hosted dbt Core integration or our third-party dbt Cloud and Coalesce orchestration to centralize and manage all your trans…”
   • [claimed-docs] “We created data models that transform your data into analytics-ready tables. You can either add the models in the Fivetran dashboard (Quicks…”

   proof ↗⚑ flag

   Dagster✓fullcommunity8/10

   Dagster models dbt models as assets with explicit dependencies, and provides Declarative Automation and sensors that launch asset executions based on upstream data/asset status rather than only fixed schedules, directly enabling dbt runs triggered by fresh data arrival. The dbt integration lets you run models/seeds/snapshots via the UI/API tied to asset dependency graphs, and asset checks can verify if data needs refreshing before/after transformation. missing for 10: independent or hands-on evidence specifically showing a dbt-on-freshness (event-driven, not timer) pipeline in production use; community evidence only confirms Dagster+dbt+DuckDB works well generally, not the freshness-trigger mechanic specifically.

   • [claimed-docs] “Declarative Automation is a framework that uses information about the status of your assets and their dependencies to launch executions of y…”
   • [claimed-docs] “Sensors enable you to take action in response to events that occur either internally within Dagster or in external systems.”
   • [claimed-docs] “Use Dagster's UI or APIs to run subsets of your dbt models, seeds, and snapshots.”
   • [claimed-docs] “Ensure a particular column doesn't contain null values * Verify that a tabular asset adheres to a specified schema * Check if an asset's…”
   • [community] “I've been working with this stack (Dagster, dbt, DuckDB) for a few months and am super happy with how well everything plays together.”

   proof ↗⚑ flag