Dust

What it can cover

• ✓Search across multiple internal sources
• ✓Answer questions with company context
• ✓Respect source-system permissions
• ✓Find documents, experts and historical knowledge
• ✓Support internal assistants grounded in company data

When it may be enough

• ✓Required data sources are covered by available connectors
• ✓The primary need is internal search and knowledge access
• ✓Source permissions can be synchronized reliably
• ✓The company prefers deploying a product over operating its own RAG stack

When custom may make more sense

• ×Retrieval, ranking or orchestration is strategically proprietary
• ×Important sources cannot be reached through available connectors
• ×The capability must be embedded in an external customer-facing product
• ×Sovereignty or infrastructure constraints are unusual

Strengths

• ✓Cross-system search
• ✓Enterprise connectors
• ✓Permission awareness
• ✓Shorter time to value

Watchouts

• ×Connector coverage is decisive
• ×Governance still matters
• ×Enterprise pricing
• ×Quality depends on source data