Describe the outcome. Keep the system yours.

Have a short conversation about what you want. Doso reasons about how to get there, designs a workflow, asks permission before consequential actions, then works, checks progress, and adapts until the outcome is achieved — without locking your graphs, tools, host, or models to one vendor.

Why Doso

The primary benefits are ownership and choice. Doso is open source and designed so the durable parts of the system remain under your control.

Your graphs stay yours

Knowledge and workflow graphs you build over time remain yours, always. No vendor lock-in.

Thousands of services

Connect third-party tools through your own Composio account, or build your own integrations.

Connections you control

Composio toolkits, or a paired desktop runtime for host CLIs.

Host anywhere

Run locally, on your own server, in any cloud, in any country.

Any model, anywhere

Choose any inference provider and any model. Swap when you want.

The outcome loop

Start in Chat with the result you need: “Get the launch plan ready for Friday. Include owners for every task, resolve scheduling conflicts, and ask me before sending anything.” Doso asks only for missing details, then turns the conversation into work it can carry forward.

  • Describe the outcome along with the constraints and finish conditions that matter
  • Let Doso reason about the path and design a workflow for reaching the result
  • Set permission boundaries so Doso pauses before sending, publishing, purchasing, or making another consequential change
  • Let Doso work, inspect the result of each step, and adjust when new information or a blocker changes the plan
  • Doso verifies the finish conditions and returns the completed outcome

If work pauses, use History to resume the outcome with its progress and decisions intact.

Context and configuration stay portable

Choose any model provider in Settings. Connect hosted services through your Composio account, or pair a desktop runtime for host CLIs. Keep material in your Library, facts in Knowledge, and preferences in Memories. Deploy with compose or in any cloud. These choices help Doso work better without making the product depend on one vendor stack.

Start with a finish line

Name the result and how you will know it is done: “Prepare three viable venues for the team offsite, confirm availability for our dates, keep the total under $8,000, and stop before booking.” Doso can now plan the work, verify each option, and return when the decision is ready for you.

Decisions and deeper docs

Product UX guides live in this section. Call the HTTP surface from the API Reference. Architecture, deployment, security, and other decisions from the repo are published under Concepts, Reference, Deploy, and Security— mirrored from the markdown sources of truth.