Skip to content
Comparison

CrewAI builds teams of agents. OrchKernel governs what they do.

CrewAI is a Python framework for agents that each take a role and work through tasks together. OrchKernel decides what any of them may do in your systems, and records it.

Two jobs

Different tools, different jobs

CrewAI and OrchKernel answer different questions. You can use both.

What CrewAI is for

Designing how a team of agents splits the work.

  • A Python framework for building crews of agents
  • Each agent has a role and a goal, and the crew works through tasks
  • Your engineers own the code and how it runs

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
Together

Running them side by side

Keep the crew you designed. Add the gate in front of the systems it touches.

  1. 01

    Keep building in CrewAI

    Your crew keeps its roles, its tasks and its code.

  2. 02

    Give each agent an identity

    In OrchKernel, each outside agent gets a trust tier, a budget and the person it acts for.

  3. 03

    Send actions through the gate

    The CrewAI agent asks OrchKernel before it acts, through the governed actions API or the MCP gateway.

  4. 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.

Decision guide

When to use which

You may need one, the other, or both.

CrewAI on its own is enough when…

  • You are exploring how several agents should split a task
  • A person reads the crew's output before anything acts on it
  • One team owns the crew, 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

CrewAI and OrchKernel questions

Put one real workflow through the gate

We help you run it on OrchKernel, on your own systems.

Runs on your own servers. The repository opens soon.