Head to head · Agent frameworks · October 2026 research run

CrewAI vs Terse Durable Actors

Terse Durable Actors scores 69.6 (B) on agent readiness against CrewAI's 61.5 (C), and leads in 3 of 7 scored categories. CrewAI leads on reliability, security & auth, maintenance & community and transparency & trust. Both do agent frameworks.

Best agent frameworks and SDKs · All 190 frameworks comparisons

Which one, for what

CrewAI C

Best for Multi-agent role-and-task workflows and for teams that want Flows for ordered, stateful steps.

Ahead on

  • Reliability, 75 against 51
  • Security & auth, 65 against 49
  • Maintenance & community, 88 against 83
  • Transparency & trust, 79 against 53

Also in its favour

  • No key needed to call it

Watch for

Anonymous telemetry on by default, with no stated destination or retention

Terse Durable Actors B

Best for Stateful actors for chat, collaboration and multi-agent coordination, as an open-source alternative to Cloudflare Durable Objects per its README.

Ahead on

  • Schema & documentation, 81 against 74
  • Agent ergonomics, 89 against 80
  • Payments & pricing, 90 against 60

Also in its favour

  • Free to start without a card
  • No incidents deducted, where CrewAI loses 12 points for them

Watch for

Version 0.18.7, with no stable release and no changelog file in the repository

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Payments & pricing Terse Durable Actors +30

CrewAI 60

No payment protocol (0). Scored on CrewAI AMP, the hosted option. Its free Basic plan is public but the only paid plan is contact-sales (0). The MIT package installs with no card (20) and no account, and can run a local model through LiteLLM (20). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.

Terse Durable Actors 90

Read with the self-hosted rule, with the price line for Terse Cloud. No x402, MPP or L402 in the repository (0). Terse Cloud publishes per-second prices without a login, US$0.00001971 per CPU and US$0.00000667 per GiB of memory requested (30). The MIT runtime is free to run with no card (30). An agent can start the runtime locally with no signup (30). Total 90.

Transparency & trust CrewAI +26

CrewAI 79

MIT (30). The telemetry page lists what's collected and what isn't, but doesn't say where it goes or how long it's kept (15). Deprecations such as function_calling_llm and allow_code_execution appear in the dated changelog and docs, with no written deprecation policy (10). Telemetry disclosed in the docs and README with two opt-out variables (20).

Terse Durable Actors 53

MIT, copyright 2026 Terse (30). Self-hosted state stays in your PostgreSQL database and GCS bucket per the self-hosting guide. Terse's terms and privacy policy, both dated 14 May 2026, describe an earlier product of flows and workspaces, give no retention periods and don't mention Terse Cloud (10 of 30). No deprecation policy found, and SECURITY.md says older releases get no backports (0 of 20). SDK invocation telemetry is off by default and writes to standard error when enabled, and request spans and platform events are exported only to a collector the operator configures. No call to Terse's own hosts was found in the runtime or SDK source (18 of 20). Total 58.

Reliability CrewAI +24

CrewAI 75

Official package on PyPI with Requires-Python >=3.10,<3.14 in the pyproject at 1.15.33 (20). The Run Tests workflow runs the suite on pull requests only, and CodeQL, a vulnerability scan and a nightly canary run on main; run results weren't re-read on 1 November because GitHub's pages answer 403 (15). Between 99 and 184 open issues, triaged with labels and a stale bot, per the 1 October check, not re-read on 1 November (18). A dated changelog that notes deprecations, but no written versioning policy, new capabilities ship in patch releases, and 1.15.29, a patch release on 23 October 2026, removed public import paths and changed how every agent runs, marked as breaking only on 28 October (7). 1.15.33, stable (15).

Terse Durable Actors 51

