Skip to main content
usedby

Dust vs Guru: who uses which

Customers, public proof and the companies that use both.

On usedby, 42 companies use Dust and 25 use Guru. No company is listed with both yet. Dust leads among the Fintech & Payments companies on usedby that use either tool.Latest check Nov 20, 2026: 56 of 67 public lines checked. Counts include every proof level, job-post signals included. A company on both tools counts at any proof level, and a job post on one side is marked as such.

Who uses Dust, Guru, or both

Every company with a public proof for at least one of the two tools.

42

listed for Dust only

0

companies use both

25

listed for Guru only

On usedby, 42 companies are listed for Dust only, 25 are listed for Guru only and 0 use both, out of the 67 companies listed for at least one. An absent listing does not prove non-use.

42customers
36 confirmed 6 observed

Where it lands

Fintech & Payments5
Artificial Intelligence3
Cybersecurity3

Recently publicly listed customers

No new public customer listing since tracking started on October 2, 2026.

25customers
12 confirmed 13 observed

Where it lands

E-commerce & D2C3
Energy, Utilities & Cleantech2
Fintech & Payments2

Recently publicly listed customers

No new public customer listing since tracking started on October 3, 2026.

By industry

Which tool the companies on usedby use, by industry. Shares of the companies on usedby that use Dust, Guru or both: a share of the companies on usedby, not of the market.

IndustryListed for Dust onlyBothListed for Guru only
Fintech & Payments7 companies on usedby
71%0%29%
HealthTech & Digital Health5 companies on usedby
60%0%40%

Listed for Dust onlyBothListed for Guru only

More common with Dust

  • Fintech & Payments5 of the 7 Fintech & Payments companies on usedby that use either tool use Dust.
  • HealthTech & Digital Health3 of the 5 HealthTech & Digital Health companies on usedby that use either tool use Dust.

Source: every usedby line, from confirmed proofs to job-post signals (the weakest proof level).

Side by side

Facts from our data and from each vendor's public pages. Each line says where it comes from.

Vendor facts checked: Dust, 6 of 6; Guru, 2 of 6. Missing facts remain unverified, not absent features.

DustGuru
Customersusedby, latest check Nov 20, 2026Dust: 42 (36 confirmed, 6 observed)Guru: 25 (12 confirmed, 13 observed)
PricingDust: Free: $0 500 credits · Lifetime; Pro: $24 8,000 credits /seat/mo; Max: $120 40,000 credits /seat/mo; Enterprise: contact salesdust.tt, checked Oct 20, 2026Guru: Guru · Guru tailors pricing to organizational scale, knowledge complexity and AI maturity.getguru.com, checked Nov 16, 2026
SecurityDust: SOC 2 Type IIdust.tt, checked Oct 20, 2026Guru: SOC 2 Type IIgetguru.com, checked Nov 20, 2026
Your dataDust: Not used to train models by default.dust.tt, checked Oct 20, 2026No verified public evidence
Data residencyDust: EU, USdust.tt, checked Oct 20, 2026No verified public evidence
Free trialDust: Free trial or free plan available.dust.tt, checked Oct 20, 2026No verified public evidence
IntegrationsDust: Slack, Notion, Google Drive, GitHub, Salesforce, Zendesk, HubSpot, Jira, Linear, Confluence, Microsoft Teams, Snowflakedust.tt, checked Oct 20, 2026No verified public evidence
WebsiteDust: dust.ttGuru: getguru.com

What customers report

Results as the vendor or the customer published them, with the source and the date.

Dust

Dust AI agents can remove at least 50,000 hours of work per year

Qonto

Vendor case study, dust.tt, published Sep 19, 2024

Read the story

Today, a dozen people, from engineers to executives, access cost data weekly through Dust.

Dailymotion

Vendor case study, dust.tt, published Jun 25, 2026

Read the story

Guru

908 utilisateurs actifs d'IA/mois

Perk

Vendor case study, getguru.com, captured Nov 7, 2026

Read the story

The Vid Help Assistant achieved a 48% reduction in support tickets

Steno

Vendor case study, getguru.com, captured Nov 7, 2026

Read the story

Evidence for your decision: Dust

Source observations. Check the required plan and conditions before choosing.

Documented tasks

ContentsquareAutomate internal business workflows
Jenna's team built a suite of agents in Dust, each targeting a specific workflow where context-gathering was creating friction.

