Dust is internal knowledge agents for employees. Squidgy is customer-facing agents for businesses. Different audiences, different jobs.
Dust
A workplace-AI platform — internal knowledge agents for employees, with deep enterprise connectors for company-wide knowledge.
Squidgy
A no-code agent builder for customer-facing products — agents that talk to customers, run businesses, and earn revenue.
| Feature | Dust | Squidgy |
|---|---|---|
| Primary use | Internal employee knowledge agents | Customer-facing agent products |
| Target user | Enterprise IT / ops teams | Non-technical builders, vertical experts, agencies |
| Knowledge connectors | Deep — enterprise tools (Notion, Slack, Drive, etc.) | Standard knowledge base + RAG; less enterprise-connector breadth |
| Deployment surface | Internal Slack, web, integrations | Web, embed, Slack, Teams, Roam, voice — customer-facing |
| Marketplace | No — internal use only | Yes — list and earn per use |
| Vertical pre-builts | Generic | Pre-shaped per vertical |
| White-label | Limited | First-class (Fanatiq, YEAA, Handled) |
| Pricing | Per-seat enterprise subscription | Platform fee on revenue earned |
| Best for | Enterprise teams with internal knowledge to surface to employees | Builders shipping customer-facing agent products |
Honest take
Dust's enterprise polish, deep internal connectors (Notion, Slack, Drive, GitHub, etc.), and per-seat scaling make it the right pick for enterprise IT teams surfacing internal knowledge to employees. Different problem; different right answer.
For customer-facing agents — yes. For internal-team knowledge agents (helping employees find answers across company tools), Dust is purpose-built for that and you should use it directly.
Dust does support some customer-facing patterns but its DNA is internal-employee. Customer-facing flows aren't the primary design target.
You can build internal agents on Squidgy, but the platform is optimised for customer-facing — marketplace, billing, multi-channel deployment are designed for external monetization.
Dust uses per-seat enterprise subscriptions. Squidgy uses platform fee on revenue earned. For internal use Dust scales by team size; for external monetization Squidgy scales by what your agent earns.
Dust's enterprise connector breadth (Notion, Slack, Drive, GitHub, internal tools) is deeper for internal knowledge surfacing. Squidgy's RAG knowledge base is standard but less optimised for enterprise data warehousing.
Other comparisons
By vertical
For coaches
An accountability partner between sessions. An intake assistant that books only fit clients. A program companion that answers in your voice. Built without code, ready in days.
For consultants
Your audits, diagnostics, frameworks — turned into AI agents that scale beyond your billable hours. Built without code. Listed in the Squidgy marketplace. Earn while you sleep.
For creators
An AI agent your audience already trusts you to build. Sell access to a tool only you could ship — built without code, with billing handled.
For influencers
Your followers don't just want your content — they want your taste applied to their problem. Bottle that as an AI agent and sell access. No code, no agency cut, no platform shaving margins.
For fitness coaches & gyms
Accountability agents that check in between sessions. Programming assistants that draft week 3. Member onboarding that runs while you coach. All built without code.
For real estate
Qualify leads while you show. Schedule tours while you negotiate. Follow up with past clients without lifting a finger. YEAA.co is the Squidgy deployment built specifically for real estate.