65%
automation rate on contact centre workflows
NOS
80%
reduction in document processing costs
Sonae Sierra
6–12
weeks from kickoff to production deployment
GenOS delivery model
Why GenOS
What makes GenOS different from Dust
01
Built for the team doing the work
Dust is a product for IT owners who configure OAuth apps and manage agent permissions. GenOS is built for the operations manager whose team will use the system. They do not configure anything. The Forward Deployed Engineer handles deployment, integration, and ongoing tuning.
02
Beyond the chat window
Dust's surface is a workspace chat interface. GenOS runs across WhatsApp, voice, your website widget, and email. It processes documents in the background without any chat interaction. That is a wider definition of AI work.
03
An operating layer that improves after launch
Dust ships product updates. GenOS's Forward Deployed Engineer runs a continuous improvement loop after go-live: usage analysis, knowledge gap detection, conversation quality scoring, and model routing refinement. The system gets better because someone is responsible for making it better.
Why switch to GenOS
Teams choose GenOS over Dust when
- Your operational workforce will not configure anything themselves. They need a system the FDE stands up.
- You need multi-channel customer-facing agents: voice, WhatsApp, chat widget, email continuity
- High-volume document automation is in scope. Dust has no Supervisor-equivalent pipeline product.
- You need post-go-live improvement as a service: FDE-led usage analysis, knowledge audits, quality evaluation
- Your governance requirements go beyond per-function stake settings: cross-agent audit trails, RBAC at the workflow level, and a unified control plane
Feature by feature
| GenOS | Dust | |
|---|---|---|
| Day-1 polish and UX | Production-grade deployment; more operationally shaped than self-serve | Polished, opinionated workspace with strong UX: Connections, Tools, Skills are clean primitives |
| Deployment model | Named FDE builds and configures the deployment; workforce uses without technical ownership | Self-serve SaaS: IT or Platform owner builds and governs; no deployment partner |
| Customer-facing service agents | Multi-channel ServiceAgent: web widget, WhatsApp, voice, email continuity | Workspace-only chat surface; no customer-facing multi-channel agent product in evidence |
| Document and workflow automation | Supervisor: deterministic pipelines for invoice processing, order intake, document classification at volume | No case-management, operator inbox, or volume-processing pipeline product |
| MCP catalogue depth | Growing catalogue; FDE installs and configures on behalf of the customer | 42 prebuilt MCPs on day one, plus custom MCP server support: the widest available catalogue |
| Per-function governance | Agent-level RBAC and audit trail; per-function granularity on roadmap | Per-function enable/disable plus 4-tier stake setting (High/Medium/Low/Never): production-grade today |
| Cross-agent audit trail | Cross-workflow, cross-agent audit log with reasoning context: a core platform capability | Per-agent insights exist; global cross-agent tool-call audit log not confirmed in public UI |
| Post-go-live improvement | FDE-led improvement loop: usage analysis, knowledge audits, quality evaluation, model routing optimisation | No equivalent. Dust ships product updates; no one at Dust improves your specific deployment. |
| European enterprise fit | Built from DareData deployments at European enterprises; BYOC and on-prem for data residency | Paris-based, European-native; BYOC not confirmed |
| Audience | Operational workforces: logistics, finance, customer service, that will not self-configure | Technical buyers: IT owners, Platform teams, SaaS-heavy knowledge-worker companies |
Frequently asked
What is the difference between GenOS and Dust?
Dust is a self-serve workspace for technical teams who build their own agents. GenOS is an operational deployment for workforces that will not self-configure: a named engineer builds and runs it across customer service, document automation, and one governed control plane.
Does GenOS handle customer-facing and document workflows like Dust?
GenOS goes further here. Dust's surface is a workspace chat interface. GenOS runs multi-channel service across web, WhatsApp, voice, and email, and processes documents at volume through deterministic pipelines, which Dust has no equivalent for.
Who is GenOS built for compared to Dust?
Dust suits technical buyers and platform teams who configure their own tools. GenOS suits operational workforces in logistics, finance, and customer service who need a system stood up and improved for them by a named engineer.
Bottom line
Dust is strong self-serve infrastructure for technical teams. GenOS is for the operational workforce that will not configure OAuth apps: customer-facing agents across voice, WhatsApp, and chat, document pipelines at volume, and a governed control plane, all stood up and improved by a named engineer. A workspace and an operating system serve different audiences.
See in practice
Next step
Book a working session. We run it in your environment, on your data.