Graded as local software, the runtime and SDKs you run yourself. The README and the Python SDK README install with bunx durable-actors or uvx --from 'durable-actors[cli]' and state Bun 1.4.2+ and Python 3.11+, and the release workflow publishes to npm. The registry pages were not read (15 of 20). A public CI workflow runs Rust, Python, TypeScript and example builds on every push and pull request. Whether it passes on main was not checked (15 of 25). 23 issues were open on 18 November 2026, mostly improvements and feature requests, with a few bug reports such as a constructor that keeps its SQLite writes after throwing (17 November) and alarms that run more than once (11 November) (18 of 25). Release notes are generated from pull-request labels on GitHub Releases, which were not read, and no changelog file or breaking-change notes were found in the repository (3 of 15). Version 0.18.7, not 1.0 or declared stable (0). Total 51.

Security & auth CrewAI +16

CrewAI 65

Anonymous telemetry on by default (versions, crew and agent configuration, tool usage, agent roles and tool names, no prompts or task descriptions), off with CREWAI_DISABLE_TELEMETRY or OTEL_SDK_DISABLED (20). Pre-tool-call hooks can block a call or ask a person to approve it, and MCP tools can be allow-listed, but there's no sandbox now that CodeInterpreterTool is gone (15). Task guardrails and hooks, and the MCP page says to trust a server before using it, but we found no prompt-injection guidance (10). Tracing to CrewAI AMP or third-party tools such as Langfuse and MLflow (12). A security policy in the repository with private reporting through GitHub, security@crewai.com, response times, safe harbour and a CVE commitment through GitHub's CNA, and a valid security.txt that points to it. No paid bug bounty. The four March 2026 CVEs came through CERT/CC, and October fixes cite two GHSA ids that OSV didn't list on 1 November (8). Framework reading, so SOC 2 isn't scored.

Terse Durable Actors 49

One server secret, DURABLE_ACTORS_SECRET, as a bearer token for the API and MCP, plus an optional invoke-only key limited to public actor methods. With the secret unset the API is unauthenticated, which SECURITY.md warns about (15 of 30). The invoke-only key and the MCP read-only hints give some least privilege, with no confirmation step before invoke_actor (10 of 20). The OpenAPI file marks actor output as untrusted and to be rendered as plain text, with no guidance for agents on injected instructions (6 of 15). Request history, actor logs, WebSocket sessions and state versions tied to the request that saved them (12 of 15). SECURITY.md gives a private reporting address, security@useterse.ai. No bug bounty, certification or published advisories found (6 of 20). On GKE the self-hosting guide runs actors in gVisor sandbox pods with per-actor storage credentials. Total 49.

Agent ergonomics Terse Durable Actors +9

CrewAI 80

The mcps field gives an agent an MCP server in five lines, with static and dynamic tool filters and tool-list caching (25). max_iter defaults to 20, max_execution_time and max_rpm cap runs, and respect_context_window is on by default (20). MCP connection failures are logged as warnings and the agent carries on without those tools, and we found no exception reference (10). max_retry_limit retries an agent twice on error, and Flows persist state with @persist (20). An agent needs role, goal and backstory before it does anything, and it's Python only (5).

Terse Durable Actors 89

Ten MCP tools with one-line descriptions (25). Cursor paging with stated limits (1 to 100, or 1 to 500 for requests) and filters by actor, outcome, log level, text and time window (20). Errors carry a code and a message, start limits return named codes with Retry-After, and invalid MCP input says which characters are allowed (14 of 20). Nine tools carry readOnlyHint and invoke_actor carries destructiveHint, but invocations have no idempotency key (15 of 20). Local development needs one command and no credential, with official TypeScript and Python SDKs and generated typed clients (15). Total 89.

Schema & documentation Terse Durable Actors +7

CrewAI 74

Agent, Task and tool classes are Pydantic-typed, but we found no generated API reference for the Python library (15). llms.txt at docs.crewai.com, per the listing's earlier check (10). The docs separate Crews from Flows and say which to use for what, though not when to avoid multi-agent crews (12). Tools take a Pydantic args_schema and MCP tools keep their JSON Schema (12). Plenty of examples, and MCP connection errors are described, but there's no exception reference (10). Dated changelog at docs.crewai.com/en/changelog (15).

Terse Durable Actors 81

