+32 Commodity PressureMarketing and product framing lean heavily on connectors, agent templates, and multi-model choice—easy surface to replicate as 'AI features' bundled into other stacks.
"Multiplayer AI for human-agent collaboration" (homepage title)Heavy emphasis on connectors + model choice rather than proprietary model IPMarketing terms like 'AI Operators' and 'Self-improving AI' that read like productizable patterns
+30 Model DependencyPlatform explicitly stitches in third‑party models (OpenAI, Anthropic, Google, Mistral) and offers 20+ model options—no visible proprietary model to own the stack.
"Build agents with 20+ frontier and open-source models from OpenAI, Anthropic, Google, Mistral, and more."Allows choosing different models per task/workflowNo visible claim of a proprietary large model or unique core model
-18 Workflow OwnershipAgents are embedded into daily tools (Slack, QBR prep, RFPs, onboarding), with customer metrics claiming high adoption and repeated use—this is driving real workflow gravity.
Agents embedded directly in Slack channels for daily use (#ask-engineers style)Used for deep recurring workflows: QBR prep, RFP responses, onboarding, ticket triageCustomer claims: '95% internal adoption' and '~400 hours saved per week'
-12 Distribution EmbeddednessStrong channel signals: 70+ connectors, Slack and GitHub embedding, API exposure, platform docs, and thousands of orgs and hundreds of thousands of agents deployed.
"Connect Dust to 70+ connectors, including Slack, Notion, Google Drive, GitHub, Salesforce, and Zendesk."Expose agents as APIs (customers built agents exposed as APIs)"Trusted by teams at 3,000+ global organizations" and "300,000+ Agents deployed"
-12 Integration DepthReusable skills, sub-agent composition, single‑tenant deployments, and deep connectors to CRM/docs/Slack indicate real integration and entanglement, not just shallow plug‑ins.
Reusable skills and sub-agent composition describedDedicated single-tenant deployment and custom data retention policiesDeep integrations across critical business systems (CRM, docs, Slack, Zendesk)
-12 Enterprise TrustClear enterprise posture: SOC 2 Type II, data residency, single‑tenant options, SSO/SCIM—signals aimed squarely at procurement and security teams.
"SOC 2 Type II certified. Data residency in the US or EU. Dedicated single-tenant deployment."SSO and SCIM automated provisioningOperational controls and auditability that appeal to CISOs
-18 Switching CostHigh switching friction: agents living in Slack and as APIs, reusable templates, broad internal adoption and data residency make migration painful and costly.
Customers embed Dust into Slack and expose agents as APIs for cross-team orchestration"300,000+ Agents deployed" and customer adoption metrics (95%, 80%)Platform approach enabling internal builders and reusable domain agents
-6 Monetization MaturityStrong enterprise signals and customer case studies indicate commercial traction, though pricing is only partially visible—mature go‑to‑market but not fully transparent.
Multiple detailed customer case studies with measurable ROI (Clay, Assembled, Persona, Vanta)"Trusted by teams at 3,000+ global organizations"Pricing visibility: partial
-6 Category BaselineEnterprise platforms get baseline credit for embeddedness and trust.
enterprise platform
+4 Relative PlacementModest upward tweak: Dust's strong enterprise embedding cushions it, but clear model dependency and commodityable surface justify a small increase in vulnerability.
High commodity_pressure (32) and model_dependency_risk (30) indicate Dust is largely an orchestration layer around third‑party models with replicable connector + template patterns.No visible proprietary LLM or unique model IP—site explicitly advertises 20+ frontier and open models (OpenAI, Anthropic, Google, Mistral), increasing replaceability risk.Peers in the same archetype are largely rated 'At Risk' (deathScore ~40–59) for similar wrapper/orchestration dynamics; Dust is stronger on trust and embedment but shares core fragility.