Dify builds LLM apps. OrchKernel governs what agents do.
Dify is a platform for building LLM apps and agents, with a visual workflow editor and retrieval over your documents. OrchKernel decides what any agent may do in your systems, and records it.
Different tools, different jobs
Dify and OrchKernel answer different questions. You can use both.
What Dify is for
Building LLM apps and agents visually.
- A platform for building chat apps, workflows and agents on LLMs
- A visual editor for designing the flow
- Retrieval over the documents you add
What OrchKernel is for
Deciding what agents may do, and proving what they did.
- Puts one gate between every agent and everything it touches
- Checks kill switches, arguments, delegation, budgets, rules, then risk against trust
- Holds risky actions for a person, who sees the exact payload
- Keeps vendor keys away from agents and runs approved actions with its own credentials
- Records every action in a tamper-evident log, with rules kept in Git
- Runs on your infrastructure: one binary and one database file
Running them side by side
Keep the app you built. Add the gate in front of the systems its agents touch.
- 01
Keep building in Dify
Your app keeps its flows, its prompts and its knowledge.
- 02
Give each agent an identity
In OrchKernel, each outside agent gets a trust tier, a budget and the person it acts for.
- 03
Send actions through the gate
The Dify agent asks OrchKernel before it acts, through the governed actions API or the MCP gateway.
- 04
Rules decide, the kernel applies
The answer is allowed, needs approval or denied, with the reason. Approved actions run with OrchKernel's credentials and land in the log.
When to use which
You may need one, the other, or both.
Dify on its own is enough when…
- The app answers questions from your documents and does not act
- You are trying out an idea and nobody depends on it yet
- One team owns the app, its keys and its risks
Add OrchKernel when…
- The agent will email customers, issue refunds, change records or ship code
- Someone must approve risky actions before they happen
- You need to prove what an agent did and who allowed it
- Agents built in different ways need one set of rules
Dify and OrchKernel questions
Put one real workflow through the gate
We help you run it on OrchKernel, on your own systems.