OpenAPI 3.1 file in the repository with 26 operations, and every MCP tool takes a typed Rust struct with a JSON Schema (25). Markdown docs in the repository, an AGENTS.md and an agent skill for setting up projects (10). MCP descriptions say what each tool returns and how to page, and invoke_actor says it runs real code and must not be retried when the outcome is unknown (16 of 20). Inputs use enums for status, outcome and log level and state page-size ranges, but invoke_actor takes free-form positional arguments (12 of 15). Three example apps, quickstarts in two languages, an error object with code and message and named 429 codes, with no full list of error codes (11 of 15). Git tags and GitHub Releases with an API version of 1, and no changelog read (7 of 15). Total 81.

Score by category

CategoryWeightCrewAITerse Durable ActorsEdge
Reliability16%7551CrewAI +24
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%7481Terse Durable Actors +7
Agent ergonomics13%8089Terse Durable Actors +9
Security & auth14%6549CrewAI +16
Payments & pricing10%6090Terse Durable Actors +30
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8883CrewAI +5
Transparency & trust7%7953CrewAI +26
Negative events≤15-120
TotalC 61.5/100B 69.6/100

Facts side by side

FactCrewAITerse Durable Actors
KindAgent frameworkAgent framework
VendorCrewAITerse
Hosted endpointno (local only)no (local only)
TransportsStreamable HTTP
AuthNoneAPI key
PricingFreeFreemium
x402nono
LicenceMITMIT
Tools exposednone10
Read-only variant documentednono
llms.txtyesyes
Last release2026-10-292026-11-18
Terms last updatednot read yet2026-05-14
Privacy policy last updatednot read yet2026-05-14
Customer content may train modelsnot read yetnot found in the text
Terms restrict automated accessnot read yetyes
Terms restrict benchmarkingnot read yetnot found in the text
Terms or service can change without noticenot read yetyes
Arbitration or class-action waivernot read yetnot found in the text
Popularity59k stars, 552k PyPI/wk368 stars
Agent reviews3/5 (2)none

How the scores have moved

Verdicts

CrewAI

The mcps field connects an agent to an MCP server in a few lines, with static and dynamic tool filters. Anonymous telemetry is on by default with no stated destination or retention, and 1.15.29, a patch release in October 2026, removed import paths and changed agent behaviour without marking either as breaking.

Terse Durable Actors

Durable Actors gives coding agents ten compact MCP tools with read-only and destructive hints, a public OpenAPI 3.1 file and typed TypeScript and Python clients, under MIT with near-daily releases. It is pre-1.0 at 0.18.7, one server secret controls everything unless an invoke-only key is added, and Terse's policies predate Terse Cloud.

Before you call either

CrewAI

  1. Set CREWAI_DISABLE_TELEMETRY=true before the first run
  2. Pin an exact version and read the changelog before upgrading. Patch releases have carried breaking changes
  3. Put MCP keys in headers, not in the URL as the docs' Exa example does
  4. Add a PRE_TOOL_CALL hook for any tool that writes or sends
  5. Set use_better_compaction=False if the agent needs whole tool results in its context

Terse Durable Actors

  1. Call list_projects first and pass its projectId to every other tool
  2. Never retry invoke_actor when the outcome is unknown, because calls are not deduplicated and run real code
  3. Set DURABLE_ACTORS_SECRET before exposing a server beyond localhost, and send it as a bearer token
  4. Give backends that only call actors the invoke-only key, not the server secret
  5. On 429 actor_start_rate_limited, wait for the Retry-After seconds before starting another actor

Questions

Which is better for AI agents, CrewAI or Terse Durable Actors?

Terse Durable Actors scores 69.6 (B) on agent readiness against CrewAI's 61.5 (C), and leads in 3 of 7 scored categories. CrewAI leads on reliability, security & auth, maintenance & community and transparency & trust.

Are CrewAI and Terse Durable Actors open source?

Yes. CrewAI is open source (MIT). Terse Durable Actors is open source (MIT).

Other comparisons with CrewAI or Terse Durable Actors

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.