Oz vs. Dust

Dust helps teams build agents. Oz gives teams a teammate out of the box.

Dust is compelling for organizations that want to create company-aware agents and collaborate with them. Oz is a more direct path for operators: ask for the result, let Oz pull context, then approve and use the output.

Try Oz Visit Dust

vs.

Dust

private contexthuman approvalfinished artifact

From signal to shipped work

Oz adds the operating layer around Dust.

Signal

Where Dust fits

Dust is a platform for building or orchestrating automations.

02Context

Company memory

Oz blends the outside signal with private CRM, email, Slack, docs, meetings, and relationship context.

03Control

Approval gate

Anything risky pauses for review, so sends, deletes, payments, and customer-facing work keep a human in the loop.

04Output

Finished work

The result comes back as a brief, deck, recap, follow-up, plan, or file the team can use immediately.

The real buying question

Where does the work actually stop?

The useful comparison is not who can produce an impressive answer. It is where the system sits when the answer needs to become real work.

Start

Dust is strongest at the signal layer.

It helps when the team already knows the system it wants to build or the surface where AI should help.

Middle

Oz keeps the business context attached.

The work keeps private company memory, approvals, and customer-ready formatting in the same loop.

End

The adoption test is what ships next.

A team comes back when the output is a brief, deck, plan, send, or file they can use immediately.

Decision map

Pick based on what happens after the answer.

Best when

Choose Dust when

Dust fits teams ready to define, deploy, and manage multiple internal agents.

Internal agent building
Company knowledge access
Collaborative AI workspaces

Best when

Choose Oz when

Oz fits teams that want one teammate with deep memory before they design an agent portfolio.

Lower setup burden for everyday operators
Outcome-specific skills and deliverables
Channel-native work in Slack, Teams, email, web, and voice

Checkpoint

What to watch

Make sure the tool covers the work after the first response, not only the answer itself.

Agent platforms create power, but also design work.
Teams need a clear owner for agent quality, permissions, and adoption.

What Oz adds

The practical difference.

These are not abstract feature boxes. They are the moments that decide whether an AI system becomes a habit for the team.

LensDustOz

Primary jobDust is a platform for building or orchestrating automations.Oz is the teammate operators can ask for the finished outcome.

Who buildsBuilders configure flows, agents, tools, prompts, or apps.Operators ask in plain language; Oz chooses the skill path and delivers.

Time to valueFast for teams with a builder who owns the system.Fast for teams that want useful work without a platform project.

GovernanceGovernance is configured by the team and varies by deployment.Approvals, logs, cost units, and memory review are first-class product surfaces.

Verdict