SourceVENDOR CASE STUDYCaptured:

Choice criteria

Free trial or free plan: YesRecheck required

Plan: Unknown

Free $0 500 credits · Lifetime

SourceVendor pageChecked:

Pricing: $0Recheck required

Plan: Free

Scope: 500 credits · Lifetime

Conditions: The passage includes multiple prices; verify the applicable price

Free $0 500 credits · Lifetime Pro $24 8,000 credits /seat/mo Max $120 40,000 credits /seat/mo

SourceVendor pageChecked:

Pricing: $24Recheck required

Plan: Pro

Scope: 8,000 credits /seat/mo

Conditions: The passage includes multiple prices; verify the applicable price

Free $0 500 credits · Lifetime Pro $24 8,000 credits /seat/mo Max $120 40,000 credits /seat/mo

SourceVendor pageChecked:

Pricing: $120Recheck required

Plan: Max

Scope: 40,000 credits /seat/mo

Conditions: The passage includes multiple prices; verify the applicable price

Free $0 500 credits · Lifetime Pro $24 8,000 credits /seat/mo Max $120 40,000 credits /seat/mo

SourceVendor pageChecked:

Integration: SlackRecheck required

Plan: Unknown

Product: Dust

Setup and limits: Workspace admin must enable Slack Bot and approve Slack authorization.; Documented integration availability; no execution tested.

Call your Dust agents from Slack channels, threads, and direct messages.

SourceDocumented · Not testedChecked:

Language: FrenchRecheck required

Plan: Unknown

Product: Dust

Setup and limits: Vendor documents French agent instructions; output quality and every workflow are not tested.

If you want an agent to **always respond in a specific language** regardless of the input language, you can specify that in the agent's instructions (e.g. "Always respond in French")

SourceDocumented · Not testedChecked:

API access: UnknownRecheck required

Plan: Unknown

Conditions: Production plan entitlement and account permissions are not established.; Interface documentation does not establish plan access

Product: Dust

Setup and limits: Documented only. No authenticated operation was executed.

API keys let your scripts and integrations call the [Dust API](/docs/developer-platform/overview/developer-platform).

SourceDocumented · Not testedChecked:

Data export: YAMLRecheck required

Plan: Unknown

Conditions: Only agent configurations are described; workspace-wide portability and plan entitlement are not established.; Product scope needs verification; Interface documentation does not establish plan access

Product: Dust agent configuration

Setup and limits: Documented only. No authenticated operation was executed.

Download the agent configuration identified by {sId} as a YAML file.

SourceDocumented · Not testedChecked:

Free trial or free plan: UnknownRecheck required

Plan: Unknown

Product: Dust

Setup and limits: Current page describes a free seat with lifetime credits, not a time-limited trial. Prior trial claims require recheck.

Free: 0€ , 500 credits lifetime. Best for occasional users or people trying Dust.

SourceDocumented · Not testedChecked:

Pricing: 0€Recheck required

Plan: Free

Conditions: Free is a seat type within Business; 500 lifetime credits. Currency reflects the captured page, not a regional price guarantee.

Product: Dust

Setup and limits: Documented only. No authenticated operation was executed.

Free: 0€ , 500 credits lifetime. Best for occasional users or people trying Dust.

SourceDocumented · Not testedChecked:

Integration: SalesforceSourced observation

Plan: Business

Conditions: Admin must configure the Salesforce External Client App, OAuth scopes and Dust Salesforce tool.

Product: Dust

Setup and limits: Personal credentials preserve each user's Salesforce permissions; workspace credentials share the setup admin permissions.; Documented only; not_tested. No vendor operation was executed.

Available on Business and Enterprise plans.

SourceDocumented · Not testedChecked:

Integration: SalesforceSourced observation

Plan: Enterprise

Conditions: Admin must configure the Salesforce External Client App, OAuth scopes and Dust Salesforce tool.

Product: Dust

Setup and limits: Personal credentials preserve each user's Salesforce permissions; workspace credentials share the setup admin permissions.; Documented only; not_tested. No vendor operation was executed.

Available on Business and Enterprise plans.

SourceDocumented · Not testedChecked:

Integration: HubSpotSourced observation

Plan: Unknown

