Agentic Index
Dust vs Writer (2026)
Both vendors last verified
Dust lets every team build its own agents on a model it picks, while Writer builds its own Palmyra models and runs governed agents on them. That verdict is the Agentic Index coverage score, graded from each vendor's own published materials.
On Dust, a Paris platform, each agent can run on any of more than 20 models and draw on Slack, Notion, Drive and dozens of other sources. Its prices are public and in euros, from a free seat to Pro at €24 a seat a month on yearly billing and Max at €120 a seat. Writer runs WRITER Agent on Palmyra, with more than 100 ready agents, playbooks that run on schedules, brand voice controls and browser automation. It sells a Starter plan for up to five users with a 14 day free trial, and custom enterprise plans with no published price. Choose Dust when many teams will build their own agents and want to pick the model and see the price. Choose Writer when governed, on brand output at enterprise scale matters most and one vendor should supply both the model and the agents.
This comparison is published by Agentic Index, an independent agentic AI vendor research platform. Dust and Writer 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
This comparison, as a video
Dust vs Writer in 3 minutes
A short walkthrough of what each product does, how they are priced, where they overlap and when to choose each.
Choose Dust if
- Many teams will build their own agents, starting from templates and trying each change in a preview before it goes live.
- You want to pick the model for each agent from more than 20, across OpenAI, Anthropic, Google, Mistral and DeepSeek.
- Public per seat prices, with a free seat to start, suit how you buy software.
Choose Writer if
- Output has to stay on brand and compliant, with voice profiles, guardrails and approval steps built into each playbook.
- You want one vendor for the model and the agents, with Palmyra models trained for business work.
- Agents need to operate websites directly, or the platform has to run in your own environment.
| Feature | D Dust |
W Writer |
|---|---|---|
| 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 |
||
|
WriterIntegrations & Tool Calling WRITER Agent writes into systems Writer does not own. The Asana connector lets it "access available workspaces and team members, create, read, update, and delete tasks and subtasks, and retrieve task details, comments, dependencies, and project structure". The Salesforce integration is built by Writer, works in both directions, is published on AgentExchange, and lets the agent "query CRM data, manage records, run reports, and automate workflows". Connectors has its own place in the main product navigation, with Microsoft SharePoint, Semrush, Snowflake, HubSpot and Microsoft Teams in the in product picker alongside Asana and Salesforce. Worked examples write across systems, from "Update the GTM report in SharePoint with campaign metrics" to a Snowflake query feeding a campaign that ends with emails actually delivered. Connector Profiles let administrators configure several versions of the same connector with different permissions per team, and every agent request to a connected system passes an identity and permission check. Custom connections are open too, since agents can discover and call external tools through MCP connectors, one of the nine capabilities Writer scores. Sourcewriter.com/product/writer-agent connectors, writer.com/product/connectors, support.writer.com what's new Asana and Salesforce entriesread 2026-09-13 |
||
|
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 |
||
|
WriterWorkflow Orchestration Given a goal, WRITER Agent "autonomously plans and executes work across your data and tools", and once told what to accomplish, "it builds the plan to get there, mapping every step across the right data and tools". A worked example chains a whole job, analyzing churned customer segment data in Snowflake, selecting top customers per segment, mapping product SKUs to segments, creating personalized email content, then deploying test emails and verifying delivery, tracked as a three section checklist with subtasks completing in sequence. On duration, Writer says "X6 holds one goal for up to eight hours", planning, executing, testing its own output, correcting and delivering finished work, and a sample run timeline shows Plan, Execute, Optimize and Deliver phases, with events at 01:00 "Plan locked: 41 tasks", 03:42 "Self-test failed then fixed", and 08:00 "Shipped: verified", so the agent backtracks and recovers from errors inside a single objective. Agents can delegate work to spawned sub-agents and merge the results, one of nine capabilities Writer scores, and AI Studio composes ready-to-use agents as building blocks that "interact with other ready-to-use and custom agents to automate complex, end-to-end business processes". The durable unit is the Playbook ("repeatable workflows, not one-off prompts"), with version control, edit history and restore in AI Studio. Sourcewriter.com/product/writer-agent how-it-works, writer.com/models endurance sectionread 2026-09-13 |
||
|
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 |
||
|
WriterTriggers & Channel Coverage Agent work starts on a clock, on external events and from meetings, not only when a person asks. Schedule based triggers, first launched as Routines to "schedule playbooks to run on a daily, weekly, or monthly basis, so your reports are ready when you are" and since renamed Triggers, run playbooks automatically on a recurring schedule, and event based triggers sit alongside them. Meetings are a third source. WRITER Agent "joins the call, transcribes in real time, and gives every attendee the same summary of decisions and next steps", then kicks off the follow up work, and the meeting surface offers "Run a playbook from the meeting". Channels include the web application, WRITER for Slack, a Salesforce integration that works in both directions and is published on AgentExchange, the meeting surface, and the developer API at dev.writer.com. Sourcesupport.writer.com what's new schedule-based and event-based triggers, writer.com/product/writer-agent meeting sectionread 2026-09-13 |
||
| 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 |
||
|
WriterKnowledge Grounding & RAG The Knowledge Graph, now sold as Enterprise Brain, is a persistent graph that connects agents to enterprise sources for retrieval. Grounding, which Writer defines as "knowledge-graph and document grounding, retrieval, and citation", is one of nine capabilities it measures and publishes a score for. Answers cite their sources, alongside activity traces and decision logs, and Writer's evaluation describes pulling twenty-two sources through a knowledge graph and citing each one. Connectors including Microsoft SharePoint, Snowflake, HubSpot, Salesforce, Microsoft Teams and Semrush feed the graph, with direct document upload alongside, and ready-to-use agents are "grounded in business context via WRITER's Knowledge Graph and document upload". Web search is a separate capability that admins switch on or off, using a standard search engine for current outside information, while grounding rests on the customer's own indexed content. Sourcewriter.com/models capability table and FAQ, writer.com/product/enterprise-brain nav, writer.com/trust explainabilityread 2026-09-13 |
||
|
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 |
||
|
WriterMemory & State Persistence WRITER Agent builds a memory of how each person works as they go, keeping output structure and tone, the tools and processes they use, the sources they trust, recurring projects and formatting preferences. Personal memory stays private to its owner, and context that three or more teammates share is promoted to team memory. People can see what was kept under Customize, Agent Insights, mark items relevant or not, and switch capture off for a session with incognito mode, while admins turn memory on by team and choose where it is stored. Writer states no lifetime for a memory and describes no way to delete one. The feature is an opt in beta that starts switched off, with Writer planning to turn it on for enterprise organizations on Writer managed storage from the end of August 2026. Users can also give WRITER Agent a personality with different voices and custom instructions, plus reusable voice profiles. Sourcesupport.writer.com Understanding WRITER Agent Memory and How to configure Agent Memory for your organizationread 2026-10-21 |
||
| 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 |
||
|
WriterHuman Oversight & Guardrails During a run, WRITER Agent "knows when to act and when to ask", and it "autonomously executes the plan and stops along the way for input", so the user stays "in full control without micromanaging every step". Since 15 September a playbook step can carry an approval, which pauses the run until a designated reviewer signs off, and since 30 September playbooks an admin has approved show a badge in team libraries. Approval before deployment is a separate layer, since "governance is built into the agent lifecycle, from pre-deployment approvals to monitoring in production", and guardrails, identity validation, granular permissions and approval flows shape how agents interact with connected systems. Admins set limits ahead of time. In AI Studio, Capabilities settings enable or disable high level functions per organization, browser automation is scoped to an allowlist or blocklist of named domains, web search is toggled separately, and agents are confined to the connectors, tools and knowledge sources they need. Configurable guardrails "detect and redact PII and screen outputs against copyrighted material", "before a single word leaves the building", with prompt injection defense on every connection between an agent and a system, and a data loss prevention guardrail blocks sensitive data before it reaches a model. Under "Govern workflows at scale", an admin can reassign ownership of playbooks and skills or disable them entirely. Sourcewriter.com/product/writer-agent, writer.com/trust safety and governance, support.writer.com Manage WRITER Agent 2026-09-13; support.writer.com what's new, step approvals 2026-09-15 and DLP guardrail 2026-10-13, readread 2026-10-21 |
||
|
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 |
||
|
WriterSecurity, Identity & Governance On certification, Writer says "We undergo annual SOC 2 Type II evaluations and hold ISO/IEC 27001, 27701, and 42001 certifications, confirming our implemented controls for security, privacy, and responsible AI management." It also covers HIPAA, GDPR and PCI-DSS, and ISO 42001 certifies an AI management system. On access, Writer says "We support all major SSO providers and multi-factor authentication; role-based permissions and least-privilege access helps ensure every action is appropriately authorized." SSO and SCIM, granular RBAC, audit logs and customer managed encryption keys cover automated provisioning, a role model, federation and keys the customer holds. For agents, "agent requests to connected systems pass through a governed execution layer that validates identity, checks permissions, and records activity", with scoping per connector so users and agents "only have access to the connectors, tools, and knowledge sources they need". Identity is validated on every agent request, not only at login, and tenant isolation at the infrastructure level and data separation between teams within one org sit alongside. Sourcewriter.com/trust security and transparency sections, writer.com/models enterprise-grade sectionread 2026-09-13 |
||
|
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 |
||
|
WriterObservability & Auditability Every agent action can be audited, in Writer's words "Audit every agent action. Get complete logs of every user action and agent session, searchable and exportable to your SIEM, and retained for compliance." Admins can enable WRITER Agent session logs and review user feedback in AI Studio, with session records and thumbs up or thumbs down feedback viewable in the product and exportable as JSONL or CSV for offline review. Reporting and logs cover usage, performance and costs in real time, token consumption is tracked live with alerts and hard blocks above target limits, adoption trends filter by team, billing group or seat, and each playbook has an Analytics tab showing runs, active users and submitted feedback. For explainability, "activity traces, source citation, and decision logs provide clarity into how AI reached an answer", and activity traces and performance reports help teams "monitor AI behavior, understand request patterns, and review how workflows are executed". Sourcewriter.com/product/ai-studio how-it-works section, writer.com/trust transparency and control section, support.writer.com what's newread 2026-09-13 |
||
|
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 |
||
|
WriterDeployment & Data Residency Self hosting is on offer, in Writer's words "Self-hosting and full data residency are available", alongside "managed, multi-cloud options, including dedicated private cloud deployment". Multi cloud is a choice among managed options, and the bring your own model path reaches into AWS Bedrock, Microsoft Azure and NVIDIA NIM on the customer's side, so the buyer picks where inference runs as well as where data sits. Data controls sit alongside, with customer managed encryption keys, tenant isolation at the infrastructure level, zero retention by default, and a configurable organization wide automated data deletion schedule. Writer does not publish a list of regions, so the residency jurisdictions on offer are not stated. Sourcewriter.com/models enterprise-grade section and writer.com/trust privacy and compliance sectionread 2026-09-13 |
||
| 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 |
||
|
WriterPrebuilt Agents, Templates & Packs The agent library at writer.com/agents/ is, in Writer's words, "a library of over 100 ready-to-use agents". They include the chart analysis agent, a "multimodal agent powered by Palmyra Vision" built to extract insights and perform contextual data interpretation from complex charts, the company financials research agent and the report generator agent. Ready-to-use agents are "quickly grounded in business context via WRITER's Knowledge Graph and document upload" and serve as "composable building blocks in Agent Builder", interacting with each other to automate end to end processes. Playbooks and Skills add two more packaged layers, each with its own gallery. Playbooks, billed as "repeatable workflows, not one-off prompts", come as structured units with an Overview, a "What it does" statement and a list of "Deliverables you'll get", and one example, an event outbound materials generator, returns email templates, LinkedIn messages, a cold call script and a materials guide. Skills are browsable from a grid with named entries including SEC Filing Parser, Finserv Compliance Checker, Weekly Campaign Performance and Voice of Customer Summarizer. Sourcewriter.com/blog/writer-agent-press-release 100+ ready-to-use agents, writer.com/blog/writer-ai-hq-press-release named agents, writer.com/product/writer-agent Playbooks and Skillsread 2026-09-13 |
||
| 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 |
||
|
WriterModel Flexibility & Routing Palmyra X6 is the default model but not the only one. In Writer's words, "X6 leads our evaluation, so it's the default, but it isn't the only option. Admins can enable models from other providers, and users can choose a model at the start of a session. Specialized models can be selected for specific capabilities, such as image generation. And beyond WRITER's own catalog, admins can bring their own models from AWS Bedrock, Microsoft Azure, and NVIDIA NIM." Admins enable models per provider in a control panel headed "Set what's available: control what models your teams can access", with a card for each provider (WRITER 8 of 8, Anthropic 9 of 9 and Google 0 of 5 models enabled) and each model toggled individually. "Users can pick the model they'd like to use for each session" from a searchable selector naming Palmyra X6, Palmyra X5, Claude Sonnet 4.6 and others, with the price of each model shown. A separate preset governs specialized models, with GPT-5 and Gemini 3 Pro Image Preview for image generation. Writer also publishes its own comparison chart against rival frontier models, and its positioning argues against "stitching together your own stack of third-party models", though the controls above let customers use other providers. Sourcewriter.com/models multi-model support section and FAQread 2026-09-13 |
||
|
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 |
||
|
WriterAPIs, SDKs & MCP Extensibility A developer site at dev.writer.com carries an introduction at dev.writer.com/home/introduction and a versioned model reference at dev.writer.com/home/models#palmyra-x6. Outside applications can call Writer in three ways. The Palmyra models are distributed through Amazon Bedrock, so a customer's own application can call them outside the WRITER application entirely. The Salesforce integration works in both directions, so Salesforce can drive Writer as well as being driven by it. And since 2 October, WRITER's own MCP server lets MCP compatible clients run playbooks, pull finished deliverables and read meeting transcripts over OAuth, so MCP runs into Writer as well as out from its agents to other tools. AI Studio fits into the customer's existing stack, integrating with monitoring tools, business systems, models and AI guardrails, and the Datadog Logs Plugin forwards LLM requests and responses to Datadog. Sourcewriter.com/product/ai-studio and writer.com/models Explore docs links to dev.writer.com, footers across the estate 2026-09-13; support.writer.com what's new, WRITER MCP 2026-10-02, readread 2026-10-21 |
||
|
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 |
||
|
WriterTesting, Debugging & Optimization Live metrics cover agents already in production, but Writer does not describe a way for a customer to test a change before it ships. Each playbook has an Analytics tab showing runs, active users and user feedback, thumbs up and thumbs down are captured on each agent output, viewable in AI Studio and exportable as JSONL or CSV, real time reporting covers usage, performance and cost, and an adoption view filters by team, billing group or seat. These all read on what is already running. Playbook version history lets an owner "track edits, view version history, and restore previous versions", so a change can be rolled back, though not tested first. Writer's nine dimension evaluation, "graded 0 to 1 against a locked baseline", scores Writer's own model. The agent's "self-test failed then fixed" step is self correction inside a single objective, and approvals before deployment decide whether a person permits a launch. Writer does not describe a harness customers run, scored test cases, a regression suite for a playbook edit or an A/B comparison of two agent configurations. Sourcewriter.com/product/ai-studio, writer.com/models evaluation FAQ, support.writer.com playbook analytics and version controlread 2026-09-13 |
||
| 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 |
||
|
WriterBrowser & Computer Use WRITER Agent has browser automation, governed from the Capabilities tab in AI Studio. In Writer's words, "Browser automation allows WRITER Agent to open a web browser in its secure sandbox environment. With this capability, the agent can perform tasks such as navigating to websites, reading page content, clicking on elements, and filling out forms." Under "Allow WRITER to use browser automation for", an org or IT admin picks "All websites", "Only specific websites" (marked Recommended) with an included URL list, or "Exclude specific websites" with a blocklist. Adding a domain automatically includes its subdomains, and wildcards are not supported. Writer does not say how the agent copes when page layouts change on sites it does not own. Web search is a separate capability with its own admin toggle that "enables WRITER Agent to use a standard search engine to find information and images from the web". Sourcesupport.writer.com Manage WRITER Agent, with writer.com/product/ai-studio capability controlsread 2026-09-13 |
||
Pricing snapshot
Sourced from the Index pricing dataset · open each vendor's profile for full detail.
| Pricing | D Dust |
W Writer |
|---|---|---|
|
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. | Starter is sold per seat, monthly or annually, for up to 5 users with fixed credit limits, and Writer's plans page prints no price for it. Enterprise is custom through sales. |
|
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. | Seats. Starter is priced per user, and Enterprise combines paid Pro seats with unlimited free Lite seats. AI Studio API usage is billed separately per million tokens. |
|
Variable cost Workload / overage exposure |
Medium variable cost | Medium variable cost |
|
Free tier / trial Try before you buy |
Free tierTrial
|
No free tierTrial
|
|
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
Writer
-
· Human approval / guardrails
Admins can now require approval before a Playbook, Writer's saved agentic workflow, becomes available to anyone beyond its owner and collaborators.
Source -
· Human approval / guardrails
A built in Data Loss Prevention guardrail in WRITER blocks a request before the model call when it finds personal data, financial data, government IDs, healthcare identifiers, or secrets and credentials.
Source -
· Agent capability
Writer released Palmyra X6, a new 744-billion-parameter model optimized for marketing and revenue tasks, alongside a rebuilt Agent harness.
Source
More comparisons with Dust or Writer
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.