Comparison

Squidgy vs Dust: customer-facing vs internal.

Dust gives your employees a fleet of internal agents wired into company knowledge. Squidgy gives your customers an agent you can sell. Both are no-code — the difference is who the agent is for, and whether it makes you money.

Two builders smiling at a laptop screen together
The short answer

One sentence each.

Dust

“The operating system for AI agents” — deploy, orchestrate and govern fleets of internal agents that work alongside your team, wired into 100+ company data sources and tools.

Squidgy

A no-code agent builder for customer-facing products — agents that talk to your customers, run businesses, and earn revenue.

Side by side

Features that matter for builders.

FeatureDustSquidgy
Who the agent servesYour employees — support triage, sales research, ops reporting, eng Q&AYour customers — answering, qualifying, booking, selling
Target userEnterprise + scale-up teams, ops and ITNon-technical builders, vertical experts, agencies
Data connectorsDeep — 100+ company sources (Notion, Slack, Drive, GitHub, Salesforce, Zendesk)Knowledge base + RAG, 50+ tool integrations, MCP and custom HTTP tools
Deployment surfaceWhere your team already works — Slack, web, connected toolsCustomer-facing — website embed, marketplace, WhatsApp, Slack, Teams, installable app, MCP
MarketplaceNo — agents are for your own organisationYes — list your agent, get discovered, earn per use
Can you sell what you build?No — it's internal toolingYes — set your price; billing, payouts and taxes handled
Vertical pre-builtsGeneric, shaped to team workflowsPre-shaped per vertical
White-labelLimitedFirst-class (Fanatiq, YEAA, Handled)
Pricing modelPer seat: Free, Pro ~$30/seat/mo, Max ~$150/seat/mo (+ Enterprise), each with a monthly credit allowancePlatform fee on what your agent earns, plus metered usage — you pay as it makes money
Cost scales withHow many employees you give seats toHow much your agent is actually used and earns
Best forGiving your whole team leverage over internal knowledge and workflowsShipping an agent product customers pay to use
Ship as installable appYes — same agent skill file ships as chat widget, marketplace listing, or installable PWA on home screen
When to pick which

Pick Dust if…

  • Your use case is internal employees querying company knowledge
  • You're an enterprise with deep tooling (Notion, Slack, Drive) to connect
  • You need per-seat pricing and SSO at enterprise scale
  • The agent is internal IT/ops tooling, not a customer-facing product

Pick Squidgy if…

  • Your agent talks to customers, not employees
  • You want a marketplace storefront for what you build
  • You're a non-technical operator or vertical expert, not an enterprise IT team
  • Multi-channel deployment (embed, Slack, voice) is part of the product
  • You want platform-fee pricing aligned with revenue, not per-seat enterprise contracts

Honest take

Where Dust is stronger.

Dust is genuinely strong at what it does: 100+ deep company connectors, permissioned shared context, and a multiplayer model where agents sit inside the tools your team already uses rather than behind a chat box — backed by a $40M Series B in 2026. If your goal is giving employees leverage over internal knowledge and workflows, Dust is built for exactly that and Squidgy isn't competing on that ground.

Frequently asked

Squidgy vs Dust, in detail.

Is Squidgy a Dust alternative?+

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.

Customer-facing on Dust?+

Dust does support some customer-facing patterns but its DNA is internal-employee. Customer-facing flows aren't the primary design target.

Internal use on Squidgy?+

You can build internal agents on Squidgy, but the platform is optimised for customer-facing — marketplace, billing, multi-channel deployment are designed for external monetisation.

How does the pricing compare?+

Dust charges per seat — a free tier, Pro around $30/seat/month and Max around $150/seat/month (annual billing discounts it, Enterprise is custom), each including a monthly credit allowance that agent usage draws down. So your bill scales with how many employees you give seats to. Squidgy charges a platform fee on what your agent actually earns, plus metered usage, so cost scales with success rather than headcount. Squidgy's rates are indicative until launch. Check both directly — Dust's pricing changed in 2026 and may have moved again.

Isn't Dust also no-code?+

Yes — Dust says agents deploy in minutes with no coding, and that's fair. No-code isn't the real difference between us. The difference is who the agent is for: Dust's agents serve your employees and stay inside your organisation, Squidgy's face your customers and can be sold. Judge on that, not on which one is 'easier'.

Which has better company-knowledge depth?+

Dust, clearly. Its 100+ connectors across Notion, Slack, Drive, GitHub, Salesforce and Zendesk, with permissions and shared context, are built for surfacing company-wide knowledge to staff. Squidgy's knowledge base plus 50+ integrations and MCP is aimed at what a customer-facing agent needs to know, not at indexing your whole company.

Can we use both?+

Often the right answer. Dust for the internal fleet that makes your team faster, Squidgy for the agent your customers talk to and pay for. They serve different sides of the business and don't overlap much in practice.

Compare in your own time.
Then build.

Chat with Squidgy