Frameworkby LangChainCUR
Coverage gap: Stateful Workflow Graphs
Coverage gap · HypothesisOverall 58.4 / 100 DERConfidence Low DERCalculated
Only 38 indexed products match "Stateful Workflow Graphs" by keyword DER, inside a much larger parent category. This is a hypothesis, not a validated market: demand was inferred from the parent and discounted, and a missing record is not proof that anyone wants it. Score 58.4 of 100, confidence Low, as of 2026-11-21.
Not indexed by search engines: coverage-gap hypothesis: demand is a proxy, not measured.
Score breakdown
Contribution = weight × component score. The contributions add up to the overall score.
| Component | Weight | Score | Score (0–100) | Contribution | Kind |
|---|---|---|---|---|---|
| Demand | 0.25 | 58.0 | 0.25 × 58.0 = 14.50 | Heuristic | |
| Competition gap | 0.20 | 72.0 | 0.20 × 72.0 = 14.40 | Measured | |
| Monetisation | 0.20 | 65.0 | 0.20 × 65.0 = 13.00 | Heuristic | |
| Growth (relative) | 0.15 | 17.0 | 0.15 × 17.0 = 2.55 | Measured | |
| Feasibility | 0.10 | 60.0 | 0.10 × 60.0 = 6.00 | Heuristic | |
| Distribution | 0.10 | 79.0 | 0.10 × 79.0 = 7.90 | Measured | |
| Overall | 1.00 | 58.35 → 58.4 |
Solid bars are measured components; dashed outlines are rules of thumb. The full formula is on the radar page.
Confidence: Low
Rule: every coverage gap is Low.
What would raise it
- Confidence for coverage gaps is fixed at Low: demand is inferred from the parent category. It would rise only with a direct demand measurement for this capability (none is connected), or with researcher review of products the keyword rules missed.
The opportunity
All text in this section is generated by rule from the record. It is a starting point, not research.
- Description
- Durable, graph-based agent execution. Few indexed products offer it, although the surrounding category (Agent Orchestration) is large.DER
- Problem
- Only 38 indexed products match "Stateful Workflow Graphs", against 671 in Agent Orchestration overall.DER
- Target users
- Teams already using agents for agent orchestrationHEU
- Product form
- MCP server, agent skill or pluginHEU
- Revenue model
- Not assessedHEU
- Complexity
- Not assessedHEU
- Competition level
- HighDER
- Subject
- Stateful Workflow Graphs (capability)
Evidence for
4 row(s) from opportunity_evidence.
DemandHeuristicHEUvalue 1,560,914
The parent category Agent Orchestration holds 671 products with 1,560,914 combined GitHub stars (96th percentile of subcategories). Interest in the parent is only a proxy — demand for this exact capability was not measured — so the percentile is discounted by 40% to 58.
/categories/agent-infrastructure/agent-frameworks/agent-orchestration/
Competition gapMeasuredDERvalue 38
38 indexed products match this capability by keyword.
MonetisationHeuristicHEU
Rule of thumb by ecosystem (Agent Infrastructure); no pricing data behind it.
DistributionMeasuredDERvalue 37
37 of 47 tracked agent platforms document MCP support.
Evidence against
3 row(s) from opportunity_evidence.
Competition gapHeuristicHEU
Classification is keyword-based: products that offer this without naming it are not counted, so the real gap may be smaller.
Growth (relative)MeasuredDERvalue 173
173 launches in the parent category in the last 90 days versus 121 in the previous 90.
FeasibilityHeuristicHEU
Technical feasibility was not assessed for this capability; a neutral 60 is used.
Existing products
All Stateful Workflow Graphs productsThe most notable profiled products matching this capability (up to 8). 38 indexed in total.
Frameworkby LettaCUR
Infrastructureby Temporal TechnologiesCUR
SDKby cloudflareCUR
Infrastructureby RestateCUR
Libraryby DBOSCUR
Agent projectby daprHEU
MCP serverby plastic-labsSRC
Where it could be distributed
All platforms37 of 47 tracked agent platforms document MCP support CUR, so one MCP server could reach all of them. No pairing has been tested.
ContinueOpenCodeClaude CodeCodexGemini CLIZedOpenHandsClineWarpgooseQwen CodeRoo Code+25 more
Channels: Official MCP Registry listing, plugin marketplaces for Claude/Cursor/Codex, and the integration vendor's own app directory where one exists. HEU
Data coverage
- Indexed products
- 38DER
- With a full profile
- 8+DER
- Launches, last 90 days
- 11 vs 10 in the 90 beforeSRC
- Segment calculated
- Score calculated
Risks and counterarguments
- This is a hypothesis: demand is inferred from the parent category, not measured.
- A low count can mean low demand rather than an unmet need — a missing record is not proof of a market.
- Keyword classification under-counts products that do not name this capability.
- Classification is keyword-based: products that offer this without naming it are not counted, so the real gap may be smaller.
- 173 launches in the parent category in the last 90 days versus 121 in the previous 90.
- Technical feasibility was not assessed for this capability; a neutral 60 is used.
Assumptions
What has to be true for the score to mean anything.
- Interest in the parent category (combined GitHub stars) stands in for demand for this capability; the proxy is discounted by 40%.
- Keyword classification finds the products that offer this capability; products that do not name it are not counted.
- Monetisation and feasibility are not assessed beyond a fixed rule of thumb.
- A platform that documents MCP support can run any MCP server; no pairing has been tested.
How to verify this yourself
- No direct demand query exists for this capability; the demand figure comes from the parent category's GitHub stars.
- Check the supply on the Stateful Workflow Graphs page, and search the catalogue for products that offer it without naming it.
- Download the record with all evidence: /api/dataset/opportunities.json.
Page data last updated .