Conditions: Requires admin OAuth setup and HubSpot tool made available to the agent.; Requires target object write scope, authorized operator and known existing record/property mapping.; Personal and Workspace credential modes have different permission scope; verify exact mode and current workspace action schema.; Product scope needs verification

Product: Dust HubSpot tools

Setup and limits: Catalog lists Update Contact, Company, Deal and Custom Object; no universal BANT mapping, plan entitlement, approval or successful write inferred.; Fathom transcript retrieval is a separate read-only tool; Salesforce CREATE evidence is excluded.; Documentary only; not_tested. No authenticated vendor operation executed.

Update Contact Update Company Update Deal Update Custom Object

SourceDocumented · Not testedChecked:

Integration: HubSpotSourced observation

Plan: Unknown

Conditions: Requires admin initial HubSpot OAuth and Personal authentication mode.; Each user must authenticate; optional object scopes must be granted. Personal connection cannot exceed Workspace-granted scopes.; Product scope needs verification

Product: Dust HubSpot tools

Setup and limits: Personal user permissions/audit scope only; Workspace mode uses admin account. Does not establish exact record/property write permission.; Documentary only; not_tested. No authenticated vendor operation executed.

Personal means users will need to authenticate the first time they use an agent that has Hubspot access and the actions will then be taken through their account (permissions, audit, etc)

SourceDocumented · Not testedChecked:

Usage limit: 42 webhook trigger runs per 24 hours by defaultRecheck required

Plan: Unknown

Scope: per 24 hours (default webhook trigger runs)

Conditions: Applies to Dust webhook triggers with default rate limiting; source must be configured by workspace admin.; Confirm actual workspace/trigger settings before capacity planning.; Product scope needs verification

Product: Dust webhook triggers

Setup and limits: Not 42 CRM writes per day; one run can use multiple actions and consume variable credits. No successful HubSpot field update inferred.; Documentary only; not_tested. No authenticated vendor operation executed.

Webhook triggers run at most 42 times per 24 hours by default. See Rate limiting.

SourceDocumented · Not testedChecked:

Capabilities for agents: Dust

Documentation and operational tests are separate. A test covers only the stated task and operation.

List agent configurations visible in an authorized Dust workspaceDocumentation: Needs rechecking · Operational test: Needs rechecking

Dust — Official publisher

Interface: REST. Plan: Unknown. Version: v1.

Endpoint: https://dust.tt/api/v1/w/{wId}/assistant/agent_configurations

Authentication: Dust API key as a Bearer token

Permissions: Read-only

Documented operations: list_agents (Read)

Manual setup: An authorized workspace admin opens Admin > Developers > API keys. Create a key with Read-only access and an optional consumption cap. Supply the approved workspace ID and Bearer key.

Limits: The all_unrestricted agent view requires an admin key. Monthly key caps can restrict programmatic use.

Documented costs: Unknown

Get the agent configurations for the workspace identified by {wId}.

Official sourceChecked:

Your DUST API key is a Bearer token.

Official sourceChecked:

Read-only

Official sourceChecked:

Admin > Developers

Official sourceChecked:

Test receipt: preflight_dust_c14b895b3b371b564ed9

Operational test: Needs rechecking · list_agents

Receipt recorded:

Expected result: After sandbox eligibility is verified: the documented read operation returns its documented response for synthetic fixtures. No operational assertion was executed in this preflight.

Test outcome: This receipt needs verification before use.

Still to verify: Workspace ID, account plan, numeric request quota and list-operation cost were not verified. Dust’s Read-only key role can create conversations; its label does not mean every accessible endpoint is non-mutating. No workspace agent list was requested.

Questions about Dust and Guru

Which has more customers on usedby, Dust or Guru?

Dust has more customers on usedby: 42 against 25 for Guru. Counts are companies tracked on usedby, not market shares.

Do companies use both Dust and Guru?

usedby has not found a company with a public line on both Dust and Guru yet.

Who uses Dust?

42 companies on usedby, each with the public page that shows it. See who uses Dust.

Who uses Guru?

25 companies on usedby, each with the public page that shows it. See who uses Guru.

How does usedby count customers?

A company counts when a public page shows it: a vendor's customer page, a case study, a press release or a job post, most saved with a dated capture. Every line is a customer, at one of four proof levels: confirmed, declared by the company itself, observed or signal (a job post, the weakest). A company counts as using both tools when it has a line on each, at any level; the list shows the strongest proofs first and marks job posts.