Deer-Flow GitHub is where trust starts. The workspace is where work continues.

What to inspect in the repository

Start with the README, installation notes, configuration example, Docker folder, backend and frontend directories, and security notice. Those files tell you how the project expects models, tools, memory, and sandbox execution to be configured.

Also inspect the active development branch and release notes. DeerFlow 2.0 is positioned as a ground-up rewrite, so old 1.x assumptions may not apply.

• Check model provider configuration before planning a run.
• Check sandbox mode before enabling shell or file tools.
• Check memory behavior before using DeerFlow for repeated work.
• Check message-channel configuration before exposing tasks to chat tools.

When GitHub is enough

GitHub is enough when you only need to inspect the code, run a local demo, or decide whether the architecture fits your team.

GitHub stops being enough when the buyer needs onboarding, plan choice, a production checkout path, analytics, and a focused commercial workflow that non-maintainers can understand.

How the managed site complements GitHub

This site keeps the public repo link visible but does not force every visitor into a code-first path. The mission planner turns repository curiosity into a concrete buying decision.

That is useful for technical founders, automation teams, and operators who already understand DeerFlow but need a quicker way to package the first serious workflow.

Common questions