Agentic Index
Dust vs Sana (2026)
Dust last verified ·Sana last verified
Dust and Sana both ground enterprise knowledge agents in company data, and they differ on who builds the agents and how each sells. That verdict is the Agentic Index coverage score, graded from each vendor's own published materials.
Dust lets each agent pick from more than twenty models and ground itself in company knowledge, with Pro seats at €30 a month or €24 on a yearly plan, while Sana pairs an assistant with no code agents across more than a hundred connected apps, offers a free account and quotes its paid plans on request. Choose Dust for a published per seat price and US or EU data residency on every plan. Choose Sana for Workday ecosystem alignment.
On the Agentic Index bring your own model ranking, Dust and Sana 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 Sana 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,140 researched vendors. No vendor pays for placement and no vendor has reviewed this page. How this evidence is graded
Choose Dust if
- An independent vendor with its own roadmap is your preference.
- Per agent model choice across 20+ providers matters to your builders.
- The builder workspace culture (AI Operators) matches your org.
Choose Sana if
- Your enterprise runs Workday and native alignment will compound.
- Permission aware retrieval with citations over 100+ apps covers your needs.
- A polished knowledge assistant matters more than builder flexibility.
| Feature | D Dust |
S Sana |
|---|---|---|
| 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 |
||
|
SanaIntegrations & Tool Calling Sana writes into outside systems and connects to a large, named catalog. Act, one of its five headline capabilities, means "take instant actions across your tools". Its team pages promise "AI that helps you prep for calls, answers your RFPs, and updates your CRM", and "AI that assigns tickets, answers product questions, and analyzes all your support calls". Updating a CRM record and assigning a ticket are authenticated writes into systems Sana does not own. "Sana connects with 100+ applications and unifies your company's data securely", among them Google Meet, Google Drive, Google Calendar, Dropbox, Confluence, Jira, ServiceNow, Salesforce, Microsoft Teams, SharePoint, Workday and Slack, with a full list on its own integrations page. Meeting capture spans Zoom, Teams and Google Meet on free and paid tiers. The custom route is open, since "Enterprise customers can also build custom integrations to Sana AI", with an "MCP client for building your own integrations" at the Enterprise tier, so the customer is not confined to the shipped connector list. Sourcesanalabs.com/products/sana integrations section and sanalabs.com/agent-pricingread 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 |
||
|
SanaWorkflow Orchestration Automate, the first of the platform's five verbs (Automate, Create, Analyze, Act, Find), means "run complex, multi-step processes", and Sana pitches "AI agents that collaborate, automate, and think alongside your teams". An agent finds across connected apps, analyzes, generates content in any format, turns data into live dashboards, then takes action in outside tools. The examples are whole workflows, not single calls, such as a valuation memo that took a CFO almost a week finished in three or four hours, RFP responses, deal analysis and portfolio reviews, and prospecting through due diligence to investor communications. Assistants are built without code and scoped separately, so a firm runs several agents built for their purpose, and unlimited assistants on the free tier show the runtime hosts many instances. Sana names no runtime or BPMN. Sourcesanalabs.com/products/sanaread 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 |
||
|
SanaTriggers & Channel Coverage People reach the agent across many channels, but work starts without a person asking in only one way. Channel coverage is broad, with the web workspace, an iOS app Sana calls "a polymath in your pocket", Slack (a customer quote describes asking Sana in Slack for someone's actions from the last meeting), Microsoft Teams, and meeting surfaces across Zoom, Teams and Google Meet on every tier. Email is reachable through the Gmail and Outlook integrations. Triggers are thinner. Meetings arriving on a connected calendar do make the agent act unasked, since "Sana AI transcribes, summarizes, and stores your meetings so you're always prepared", and it joins sessions on its own. Integration syncs pull new documents in continuously, but they feed the index and start no run. There are no scheduled runs, cron, webhook, inbound work queue or monitoring mode that starts an agent. Sourcesanalabs.com/products/sana and sanalabs.com/agent-pricingread 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 |
||
|
SanaKnowledge Grounding & RAG Enterprise search over the customer's own content is a named product, a persistent, semantic index that respects permissions and cites its sources. Enterprise Search has its own capability page, and the Find capability covers "all the latest company docs and data". Content from 100+ connected applications is "indexed and stored in a cloud instance", with document quotas per tier (10,000 per integration on Team and unlimited on Enterprise), a retrieval index with capacity limits, not context assembled per run. Search is semantic, since "Sana Agents uses semantic search to understand concepts, not just keywords, making it easier to find what you need", even when a question is loosely phrased. It is multimodal, covering documents, structured files and video with more types "added continuously", current by design ("the platform always prioritizes the most recent and relevant information in your knowledge archive"), and it checks permissions at retrieval time, not at display time. Answers return citations that deep link back to the original document, meeting or record, and the corpus grows without manual capture because meetings are transcribed and stored automatically. Web search sits alongside it. The Search web toggle extends reach to the public web, and with it off the agent returns only internal content, so the internal index stands on its own. Sourcesanalabs.com/products/sana, sanalabs.com/agent-pricing, support.sana.ai/en/articles/148586-sana-agents-101 and support.sana.ai/en/articles/157324read 2026-10-24 |
||
|
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 |
||
|
SanaMemory & State Persistence Between runs, what persists is the corpus and a user activity log, not agent memory. Stored meetings, conversation history and indexed knowledge are the application's data model, and stored transcripts and indexed documents are retrieval content. History "keeps a log of your activities", such as searches, files accessed and content changes, so a user can revisit past work and track progress. That is a record of what the person did, not state the agent carries between runs. There is no memory scope for each user distinct from the workspace, no published lifetime, no expiry or purge path for memory as opposed to the account, and no surface to read or write it. The feedback function that helps "Sana Agents learn and improve" describes learning absorbed into the product, not a memory a customer can govern, and Sana says separately that it does "not train any language models on your data". Sourcesanalabs.com/products/sana and support.sana.ai/en/articles/148586-sana-agents-101read 2026-09-12 |
||
| 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 |
||
|
SanaHuman Oversight & Guardrails Administrators and users bound each assistant's scope before it runs, and nothing checks the agent during a run. Search web is a toggle. With it off, "searches will return only internal company content", and administrators can enable or disable web browsing for any assistant they create. Select sources lets a user "choose exactly where Sana Agents looks for answers", narrowing the corpus per question. Retrieval is bounded by permissions by construction, since "Sana Agents only shares documents or meeting notes that have been shared with you or placed in public folders". Every answer can be checked against deep linked citations. There is no approval queue, preview before commit, confirmation step, policy engine or calibration of risk for each action. That matters because the Act capability promises to "take instant actions across your tools", updating CRMs and assigning tickets, and nothing sits between the agent's decision and that write. Oversight is set at configuration time and verified after the fact, never during. Sourcesupport.sana.ai/en/articles/148586-sana-agents-101 and sanalabs.com/agent-pricingread 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 |
||
|
SanaSecurity, Identity & Governance Customers get a clear access surface of their own alongside the certifications. The security strip lists SAML single sign on, user provisioning, custom user roles, flexible groups, advanced permissions and domain verification. The enterprise entitlement is "domain verification, SAML-based SSO, and SCIM", and SSO setup guides cover Okta, Microsoft Entra, OneLogin, JumpCloud, Google Workspace, Auth0 and Salesforce, alongside a SCIM configuration guide. Identity federation, automated provisioning and a named role and group model are all aimed at the customer's own organization. The same strip shows SOC 2 Type 2 and ISO 27001. The pricing FAQ calls Sana Agents "SOC2 and ISO 27001 certified", while the AI agents page lists SOC 2 Type 1 compliance, so the SOC 2 report type differs between Sana's own pages. ISO 27001 is stated as certified on each. Retrieval also mirrors source permissions, so it inherits the entitlements of source systems instead of flattening them. Sourcesanalabs.com/products/sana security section, sanalabs.com/agent-pricing, sanalabs.com/products/sana/ai-agents and help.sana.ai/en/collections/271878-security-and-integrationsread 2026-10-24 |
||
|
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 |
||
|
SanaObservability & Auditability Visibility surfaces exist, but none is a record of agent behavior. Audit logging appears as a badge in the security strip, with no text about scope, retention, export or what is captured. The Enterprise tier includes an "analytics dashboard to measure impact". History logs a user's own activities, such as searches, files accessed and content changes. Every answer carries deep linked citations back to the source document, meeting or record. None of these reconstructs why the agent acted. History is a user's own activity log, not an administrator's record of agent behavior, the analytics dashboard measures adoption and impact, citations reconstruct the answer, not the agent, and the audit logging badge comes with no detail. Nothing lets a customer answer which agent updated which CRM record, when and under whose authority. Sourcesanalabs.com/products/sana and support.sana.ai/en/articles/148586-sana-agents-101read 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 |
||
|
SanaDeployment & Data Residency Customers can run Sana in their own cloud. Sana describes itself as a SaaS solution with managed hosting by default that "can be deployed on your cloud infrastructure", and it isolates each customer with a single tenant architecture, so no databases are shared between customers. Enterprise organizations can also get their own single tenant deployment, and a Regional deploys badge sits in the product page's security strip. Sana publishes no region list and no deployment guide for the customer cloud option, and it describes no on premises or air gapped mode. Enterprise partnership services add a dedicated deployment lead, implementation support, tailored onboarding and a change management model. Sourcesanalabs.com/products/sana/security, sanalabs.com/agent-pricing and sanalabs.com/products/sanaread 2026-10-24 |
||
| 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 |
||
|
SanaPrebuilt Agents, Templates & Packs A browsable templates surface and unlimited assistants come even on the free tier. Tasks are "pre-designed frameworks that help you quickly create and manage AI-driven content", which customers explore "to save time, maintain consistency, and boost productivity". Designed in advance, browsable and selected from a gallery, each does work when chosen. The help center's tier guide gives the Free tier "unlimited agents and prompt templates". Tasks are independent frameworks for unrelated content jobs, and none depends on another. Sana publishes no count of available tasks and has no agent template marketplace with third party contributions, so the surface exists but its size is unknown. Workday's own HR, finance and IT agents belong to the acquirer and are not part of Sana's catalog. Sourcesupport.sana.ai/en/articles/148586-sana-agents-101 and support.sana.ai/en/articles/157324read 2026-10-24 |
||
| 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 |
||
|
SanaModel Flexibility & Routing Customers choose and switch models. A model agnostic section says "Only use the AI models that work best for you. With Sana, you can choose and switch between leading models as you need." The AI agents page names the options as Azure, Anthropic, Cohere, OpenAI and self hosted models, beside the line "Choose the best model for the task and optimize performance continuously." The help center's tier guide puts OpenAI and Claude model selection on the Team tier and additional models on Enterprise, and the Enterprise plan lists an extended range of LLMs. Assistants are configured per instance, and administrators can enable or disable web browsing for any assistant they create. Sana uses third party providers under enterprise security arrangements and, whenever possible, a zero day retention policy. Sana does not say how a model is picked for each step. Sourcesanalabs.com/products/sana, sanalabs.com/products/sana/ai-agents and support.sana.ai/en/articles/157324read 2026-10-24 |
||
|
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 |
||
|
SanaAPIs, SDKs & MCP Extensibility Extension mostly runs outward, with Sana calling what the customer builds. The Enterprise plan includes an "MCP client for building your own integrations", and "Enterprise customers can also build custom integrations to Sana Agents". An MCP client means Sana consumes servers the customer stands up. The AI agents page and the help center's tier guide also list API access on Enterprise ("API access for building your own integrations", "Custom integrations & API access"), but Sana publishes no REST or GraphQL API reference for Sana Agents, SDK, developer portal, webhook or A2A card, so what an outside system can call is not described. A REST API exists for Sana Learn, Sana Labs' separate learning product, on a different help center, and does not cover Sana Agents. Sourcesanalabs.com/agent-pricing, sanalabs.com/products/sana/ai-agents and support.sana.ai/en/articles/157324read 2026-10-24 |
||
|
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 |
||
|
SanaTesting, Debugging & Optimization Customers have no way to evaluate a change. There is no sandbox or dry run to test an assistant before it acts on live data, no evaluation harness, no scored test cases, no regression check when a prompt template or assistant scope is edited, and no A/B comparison of configurations. That matters here because customers build their own agents in Sana, creating unlimited assistants with no coding, scoping each one's sources and web access, and letting them "take instant actions across your tools". With no test surface, the first run of a new assistant is the production run. The Enterprise "analytics dashboard to measure impact" is adoption reporting, the feedback function is a signal feeding Sana, not a harness the customer runs, and deep linked citations let a person verify one answer by hand, which checks an output, not a change. The enterprise surface is gated behind sales. Sourcesanalabs.com/products/sana and support.sana.ai/en/articles/148586-sana-agents-101read 2026-09-12 |
||
| 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 |
||
|
SanaBrowser & Computer Use Connectors, not screens, carry the work to outside systems, so there is no browser or computer control. There is no hosted or local browser the agent drives, desktop session, or remote or local computer control. The architecture is 100+ named application connectors authenticated with OAuth, plus an MCP client for anything not covered. The word browsing appears prominently, but it means retrieval. "Search web extends your reach by integrating internet search results directly into Sana Agents", and administrators can enable or disable web browsing per assistant. That folds public web results into the answer alongside internal content, and nothing navigates, clicks, fills a form or keeps a session on the customer's behalf. The iOS and web apps are Sana's own clients. Sourcesanalabs.com/products/sana and support.sana.ai/en/articles/148586-sana-agents-101read 2026-09-12 |
||
Pricing snapshot
Sourced from the Index pricing dataset · open each vendor's profile for full detail.
| Pricing | D Dust |
S Sana |
|---|---|---|
|
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. | Free tier; paid plans not published |
|
Pricing confidence How public the numbers are |
Public, exact | Public, partial |
|
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. | per user / month |
|
Variable cost Workload / overage exposure |
Medium variable cost | Low variable cost |
|
Free tier / trial Try before you buy |
Free tierTrial
|
Free tier
|
|
Buying motion Self-serve vs sales call |
Mixed | 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
Sana
-
· Agent capability
Sana is now the Workday Home, an agentic experience that brings tasks, decisions, meetings and agent activity into one view.
Source -
· Integrations
Workday announced the general availability of Workday Learning powered by Sana, integrating Sana's AI learning technology with Workday's Human Capital Management platform.
Source
Sana has been part of Workday since September 2025 and keeps its own name.
More comparisons with Dust or Sana
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.