Navigable Artifacts

{
  "id": "vercel-workflows-vs-cloudflare-workflows",
  "topic": "Compare Vercel Workflows vs Cloudflare Workflows for durable execution",
  "generated_at": "2026-05-09",
  "source_summary": {
    "subject_a": {
      "vendor": "Vercel",
      "name": "Vercel Workflows",
      "source_count": 8,
      "claim_count": 149
    },
    "subject_b": {
      "vendor": "Cloudflare",
      "name": "Cloudflare Workflows",
      "source_count": 9,
      "claim_count": 158
    },
    "third_party_claim_count": 34,
    "total_claims": 341
  }
}

{
  "subject_a_position": "Vercel Workflows uses build-time directives ('use workflow', 'use step') that turn ordinary async TypeScript or Python functions into durable workflows, with step identity derived implicitly from code structure and orchestration compiled away so workflow code looks like normal function calls.",
  "subject_b_position": "Cloudflare Workflows uses an explicit class-based model where developers extend WorkflowEntrypoint and wrap each unit of work in step.do('explicit-name', async () => ...), with developer-supplied string names acting as deterministic cache keys for memoized step results.",
  "verdict": {
    "winner": "depends_on_workload",
    "rationale": "Vercel's directive model wins for teams who want orchestration to feel like ordinary application code and value AI SDK ergonomics; Cloudflare's explicit step IDs win for workloads where refactor-safety, debuggability, and predictable step identity across deployments matter more than terseness."
  },
  "scoring": {
    "brief_priority": 3,
    "evidence_density": 11,
    "disagreement_intensity": 3,
    "reader_decision_impact": {
      "score": 3,
      "reasoning": "This is the sharpest design fork between the two products and directly determines how a developer writes, refactors, and reasons about durable code, making it a primary basis for choosing between them."
    },
    "composite_weight": 9.745
  }
}

{
  "name": "magic_strings_vs_explicit_identity",
  "type": "design_disagreement_between_subjects",
  "summary": "Build-time directives (Vercel) derive step identity implicitly vs explicit step IDs (Cloudflare) — the sharpest design debate, with Inngest critiquing Vercel's approach.",
  "subject_a_position": "Vercel uses build-time directives ('use workflow', 'use step') that derive step identity implicitly from code structure during compilation...",
  "subject_a_steelman": "Directives let developers write workflows as plain async functions with no API surface to learn — the same mental model as the rest of their Vercel application...",
  "subject_b_position": "Cloudflare requires explicit step.do() calls with developer-assigned string IDs, making each step's state key a literal string in the source...",
  "subject_b_steelman": "Explicit IDs decouple workflow state from code structure: a developer can insert steps, reorder logic, add logging, or refactor freely...",
  "external_voice": "Inngest",
  "critique_summary": "Inngest argues that implicit, code-position-derived step identity is fragile under refactoring and that build-time compilation hides what actually runs from the developer who wrote it.",
  "narrative_payload": "Vercel derives step identity at build time from the structure of the code itself; Cloudflare requires the developer to assign a string ID to every step.do() call...",
  "draft_placement": "Section 2, first subsection: 'Programming model and step identity'",
  "steelman_quality": "both_strong",
  "scoring": {
    "composite_weight": 9.33,
    "reader_decision_impact": {
      "score": 3,
      "reasoning": "Step identity directly determines refactor safety, debugging experience, and long-term maintainability..."
    }
  }
}

[
  {
    "type": "evidence_density_imbalance",
    "description": "State persistence is documented far more heavily on the Cloudflare side (38 claims) than the Vercel side (5 claims).",
    "implication": "The asymmetry reveals what each company believes its product *is*. Vercel believes Workflows is a programming model — state is an implementation concern hidden behind directives. Cloudflare believes Workflows is a runtime primitive — state is part of the surface area developers must understand.",
    "draft_treatment": "Surface in the 'State persistence and where code runs' subsection as the architectural through-line."
  },
  {
    "type": "evidence_density_imbalance",
    "description": "Observability and testing has 17 claims on the Cloudflare side (plus 6 third-party) and zero on the Vercel side in the extracted corpus.",
    "implication": "Cloudflare's explicit attention to testing tooling — and their public acknowledgment of where it was weak — is a real signal about DX maturity trajectory."
  },
  {
    "type": "feature_framing_difference",
    "description": "Steps are framed as a compile-time language feature on Vercel (\"use step\" directive) and as an explicit runtime API call on Cloudflare (step.do(id, fn)).",
    "implication": "This is the load-bearing programming-model difference. It determines refactor behavior, debugging clarity, and what each product feels like to use day-to-day."
  },
  {
    "type": "concept_hierarchy",
    "description": "Cloudflare Workflows is documented as sitting on top of a more architecturally fundamental, separately-documented primitive (Durable Objects).",
    "implication": "Cloudflare exposes its substrate as a primitive developers can compose with directly; Vercel keeps its substrate behind the application abstraction."
  },
  {
    "type": "evidence_density_imbalance",
    "description": "Language support has 6 Vercel claims and 14 Cloudflare claims, but the substantive story inverts the count.",
    "implication": "Vercel ships TypeScript and Python with feature parity (a real differentiator). Cloudflare's higher claim density covers TypeScript-first plus a more recent, more limited Python story."
  },
  {
    "type": "terminology",
    "description": "The two products use different vocabulary for the same underlying concepts. Vercel speaks of 'workflows' and 'steps'; Cloudflare speaks of 'workflow instances' and steps as method calls.",
    "implication": "The terminology gap reflects the state asymmetry. Cloudflare needs 'instance' as a first-class term because each instance is a separately addressable, separately stateful entity."
  }
]