Agentic Index
Dust vs Glean (2026)
Dust last verified ·Glean last verified
Dust starts from teams building their own agents in shared workspaces, while Glean starts from a company wide search index and graph that its assistant and agents draw on. That verdict is the Agentic Index coverage score, graded from each vendor's own published materials.
Both ground agents in company knowledge, respect each source's permissions, let customers choose among many models and log agent runs to a SIEM. Dust lets anyone write an agent in plain language and pick one of more than 20 models from OpenAI, Anthropic, Google, Mistral or DeepSeek. Its own connectors keep Slack, Notion, Drive and GitHub in sync, and more than 70 MCP connectors reach the rest. Agents run on schedules and events, ask before changing another system, and can remember each person's preferences. Pro costs 24€ a seat a month on yearly billing and Max 120€, with a free seat and US or EU residency on every plan. Glean indexes more than 275 connectors into an Enterprise Graph. Its agent builder, Agent Library and event triggers sit on top, and developers can publish agents as code from Claude Code, Codex or Cursor. Glean Protect checks an agent's write actions against the user's intent before they run. Glean routes across more than forty models and sells by quote. Choose Dust for self serve agent building at a public price. Choose Glean for governed agents on top of company wide search.
On the Agentic Index bring your own model ranking, Dust and Glean both clear the bar: each documents model flexibility and routing in full. 213 of the 556 platforms it grades clear it. See the bring your own model ranking
This comparison is published by Agentic Index, an independent agentic AI vendor research platform. Dust and Glean are each graded against the same 14 capability Agentic Index taxonomy, from the vendor's own public materials under the Agentic Index verification standard, alongside 1,165 researched vendors. No vendor pays for placement and no vendor has reviewed this page. How this evidence is graded
Choose Dust if
- Team members should build, deploy and run their own agents in plain language, starting from templates Sidekick fills in.
- You want a published per seat price, 24€ on Pro or 120€ on Max a month with yearly billing, and a free seat to try.
- Each agent should run on the model its builder picks, from OpenAI, Anthropic, Google, Mistral or DeepSeek.
- Agents should remember each person's preferences privately, and the person should be able to review or delete what was kept.
- Data must stay in the US or the EU on every plan, with single tenant deployment for Enterprise.
Choose Glean if
- Search across more than 275 connected systems, with source permissions on every read, is the foundation you want.
- An Agent Library should let teams find, certify and adopt agents others have built.
- Developers will write agents as code in Claude Code, Codex or Cursor and publish them to the same runtime.
- Write actions should be checked against the user's intent and authority before they execute.
- Your review asks for SOC 2 Type II, ISO 27001, ISO 42001, HIPAA and TX-RAMP Level 2.
| Feature | D Dust |
G Glean |
|---|---|---|
| Action & orchestration | ||
|
Integrations & Tool Calling Ability to connect agents to real systems through native integrations, OAuth-authenticated actions, custom tools, APIs, webhooks, or MCP-compatible tools. |
||
|
DustIntegrations & Tool Calling Dust offers more than 70 ready made MCP connectors that let agents use other systems' tools. MCP servers, native and remote, are on both plans, with up to 5 remote servers on Business and no limit on Enterprise. Alongside MCP, Dust maintains native connectors to more than 20 data sources, among them Slack, Notion, GitHub, Google Drive, Confluence, Zendesk and Salesforce, with up to 3 on Business and no limit on Enterprise. The native connectors cover the main systems and MCP covers the rest. Agents act as well as read, and credits are charged for tool use that includes actions in connected apps. Zapier, Make, n8n and Power Automate are available on both plans. Each integration belongs to a Space, so what an agent can reach through it follows the customer's own access model, not a blanket service account. Dust's inbound APIs, for outside systems calling Dust, are separate. The 70 and 20 counts are Dust's own, with no published directory listing them. Sourcedust.tt/home/product, /home/pricing feature table and credits FAQread 2026-09-12 |
||
|
GleanIntegrations & Tool Calling Agents act in outside systems as well as reading from them, through Connectors & Actions, and Glean enforces source-system permissions on every read and write. The 275+ app connectors each have their own page under glean.com/connectors, spanning documents, tickets, chat and code, and the same connectors feed Glean's index. The Indexing SDK lets teams add custom, permission-aware data alongside Glean's existing connectors, and custom actions are available through the APIs. Sourceglean.com/ai-agents connector index and glean.com/platform/apiread 2026-09-12 |
||
|
Workflow Orchestration Ability to sequence, branch, retry, route, and combine deterministic workflow nodes with autonomous agent steps. |
||
|
DustWorkflow Orchestration Multi agent orchestration with scheduled and event driven triggers is included on both plans, and agents run on those schedules and triggers without a person present. Pods are persistent shared workspaces where people and agents work together on a topic, project or initiative, with shared conversations, tasks, files and agents in one place. Frames are interactive dashboards and apps that agents produce. Pods and Frames run on a shared virtual computer and automations. Work is built from reusable, governable skills, agents and memory that the customer combines into workflows that compound with use. Deep research tasks that need complex, multi step orchestration and tool use consume more credits. A run can involve the people in a Pod, agents working in parallel, the connected systems each step reads and writes, and the model chosen for each agent. Dust does not say what happens when a step in a multi agent run fails or whether it is retried. Sourcedust.tt/home/pricing feature table and /home/productread 2026-09-12 |
||
|
GleanWorkflow Orchestration Glean's agentic engine lets agents reason through tasks, plan next steps and take action using enterprise context, in multi step and multi agent runs. Agent orchestration, which Glean describes as automating work across systems, routes tasks between agents and connects to external systems so automations run when and where they are needed, inside a governed runtime. An agent builder supports reasoning-based agents and complex workflows, and a deployment surface lets teams roll out, share and certify agents. Sourceglean.com/ai-agentsread 2026-09-12 |
||
|
Triggers & Channel Coverage How agents wake up and where they work: schedules, webhooks, message events, CRM events, inbox events, chat, email, voice, and collaboration tools. |
||
|
DustTriggers & Channel Coverage Scheduled and event driven triggers come with multi agent orchestration on both Business and Enterprise, and automations help power Pods and Frames. Dust's own connectors sync in real time, so a change in Notion, Slack or GitHub reaches Dust without waiting for a poll, and an agent can be triggered by it. Agents are reached in the Dust workspace, including Pods where people and agents work in parallel, through a Chrome extension that brings agents into the tools people use, and through Slack, Notion, GitHub and Drive. Zapier, Make, n8n and Power Automate are included on both plans and can start a Dust agent from anything they can see. Dust does not list which event types each connector supports or whether customers can combine conditions, and does not explain its automations further. Sourcedust.tt/home/pricing feature table, /home/product and docs.dust.tt welcome pageread 2026-09-12 |
||
|
GleanTriggers & Channel Coverage Key events start agent runs, and agent orchestration exists to trigger agents from key events, route tasks between agents and connect to external systems so automations run when and where they are needed. People reach Glean from its own web app, from 275+ connected applications, and through Glean MCP inside Claude Code, Codex, Gemini, Cursor and Copilot. Proactive AI, which anticipates next steps like meeting prep or first drafts before anyone asks, is marked coming soon, while the event triggers carry no such marker. Sourceglean.com/ai-agents, against glean.com/platform/enterprise-contextread 2026-09-12 |
||
| Knowledge & context | ||
|
Knowledge Grounding & RAG Ability to ground agent behavior in company data through document ingestion, retrieval, external knowledge APIs, semantic search, or RAG layers. |
||
|
DustKnowledge Grounding & RAG Agents answer through retrieval augmented generation over a corpus Dust keeps current. Dust maintains its own connectors instead of relying on a generic integration provider, and real time sync keeps agents working from current information. Search, query and extraction across all company data are included on the plans. Semantic search covers unstructured content, and Table Query combines semantic search with SQL for structured data, so one run can answer a numeric question from a warehouse and a policy question from a wiki. Image analysis is also supported. What an agent can retrieve is limited by the asking user's permissions, because data sits in Spaces with configurable access controls and each integration belongs to a Space. Named sources include Slack, Notion, Google Drive, Confluence and GitHub, with more than 20 native connectors in all and anything else over MCP. Dust does not describe chunking, embedding, citations back to a source passage or how fresh a retrieved answer is. Sourcedocs.dust.tt welcome page with dust.tt/home/product and /home/pricingread 2026-09-12 |
||
|
GleanKnowledge Grounding & RAG A persistent index and graph sit over the customer's corpus. Glean has 275+ connectors across apps, documents, tickets, chat and code and 1000+ signals in the Enterprise Graph mapping people, content and relationships, on the principle of indexing data once and using it everywhere. The Enterprise Graph captures not just content but the relationships between people, data and activity across the organization, and it persists between runs and stays queryable. Retrieval respects permissions, enforcing source system permissions on every read, so the graph carries access state as well as content. Sourceglean.com/platform/enterprise-contextread 2026-09-12 |
||
|
Memory & State Persistence Ability to persist context across a run, conversation, workflow, user, team, or longer-term memory layer. |
||
|
DustMemory & State Persistence Agents can keep a memory of each person they work with. Once the Memory tool is added in the builder, the agent decides during a conversation what is worth keeping, and a user can also ask it to remember something, such as a preference for morning meetings. Memories are private to each user and kept separately for each agent, they last until the user deletes them, and the user can browse them in the agent's Memory tab and delete any single item. Within a piece of work, Pods hold the shared conversations, tasks and files for a project, and long conversations are compacted so the agent keeps the thread. Sourcedocs.dust.tt Agent Memory, Tools and Context Compaction pagesread 2026-10-21 |
||
|
GleanMemory & State Persistence Enterprise Memory, which learns continuously, is one of four Enterprise Context components, and what Glean publishes under that heading is the Enterprise Graph, a knowledge structure. A per user layer sits beside it. Personal Graph learns each person's goals, commitments, priorities, writing style and ways of working from their edits, replies, messages and other work signals, and Glean uses it to tailor answers and write in that person's voice. Glean does not describe a lifetime, expiry or purge path for either, or a way for a person or an admin to read or edit what was learned. Skill reflection, launched in October 2026, updates a skill from how it is used only after a person confirms the change. Proactive AI, which builds a live view of teams and projects and anticipates next steps, is marked coming soon. Sourceglean.com/platform/enterprise-context, glean.com/enterprise-context/personal-graph and glean.com/blog/skill-reflection-2026read 2026-10-24 |
||
| Control & trust | ||
|
Human Oversight & Guardrails Approval steps, consent checkpoints, escalation rules, structured guardrails, policy constraints, and pause/resume controls. |
||
|
DustHuman Oversight & Guardrails Agents stop and wait for a person before an action that needs approval. Every tool on an MCP server carries a stake level, set in its Tools and Stakes settings, and a tool that asks pauses the agent until the user approves or declines that action, with medium stake approvals remembered per agent. Dust's own connectors come with the gate built in for changes, so publishing or deleting in Contentful, writing to Grafana, changing an Airbyte sync or running a paid Bright Data scraper all wait for a yes. The request reaches people where they are, through a sound alert when an agent is waiting, an email with allow and decline links for agents started by email, and an API call that approves or rejects an action. A credit circuit breaker also pauses an agent at 600 credits on one message and asks whether to continue. Spaces and Groups decide beforehand which data, tools and systems an agent can reach. Sourcedocs.dust.tt changelog (tool stakes and approval entries, January to October 2026) and API reference, validate an actionread 2026-10-21 |
||
|
GleanHuman Oversight & Guardrails Glean Protect checks agent actions before they run. Action Alignment checks agent actions against the user's intent and authority before execution, and write actions are checked before they execute to keep agents within their intended scope, so Glean, not the downstream system, stops a write that fails the check. Topic Restrictions check requests against acceptable use and industry-specific policies before the model responds. Agent governance policies and different policies for select agents or users are marked coming soon, and the control on agentic browser use is in beta, while the checks above carry no such marker. Glean does not describe an approval queue that a person reviews item by item. Sourceglean.com/platform/securityread 2026-09-12 |
||
|
Security, Identity & Governance RBAC, SSO, auditability, encryption, least-privilege tool access, compliance posture, and data handling policy. |
||
|
DustSecurity, Identity & Governance Business and Enterprise both carry SOC 2 Type II, GDPR compliance is stated throughout, and HIPAA can be enabled. A Trust Center sits at trust.dust.com, with a vulnerability disclosure page at dust.tt/home/vulnerability. Business includes SSO with Okta, Entra ID and JumpCloud for 5 or more seats, on demand. Enterprise adds SCIM provisioning, audit logs and advanced security controls, plus custom data retention and a custom MSA and DPA, so Business customers have SSO and Spaces but no provisioning or activity trail. On both plans, data is organized into Spaces with configurable access controls, so admins decide which teams can reach which data sources. Integrations with Notion, Slack and Google Drive belong to Spaces, and Groups set permissions. Data is encrypted with AES-256 at rest and TLS 1.2+ in transit. Prompts, documents and outputs are never used to train models, though third party model providers may keep data for up to 30 days for safety and abuse monitoring before deleting it. Sourcedust.tt/home/pricing feature table, /blog/what-is-data-sovereignty, /blog/secure-enterprise-software-ai-powered-teams and docs.dust.tt admin guideread 2026-09-12 |
||
|
GleanSecurity, Identity & Governance Glean holds SOC 2 Type II, ISO 27001, ISO 42001, HIPAA, TX-RAMP Level 2 and GDPR, with a trust center at trust.glean.com. Identity & Access verifies who is making a request through the customer's SSO provider before AI runs, covering both user and agent identity, and Data Permissions enforces source-system permissions on every read and write, so an agent does not automatically access everything the user can. An always on audit trail records what happened. Four items are marked coming soon or beta, agent governance policies, per agent and per user policies, Enterprise Graph enriched threat detection, and security scans of memory. Sourceglean.com/platform/securityread 2026-09-12 |
||
|
Observability & Auditability Traces, logs, execution histories, metrics, audit events, and debugging detail for production agent behavior. |
||
|
DustObservability & Auditability On Enterprise, audit logs record what agents do as well as what people do. Each agent run, each tool an agent executes and each trigger that starts a run is its own event, and a tool event names the tool, the MCP server and the data sources it reached, and says whether the AI drove the action or a person started it. The log is time ordered and tamper evident, searchable and exportable as CSV, and it streams to Datadog, Splunk, Amazon S3, Google Cloud Storage or any HTTPS endpoint. On every plan, analytics break credit use down by agent, member, model, tool and Pod, and a per call export lists each model call and tool call behind the bill. Sourcedocs.dust.tt Audit Logs, Audit Logs events reference, Analytics and the consumption export APIread 2026-10-21 |
||
|
GleanObservability & Auditability Every control point is logged to an end-to-end audit trail as it happens, with events available to stream into a SIEM. Six control points are logged, identity and access, data permissions, sensitive content, topic restrictions, runtime threat protection and action alignment, so the trail shows who asked, under what identity, what was permitted, what was screened and what the agent was allowed to do. It is Glean's own record of what its agents did, separate from the logs the customer's Slack, Jira or Salesforce already keep. Agent observability, a separate surface, reports adoption, error rates, upvotes, downvotes and ROI as operational metrics. Sourceglean.com/platform/security and glean.com/ai-agentsread 2026-09-12 |
||
|
Deployment & Data Residency Deployment modes and options, including SaaS, dedicated cloud, VPC, on-prem, hybrid, local runtime, and self-hosting. |
||
|
DustDeployment & Data Residency Customers on Business and Enterprise choose US or EU data residency, so a self serve customer at €24 a seat gets the choice. Enterprise adds single tenant deployment. The platform's code is public at github.com/dust-tt/dust, linked from the site footer, and Dust mentions self hosting without documenting how to do it. On EU hosting, data is stored on servers in the European Union, and model inference is routed to EU regions where available, which means not for every model, with Mistral named as the European provider. Dust separates sovereignty, residency and localization, and notes that a European data center run by a US based company can still be compelled to hand data to American authorities. Dust is based in Paris, so that CLOUD Act argument works in its favor, and it says so. Ardabelle, a named customer, chose Dust on EU hosting and GDPR grounds for private equity deal documents. The specific EU region is not named. Sourcedust.tt/blog/what-is-data-sovereignty and /home/pricing feature tableread 2026-09-12 |
||
|
GleanDeployment & Data Residency Customers can host Glean in their own cloud tenant, and Glean says SafetyCulture chose it in part for its security-first approach to enterprise data and the ability to host Glean within its own cloud tenant. TX-RAMP Level 2 points to a deployment posture US state governments can procure, and a trust center sits at trust.glean.com. Glean publishes no deployment guide for the cloud tenant option, and no single tenant, customer managed, on premises or air gapped deployment. Sourceglean.com/platform/securityread 2026-09-12 |
||
| Solution readiness | ||
|
Prebuilt Agents, Templates & Packs Ready-made workflows, packaged employees, templates, blueprints, industry solutions, and role-specific agents that reduce time-to-value. |
||
|
DustPrebuilt Agents, Templates & Packs Ready agents and a template library come with every workspace. The default agents run as they are and each does its own job: @dust answers from all the company data a user can reach, @deep-dive spends ten to thirty minutes researching across the knowledge base, data warehouses and the web, and @analyst answers questions about how the workspace uses Dust. Admins can switch each one on or off. Templates cover common use cases, and choosing one opens Sidekick with the template loaded, which drafts the instructions and suggests tools and data for the team to adjust before publishing. The workspace gallery then fills with the agents a company's own builders make. Sourcedocs.dust.tt Templates and default agents pages (@dust, @deep-dive, @analyst)read 2026-10-21 |
||
|
GleanPrebuilt Agents, Templates & Packs The Agent Library lets teams discover trusted, reusable agents, so every team can build, deploy and discover new agents on one platform, and a deployment surface lets them roll out, share and certify agents. The library holds independent agents built for different jobs that customers can adopt from the catalog. Glean does not publish a count of prebuilt agents. Sourceglean.com/ai-agents and its Agent Library sectionread 2026-09-12 |
||
| Platform extensibility | ||
|
Model Flexibility & Routing Ability to work across multiple foundation models, route tasks to different models, or let buyers bring their own providers and keys. |
||
|
DustModel Flexibility & Routing Every plan includes more than 20 frontier models from OpenAI, Anthropic, Google, Mistral and DeepSeek, across the GPT, Claude, Gemini, Mistral and DeepSeek families, open source models among them. The customer chooses the model for each agent. No model is locked behind a higher plan, though more capable models may use more credits per message. Teams can pick the right model for each workflow and switch as their needs change. Mistral AI, a French founded company, is the European option, and for work that must stay under European jurisdiction Dust offers EU hosted infrastructure with model inference in EU regions. Dust presents model choice as a way to avoid vendor lock in and geopolitical risk by controlling where data is processed and which providers are used, and calls being model agnostic a core feature. Usage analytics by agent and by model show what each model costs per workflow. Dust's MCP connectors and its Conversation and Data Source APIs are separate from model routing. Sourcedust.tt/home/pricing model list and FAQ, /home/product, and /blog/what-is-data-sovereigntyread 2026-09-12 |
||
|
GleanModel Flexibility & Routing Glean Intelligence optimizes AI for price-performance, matching each task to the right model across 40+ open and frontier models, with Auto routing. Customers and admins get a Model Hub for access to the latest models, flexible model choice as part of the Open Platform, an AI Gateway that governs every AI interaction and which models may be used, and Usage Controls for AI usage and spend. Multi cloud support and the Bedrock, Vertex and Azure OpenAI hosting relationships are infrastructure, not separate model providers. Glean does not show how a model is selected for each step. Sourceglean.com/platformread 2026-09-12 |
||
|
APIs, SDKs & MCP Extensibility Composability layer: stable APIs, SDKs, MCP tool consumption/serving, custom tools, and integration into internal systems. |
||
|
DustAPIs, SDKs & MCP Extensibility The platform has its own API. Business includes a Conversation API for driving conversations with agents from outside, and Enterprise adds a Data Source API that writes into the knowledge layer. Platform documentation at docs.dust.tt, linked from the site footer, offers an llms.txt index of every page in Markdown, with endpoints in OpenAPI. The platform's code is public at github.com/dust-tt/dust, and a developer platform at dust.tt/home/solutions/dust-platform covers Dust Apps, described as an extensible, API first platform for custom integration and LLM orchestration. Programmatic use is metered at $0.01 per credit on Business and custom on Enterprise. Zapier, Make, n8n and Power Automate are available on both plans, and a Chrome extension brings agents into other tools. The MCP connectors run the other way, letting Dust call other systems' tools. No endpoint reference or SDK page is cited, and the OpenAPI specification is mentioned but not shown. Sourcedust.tt/home/pricing developer tools table, docs.dust.tt welcome page and site footerread 2026-09-12 |
||
|
GleanAPIs, SDKs & MCP Extensibility Outside callers reach Glean through its Search API, Chat API and Agents API, an Indexing SDK that lets teams add custom, permission-aware data alongside Glean's existing connectors, and a Web SDK to embed Glean UI and context-aware chat or agent experiences. The Agents API follows the LangChain Agent Protocol, with client libraries in TypeScript, Go, Java and Python, and an ungated developer portal sits at developers.glean.com. Glean MCP feeds governed enterprise context into Claude Code, Codex, Gemini, Cursor and Copilot, letting those tools drive Glean, while the 275+ connectors run the other way, letting Glean drive other systems. Sourceglean.com/platform/api and glean.com/blog/go-agents-launchread 2026-09-12 |
||
|
Testing, Debugging & Optimization Testing, debugging, scoring, retries, fallbacks, quality gates, and optimization loops for improving agent workflows before and after deployment. |
||
|
DustTesting, Debugging & Optimization A builder can try a change before it goes live. A preview area beside the agent builder runs the draft agent on real questions, and the docs advise testing changes there until the answers are consistent. Teams that manage agents as code can keep agent and skill definitions in YAML in a GitHub repository with the official GitHub Action, review edits in pull requests and promote them from a development workspace through staging to production, and changes Sidekick proposes from a conversation arrive as cards to accept or decline. Thumbs up and down on each answer are collected and readable through the API. None of this scores a change, since there are no test cases, pass rates, evaluators or comparisons between two versions of an agent, so judging a change still rests on someone reading the answers. Sourcedocs.dust.tt Troubleshooting your agent, the dust-github-action changelog entry and the feedback APIread 2026-10-21 |
||
|
GleanTesting, Debugging & Optimization Builders can test agents before they publish them, and Glean does not describe how a test is scored. The agent builder versions every change automatically, keeps drafts and offers rollback, and lets builders test outputs and adjust instructions. Headless agent building, generally available since October 2026, lets developers define an agent in files from Claude Code, Codex or Cursor, run it with representative inputs, "run evaluations" and refine it before publishing, with changes reviewed and rolled back through Git. Debug and trace views became generally available in May 2026. Glean does not describe what an evaluation measures, a pass criterion, scored test cases, a quality gate or a controlled experiment. Agent observability reports adoption, error rates, upvotes, downvotes and ROI as live operational metrics. Sourceglean.com/ai-agents/agent-builder, glean.com/blog/glean-headless-agent-builder and glean.com/press/glean-introduces-the-enterprise-agent-development-lifecycle-codifying-how-enterprises-build-govern-and-measure-ai-agentsread 2026-10-24 |
||
| Specialist automation | ||
|
Browser & Computer Use Browser, desktop, or remote/local computer control for workflows that cannot be handled through stable APIs alone. |
||
|
DustBrowser & Computer Use Pods and Frames run on a shared virtual computer and automations, a shared environment where agents run code and produce artifacts, not one where an agent operates a graphical interface. Credits are charged for tools such as search, data retrieval, code execution and actions in connected apps, and interface control is not among them. The Chrome extension lets a person reach Dust agents while browsing, and no agent drives the browser. Every path in and out of Dust is a maintained connector, an MCP server or an API, so a third party redesigning its interface does not affect it, and Dust maintains typed connectors instead of scraping. There is no hosted or local browser session, desktop or remote computer control, RPA, recorder or extension that acts on a page for the agent. Dust does not explain what its shared virtual computer can and cannot do. Sourcedust.tt/home/product, /home/pricing credits FAQ and /home/chrome-extensionread 2026-09-12 |
||
|
GleanBrowser & Computer Use Agents reach other systems through 275+ API connectors and custom actions, and Glean offers no hosted browser, desktop session or remote or local computer control. Glean Protect lists keeping agentic browser use in check as a guardrail in beta. Nothing shows Glean's own agent driving a browser. Sourceglean.com/platform/security and glean.com/platformread 2026-09-12 |
||
Pricing snapshot
Sourced from the Index pricing dataset · open each vendor's profile for full detail.
| Pricing | D Dust |
G Glean |
|---|---|---|
|
Entry price Lowest public entry point |
Free seat at 0€ with 500 lifetime credits; paid entry is Pro at 24€ per seat per month billed yearly (30€ monthly), and Max at 120€ yearly (150€ monthly). All excluding VAT. Enterprise on application. Figures are euros, not dollars. | Contact for pricing |
|
Pricing confidence How public the numbers are |
Public, exact | Contact only |
|
Billing Primary billing axis |
Per seat per month with a monthly credit allocation attached to each seat, across three seat types inside one self serve Business plan, plus a sales led Enterprise plan. Seats are priced in euros excluding VAT; programmatic API usage is priced in US dollars at $0.01 per credit. Admins assign a seat type per user and can mix and reassign them at any time. | — |
|
Variable cost Workload / overage exposure |
Medium variable cost | Medium variable cost |
|
Free tier / trial Try before you buy |
Free tierTrial
|
No free tier
|
|
Buying motion Self-serve vs sales call |
Mixed | — |
|
Pricing verified When this pricing was last checked |
Product updates
Newest first, each linked to its source.
Dust
-
· Workflow orchestration
Dust Default, the platform's default agent, can now create, update and remove any trigger type Dust supports, including scheduled runs and event based automations.
Source -
· Security / enterprise
Each Pod in Dust now has its own settings for which network domains its agent sandboxes may reach and which variables and secrets they hold.
Source -
· Human approval / guardrails
Dust added controls for credit spend checkpoints on individual agents in Agent Builder and across the workspace in Usage settings.
Source
Glean
-
· MCP / tool calling / API
Release 565 adds 57 remote server templates to Glean's MCP server library, among them Google Ads, 6sense, BambooHR, Kong Konnect, LinkedIn Hiring Pro, NetSuite QuickStart and Pipefy.
Source -
· Agent capability
Glean release 563 adds Skill reflection, which picks out the feedback users give in chat while running a Skill and proposes it as an edit to the Skill's instructions.
Source -
· Human approval / guardrails
Glean's MCP servers now ask the user to confirm before any write action runs, on by default, because not every MCP host has its own approval step.
Source
Glean publishes no price, and some of its governance policy controls are announced but not shipped, so ask for a quote and a shipping date. Dust keeps audit logs, SCIM and custom retention for Enterprise, and its credits do not roll over. Neither vendor offers a harness that scores agents before release beyond previews and feedback, so plan your own tests.
More comparisons with Dust or Glean
Other matchups in enterprise operations agents
Not the pairing you were after? These compare a different set of enterprise operations agents on the same 14 capabilities.