---
title: "Guild vs CrewAI"
description: "Guild vs CrewAI: agent formats, integrations, credentials, triggers, approvals, self-hosting, and pricing compared, plus how to move a crew to Guild."
canonical: "https://www.guild.ai/compare/crewai"
---

# Guild vs CrewAI

Guild vs CrewAI: agent formats, integrations, credentials, triggers, approvals, self-hosting, and pricing compared, plus how to move a crew to Guild.

CrewAI is a Python framework for crews of role-based agents, with the AMP platform to deploy, trigger, and trace them. Guild runs agents in five formats, keeps credentials behind a proxy with rules per action, and shares agents on a public Agent Hub.

Last verified 2026-11-06. Across 35 features, Guild leads on 13, CrewAI on 4, and 18 are level. Every cell below names its source.

## When to choose CrewAI

- Your team writes Python and wants role-based crews of agents.
- You want a visual builder (Crew Studio) alongside code.
- You need to self-host the framework, or the whole platform on Enterprise.
- You want to start free, up to 50 workflow executions a month.

## When to choose Guild

- You want agents in TypeScript, as instructions only, or as repo agents, not only Python.
- Agents must never see credentials, with rules per action set by admins.
- You want agents to start from Slack, GitHub, a schedule, or an API call without extra wiring.
- You want to share agents and skills publicly on an Agent Hub others can install or fork.

## What CrewAI and Guild are

**CrewAI.** CrewAI models work as a crew: agents with a role, goal, and backstory take tasks in order or under a manager, and Flows wire crews and code together. AMP deploys a crew and gives it an API, app triggers, traces, and roles. The framework is MIT and Python-only, and Enterprise can self-host the whole platform.

**Guild.** Guild runs agents written as instructions, TypeScript, Goose recipes, repo agents, or Python LangGraph. Agents never see credentials: integrations go through a proxy with ALLOW/DENY rules per operation, and agent code runs with no direct network access. Teams share agents on the Agent Hub.

|   | CrewAI | Guild |
| --- | --- | --- |
| Category | Open-source multi-agent framework + enterprise platform | One platform to run and control AI agents |
| License | MIT framework; AMP, Studio, and Factory are commercial | Proprietary platform; CLI published on npm as @guildai/cli |
| Pricing | Basic free (50 workflow executions a month); Enterprise custom | No public price list; plans priced with the Guild team; model usage metered at list price |
| Maturity | Generally available (framework 1.15.35, 2026-11-03) | Generally available |
| Docs | https://docs.crewai.com | https://docs.guild.ai |

## Concept map: CrewAI to Guild

| Concept | CrewAI | Guild | Note |
| --- | --- | --- | --- |
| The agent | Agent (role, goal, backstory, tools, llm) | A Guild agent: Native (PROMPT.md + guild.yaml) for prompt-only agents, TypeScript (agent.ts) for code | Role, goal, and backstory become the agent's instructions. |
| Tasks | Task (description, expected_output, output_pydantic) | A step in run(), or a task.llm call with a zod output schema | Typed task output maps to a zod schema. |
| A sequential crew | Crew with Process.sequential | A TypeScript agent that calls each step in order |   |
| Delegation | Process.hierarchical / allow_delegation=True | Sub-agents called with guildAgentTool, coordinated by a lead agent |   |
| Flows | Flows (@start, @listen, @router, state) | Deterministic orchestration in a TypeScript run() (task.gather for parallel branches) |   |
| Tools and integrations | crewai-tools, AMP integrations, and apps=[...] | Guild integrations (guildai~github, guildai~slack, …) and guildServiceTool | Check operation names with guild integration operation list <owner~name> --json. |
| MCP servers | mcps=[...] and custom MCP servers on AMP | A custom Guild integration from the MCP server or an OpenAPI spec (guild integration create, Porter) |   |
| Secrets | .env / Secrets Manager (injected as env vars) | Credentials behind the credential proxy, plus credential policies; workspace variables via task.env | The agent never sees the secret. |
| Acting as the user | user_bearer_token at kickoff | Member-scoped credentials and Slack or GitHub identity mapping |   |
| Triggers | AMP triggers (Gmail, Slack, Salesforce, …) and POST /kickoff | guild trigger create (time, integration events, or API) and guild workspace chat --once |   |
| Human input | human_input / @human_feedback | task.ui prompts in the run, or approval gates set in the Guild UI per agent and per action |   |
| Testing | crewai test / crewai train | guild agent test and Guild Evaluations (hasToolCall, toolCallContains, llmJudge) |   |
| Deploying | crewai deploy create / crewai deploy push | guild agent save --wait --publish, then guild workspace agent add |   |
| Traces and cost | Traces and the Agent Control Plane | Sessions and the session event log, Insights, and Spend Explorer |   |
| Skills | Skills (crewai skill publish, org-scoped) | Guild skills on the Hub (guild skill create), public or private |   |

## Feature by feature: CrewAI vs. Guild

### Authoring

| Feature | CrewAI | Guild |
| --- | --- | --- |
| Code-first TypeScript agents | **No.** CrewAI is Python-only (Python >=3.10,<3.14 on PyPI). There is no first-party TypeScript SDK; the only TS port found (crewai-ts) is third-party and unofficial. ([source](https://pypi.org/project/crewai/), checked 2026-11-05) | **Yes.** @guildai/agents-sdk: agent(), llmAgent(), and the task API (task.llm, task.tools, task.ui, task.gather). ([source](https://docs.guild.ai/packages/agents-sdk.md), checked 2026-10-23) |
| Python / LangGraph agents | **Yes.** Agents are written in Python as CrewAI Crews (Agent/Task/Crew) and Flows (@start/@listen/@router). This is not LangGraph; the docs include a migration guide from LangGraph to CrewAI. ([source](https://docs.crewai.com/en/concepts/flows), checked 2026-11-05) | **Yes.** LangGraph agent type: langgraph.json + graph.py using guild_model() and guild_tools(). LangChain v1, Python 3.13, no extra pip packages. ([source](https://docs.guild.ai/guide/agent-types.md), checked 2026-10-23) |
| Instruction-only (no-code) agents | **Yes.** Crew Studio on AMP builds automations from natural language and a visual drag-and-drop canvas, then publishes them as live deployments. Source can be exported as a ZIP, but the export is one-way. ([source](https://docs-platform.crewai.com/platform/en/features/crew-studio.md), checked 2026-11-05) | **Yes.** Native agents: PROMPT.md + guild.yaml, no container, ready immediately. ([source](https://docs.guild.ai/guide/agent-types.md), checked 2026-10-23) |
| Several agent formats on one platform | **Partial.** Several CrewAI-native formats run on one platform: code Crews, Flows (including `crewai create flow --declarative`), YAML-configured crews and Studio-built automations. Agents from other frameworks are not hosted; they are only reachable as tools or over A2A. ([source](https://docs.crewai.com/en/concepts/cli), checked 2026-11-05) | **Yes.** Native, TypeScript, Goose, OpenClaw, and LangGraph agent types, plus ADK (CLI 0.28). ([source](https://docs.guild.ai/guide/agent-types.md), checked 2026-10-23) |
| Typed agent input/output | **Yes.** Tasks declare `output_pydantic` / `output_json` schemas, and Flows can use a typed Pydantic BaseModel state. Deployed automations expose a GET /inputs endpoint listing the required inputs. ([source](https://docs.crewai.com/en/concepts/tasks), checked 2026-11-05) | **Yes.** Zod inputSchema and outputSchema on agent(); root input must be z.object. ([source](https://docs.guild.ai/packages/agents-sdk.md), checked 2026-10-23) |
| Repo / workspace agents (shell, git, files) | **Partial.** Agents can read and write files (FileRead/FileWrite/DirectoryRead tools) and run Python code (`allow_code_execution`, CodeInterpreter in Docker). There is no first-party containerized workspace for shell plus git; that is done through E2B or Daytona sandbox tools. ([source](https://docs.crewai.com/en/learn/coding-agents), checked 2026-11-05) | **Yes.** OpenClaw agents (AGENTS.md + skills/) run in the guildai~lobsterpot container with shell, git, and file editing. ([source](https://docs.guild.ai/guide/agent-types.md), checked 2026-10-23) |
| Sub-agents and agent-to-agent calls | **Yes.** `allow_delegation=True` gives an agent 'Delegate work to coworker' and 'Ask question to coworker' tools, and `Process.hierarchical` adds a manager agent. AMP also exposes A2A endpoints for cross-agent calls. ([source](https://docs.crewai.com/en/concepts/collaboration), checked 2026-11-05) | **Yes.** guildAgentTool calls owner~agent; Native, Goose, and OpenClaw agents declare sub_agents in guild.yaml. ([source](https://docs.guild.ai/guide/guild-yaml.md), checked 2026-10-23) |

### Tools & integrations

| Feature | CrewAI | Guild |
| --- | --- | --- |
| Managed integrations catalog | **Yes.** AMP has OAuth-connected apps with about 28 documented integrations, including Gmail, Slack, Salesforce, HubSpot, Jira, Notion, Microsoft 365, Stripe and Snowflake. The framework also ships many crewai-tools (search, scraping, databases). The pricing page marks 'Enterprise connectors' as Enterprise-only. ([source](https://docs-platform.crewai.com/platform/en/features/tools-and-integrations.md), checked 2026-11-05) | **Yes.** 37 non-model integrations (GitHub, Slack, Gmail, Linear, Jira, Notion, Zendesk, …) plus 8 model publishers. ([source](https://docs.guild.ai/integrations/overview.md), checked 2026-10-23) |
| Use MCP servers as tools | **Yes.** Agents attach MCP servers through the `mcps=[...]` field over stdio, SSE or streamable HTTP. AMP can register custom MCP servers with token, header or OAuth 2.0 auth, and it handles token refresh. ([source](https://docs.crewai.com/en/mcp/dsl-integration), checked 2026-11-05) | **Yes.** Build custom integrations from MCP servers with guild integration. ([source](https://docs.guild.ai/integrations/overview.md), checked 2026-10-23) |
| Platform exposed over MCP | **Partial.** The pricing page lists 'MCP server export', and the AMP Automations Options menu has 'Export as MCP'. The docs do not explain what the export produces or how to use it. AMP also exposes crews as A2A servers. ([source](https://docs-platform.crewai.com/platform/en/features/automations.md), checked 2026-11-05) | **Yes.** Guild is an MCP server: https://api.guild.ai/mcp (OAuth + PKCE) or local `guild mcp`. ([source](https://docs.guild.ai/api-reference/mcp.md), checked 2026-10-23) |
| Custom APIs from OpenAPI | **No.** No OpenAPI-spec-to-tools import is documented in the framework or AMP docs. Custom tools are written as BaseTool / @tool code or reached through MCP. ([source](https://docs.crewai.com/en/concepts/tools), checked 2026-11-05) | **Yes.** guild integration builds tools from OpenAPI specs; Porter drafts integrations from public APIs. ([source](https://docs.guild.ai/integrations/overview.md), checked 2026-10-23) |
| Secrets never reach the agent | **Partial.** AMP stores OAuth tokens for integrations, and its Secrets Manager (Beta) pulls from AWS Secrets Manager, GCP Secret Manager or Azure Key Vault without keeping plaintext. Those secrets are still injected as environment variables into the automation process, so agent code can read them. ([source](https://docs-platform.crewai.com/platform/en/features/secrets-manager/overview.md), checked 2026-11-05) | **Yes.** A credential proxy injects auth server-side; GitHub uses short-lived GitHub App tokens. ([source](https://docs.guild.ai/platform/credentials.md), checked 2026-10-23) |
| Per-operation credential policies | **Partial.** You can limit which actions an integration exposes, in code (`apps=['gmail/fetch_emails']`) or per deployment in service settings. RBAC can also restrict access to env vars and LLM connections. There is no documented allow/deny policy engine per credential. ([source](https://docs-platform.crewai.com/platform/en/features/tools-and-integrations.md), checked 2026-11-05) | **Yes.** ALLOW/DENY rules by operation, resource, agent, and workspace; DENY wins. ([source](https://docs.guild.ai/platform/credential-policies.md), checked 2026-10-23) |
| Act as the invoking user | **Yes.** Passing `user_bearer_token` at kickoff scopes integration auth to the requesting user. Without it, the deployment falls back to its default bearer token. ([source](https://docs-platform.crewai.com/platform/en/features/tools-and-integrations.md), checked 2026-11-05) | **Yes.** Member-scoped credentials plus identity mapping for Slack and GitHub users. ([source](https://docs.guild.ai/platform/credentials.md), checked 2026-10-23) |

### Runtime & triggers

| Feature | CrewAI | Guild |
| --- | --- | --- |
| Managed hosted runtime | **Yes.** AMP deploys crews and flows from GitHub, a ZIP upload, Studio or the CLI to managed infrastructure. Each deployment gets an HTTPS endpoint and a bearer token. ([source](https://docs-platform.crewai.com/platform/en/guides/deploy-to-amp.md), checked 2026-11-05) | **Yes.** Guild hosts and runs all agent types. ([source](https://docs.guild.ai/platform/security-architecture.md), checked 2026-10-23) |
| Self-host option | **Yes.** The MIT framework runs anywhere. The full platform can be self-hosted as CrewAI Factory (Enterprise, sales-led) via Helm on EKS/AKS/GKE/OpenShift or in AWS/Azure VPCs. The pricing page offers 'your own VPC, or your own infrastructure'. ([source](https://blog.crewai.com/unlocking-agent-native-transformation-with-crewai-factory-and-nvidia/), checked 2026-11-05) | **No.** Hosted only; no self-host option documented. ([source](https://docs.guild.ai/platform/security-architecture.md), checked 2026-10-23) |
| Sandboxed, network-controlled execution | **Via integration.** CodeInterpreterTool runs code in Docker, falls back to a restricted Python sandbox, and has an unsafe host mode. No network controls are documented. The docs point to E2B, Modal or Daytona sandbox tools for real isolation. ([source](https://docs.crewai.com/en/tools/ai-ml/codeinterpretertool), checked 2026-11-05) | **Yes.** Containers lose network access before the agent runs; only Guild proxies can reach out. ([source](https://docs.guild.ai/platform/security-architecture.md), checked 2026-10-23) |
| Durable long-running runs | **Partial.** Flows can persist state with `@persist` (SQLite by default), checkpoint and resume runs while skipping completed tasks, and pause on `@human_feedback` for later `resume()`. AMP adds a POST /resume endpoint. None of this is a durable-execution engine with documented crash guarantees. ([source](https://docs.crewai.com/en/concepts/checkpointing), checked 2026-11-05) | **Partial.** Multi-turn sessions; they can be interrupted but not resumed. ([source](https://docs.guild.ai/llms.txt), checked 2026-10-23) |
| Schedules (cron) | **Partial.** The pricing page lists 'cron scheduling' in both tiers, but no AMP doc page describes it. The documented pattern is an external scheduler (ActivePieces, Zapier, Make) calling the kickoff endpoint. ([source](https://www.crewai.com/pricing), checked 2026-11-05) | **Partial.** CLI supports --frequency CRON --cron-expression; docs list hourly–monthly presets. ([source](https://docs.guild.ai/platform/triggers.md), checked 2026-10-23) |
| Webhook, event & API triggers | **Yes.** Every deployment has a REST API (GET /inputs, POST /kickoff, GET /status/{id}, POST /resume). App triggers cover Gmail, Outlook, Drive, Slack, Teams, HubSpot, Salesforce and Zapier, and outbound step/task/crew webhooks report progress. ([source](https://docs-platform.crewai.com/platform/en/guides/automation-triggers.md), checked 2026-11-05) | **Yes.** Event triggers (Slack mention, GitHub PR, Zendesk ticket, …) and API triggers. ([source](https://docs.guild.ai/platform/triggers.md), checked 2026-10-23) |
| Chat channels (Slack, Teams, …) | **Yes.** Slack and Microsoft Teams triggers are available, and the pricing page lists 'workflow chat (UI and Slack/Teams)'. Framework Channels run a Crew or Flow as a Slack or Teams bot through CopilotKit; Discord, Telegram and WhatsApp need self-run adapters. ([source](https://docs.crewai.com/en/guides/frontend/channels), checked 2026-11-05) | **Yes.** Slack event triggers; Discord, Telegram, and Twilio integrations. ([source](https://docs.guild.ai/integrations/overview.md), checked 2026-10-23) |

### Control & governance

| Feature | CrewAI | Guild |
| --- | --- | --- |
| Per-tool-call approval gate | **Partial.** A PRE_TOOL_CALL hook can gate a tool call with `request_human_input` (console) and block it with `HookAborted`, but this is custom code. AMP's built-in human-in-the-loop (HITL) works at the task or Flow-step level (`human_input`, `@human_feedback` with email routing), not per tool call. ([source](https://docs.crewai.com/en/learn/tool-hooks), checked 2026-11-05) | **Yes.** Approval gates are set in the Guild UI, per agent and per action: when the agent reaches a gated action, the run pauses until a designated human approves. No code needed. ([source](https://www.guild.ai/product/ai-governance), checked 2026-10-23) |
| Roles & access control | **Yes.** AMP has Owner, Member and custom roles with feature-level permissions. Entity-level permissions cover automations (run, traces, manage_settings, human_in_the_loop), env vars, LLM connections and Git repos. The pricing page marks it Enterprise-only. ([source](https://docs-platform.crewai.com/platform/en/features/rbac.md), checked 2026-11-05) | **Partial.** Admin and Member org roles, restricted workspaces, and scoped API keys. ([source](https://docs.guild.ai/llms.txt), checked 2026-10-23) |
| Audit log | **Partial.** The AMP launch post claims 'RBAC + audit logs', but no docs page describes an audit log's scope, retention or export. Only execution traces, logs and deployment history are documented. ([source](https://blog.crewai.com/crewai-amp-the-agent-management-platform/), checked 2026-11-05) | **Yes.** Immutable, CSV-exportable audit log (admins). ([source](https://docs.guild.ai/llms.txt), checked 2026-10-23) |
| Runtime guardrails & scanning | **Yes.** Tasks accept function guardrails and natural-language LLM guardrails (`guardrail` / `guardrails`). AMP adds a Hallucination Guardrail and PII redaction policies; the PII redaction applies to traces only and needs Enterprise. ([source](https://docs-platform.crewai.com/platform/en/features/hallucination-guardrail.md), checked 2026-11-05) | **No.** No prompt or tool-call scanning documented; isolation comes from the network-less runtime and credential policies. ([source](https://docs.guild.ai/platform/security-architecture.md), checked 2026-10-23) |
| Spend budgets & usage limits | **Partial.** Agent Control Plane Cost Limit policies (Beta) send email alerts per automation on a daily, weekly or monthly USD threshold. The docs say they 'never pause, throttle, or stop a run'. Only rate limiting (`max_rpm`) is enforced. ([source](https://docs-platform.crewai.com/platform/en/features/agent-control-plane/policies.md), checked 2026-11-05) | **Yes.** Per-agent and per-workspace spend budgets, model allowlists, and daily token limits. ([source](https://docs.guild.ai/llms.txt), checked 2026-10-23) |
| Multi-provider models with fallbacks | **Partial.** Native SDKs cover OpenAI, Anthropic, Gemini, Azure, Bedrock and Snowflake Cortex, other providers go through LiteLLM, and models can be set per agent. Built-in model fallbacks are not documented; only retries are. ([source](https://docs.crewai.com/en/concepts/llms), checked 2026-11-05) | **Yes.** guild.yaml models is an ordered fallback list across Anthropic, OpenAI, Gemini, Meta, DeepSeek, and more; BYO keys supported. ([source](https://docs.guild.ai/guide/guild-yaml.md), checked 2026-10-23) |

### Observability

| Feature | CrewAI | Guild |
| --- | --- | --- |
| Run traces | **Yes.** AMP traces record agent reasoning, tasks, tool calls, tokens, timing and cost, and `crewai traces enable` turns tracing on locally. There is OpenTelemetry export and documented integrations with Langfuse, Datadog, Arize, MLflow, Weave and others. ([source](https://docs-platform.crewai.com/platform/en/features/traces.md), checked 2026-11-05) | **Yes.** Session event log of LLM calls, tool calls, sub-tasks, and container logs; also via the API. ([source](https://docs.guild.ai/llms.txt), checked 2026-10-23) |
| Evaluations | **Partial.** `crewai test` runs a crew N times and prints a table of 1-10 task scores; the docs say OpenAI is the only provider available. `crewai train` collects human feedback. Deeper evals rely on third parties such as Patronus, Braintrust or Opik. ([source](https://docs.crewai.com/en/concepts/testing), checked 2026-11-05) | **Partial.** Evaluations with samples, checks, and llmJudge; enabled per account, no CLI command yet. ([source](https://docs.guild.ai/platform/evaluations.md), checked 2026-10-23) |
| Cost & usage tracking | **Yes.** Traces show total tokens and an estimated cost. The Agent Control Plane tracks LLM tokens and cost per automation, provider and model against the previous period. ([source](https://docs-platform.crewai.com/platform/en/features/agent-control-plane/overview.md), checked 2026-11-05) | **Yes.** Insights and Spend Explorer. ([source](https://docs.guild.ai/llms.txt), checked 2026-10-23) |

### Ecosystem & business

| Feature | CrewAI | Guild |
| --- | --- | --- |
| Public agent hub (install & fork) | **Partial.** Custom tools can be published to all CrewAI users with `crewai tool publish --public`. The Marketplace is a curated catalog of approved assets and downloadable templates. Agent Repositories and Skills are org-scoped, so there is no public hub for installing and forking agents. ([source](https://docs-platform.crewai.com/platform/en/guides/tool-repository.md), checked 2026-11-05) | **Yes.** Agent Hub: Draft, Internal, or Public; owner~name with semver; install and fork (guild agent init --fork). ([source](https://docs.guild.ai/platform/publish-to-agent-hub.md), checked 2026-10-23) |
| Reusable skills | **Yes.** Skills are SKILL.md packages (YAML frontmatter plus markdown) that an agent loads on demand when the description matches. They are managed with `crewai create skill`, `crewai skill publish`, `crewai skill search` and `crewai skill install @org-uuid/name`, and published skills are always org-scoped. ([source](https://docs.crewai.com/en/concepts/skills), checked 2026-11-05) | **Yes.** Hub skills, `guild skill`, and skills inside Goose and OpenClaw agents. ([source](https://docs.guild.ai/cli/commands.md), checked 2026-10-23) |
| Full lifecycle CLI | **Yes.** The `crewai` CLI covers create, install, run, chat, train, test, replay, reset-memories, login, org, deploy create/push/status/logs/list/remove, tool and skill publish/install, traces, triggers run and config. ([source](https://docs.crewai.com/en/concepts/cli), checked 2026-11-05) | **Yes.** 17 top-level commands: init, test, save --publish, workspace chat, trigger, integration, skill, session, and more. ([source](https://docs.guild.ai/cli/commands.md), checked 2026-10-23) |
| Open-source core | **Yes.** The core framework is MIT-licensed on GitHub (about 60.5k stars). AMP, Studio and Factory are commercial. ([source](https://github.com/crewAIInc/crewAI), checked 2026-11-05) | **No.** Proprietary platform; the CLI is published on npm. ([source](https://docs.guild.ai/llms.txt), checked 2026-10-23) |
| Public pricing | **Partial.** The free Basic tier (50 executions/month) is public. Enterprise is 'Custom' with no listed price, and the pricing page shows no paid self-serve tier. ([source](https://www.crewai.com/pricing), checked 2026-11-05) | **Partial.** No public price list: plans are priced with the Guild team; model usage is metered at list price. ([source](https://docs.guild.ai/reference/pricing.md), checked 2026-10-23) |

## Frequently asked questions

### Does Guild run CrewAI crews?

Not as-is. Guild hosts Native, TypeScript, Goose, OpenClaw, and LangGraph agents. A crew moves to Guild by rewriting it in one of those formats: prompt-only crews become Native agents, and crews with code or several steps become TypeScript agents.

### How do I move a CrewAI crew to Guild?

Turn each agent's role, goal, and backstory into instructions, each Task into a step or typed LLM call, and delegation into sub-agents called with guildAgentTool. Replace crewai-tools and AMP integrations with Guild integrations, move .env secrets into Guild credentials, and recreate AMP triggers with guild trigger create. Test with guild agent test before you publish. Use the concept map above as the checklist.

### Can I self-host CrewAI or Guild?

The CrewAI framework runs anywhere under MIT, and the full AMP platform can be self-hosted as CrewAI Factory on Enterprise. Guild is hosted only.

### What doesn't map 1:1?

Crew Studio's visual canvas, hierarchical crews with an automatic manager agent, and self-hosting. On Guild you write the orchestration in a TypeScript run() or split the work across sub-agents.

### Is CrewAI pricing public?

Partly. Basic is free with 50 workflow executions a month; Enterprise is custom pricing.

## Sources

- [pypi.org/project/crewai](https://pypi.org/project/crewai/)
- [docs.crewai.com/en/concepts/flows](https://docs.crewai.com/en/concepts/flows)
- [docs-platform.crewai.com/platform/en/features/crew-studio](https://docs-platform.crewai.com/platform/en/features/crew-studio.md)
- [docs.crewai.com/en/concepts/cli](https://docs.crewai.com/en/concepts/cli)
- [docs.crewai.com/en/concepts/tasks](https://docs.crewai.com/en/concepts/tasks)
- [docs.crewai.com/en/learn/coding-agents](https://docs.crewai.com/en/learn/coding-agents)
- [docs.crewai.com/en/concepts/collaboration](https://docs.crewai.com/en/concepts/collaboration)
- [docs-platform.crewai.com/platform/en/features/tools-and-integrations](https://docs-platform.crewai.com/platform/en/features/tools-and-integrations.md)
- [docs.crewai.com/en/mcp/dsl-integration](https://docs.crewai.com/en/mcp/dsl-integration)
- [docs-platform.crewai.com/platform/en/features/automations](https://docs-platform.crewai.com/platform/en/features/automations.md)
- [docs.crewai.com/en/concepts/tools](https://docs.crewai.com/en/concepts/tools)
- [docs-platform.crewai.com/platform/en/features/secrets-manager/overview](https://docs-platform.crewai.com/platform/en/features/secrets-manager/overview.md)
- [docs-platform.crewai.com/platform/en/guides/deploy-to-amp](https://docs-platform.crewai.com/platform/en/guides/deploy-to-amp.md)
- [blog.crewai.com/unlocking-agent-native-transformation-with-crewai-factory-and-nvidia](https://blog.crewai.com/unlocking-agent-native-transformation-with-crewai-factory-and-nvidia/)
- [docs.crewai.com/en/tools/ai-ml/codeinterpretertool](https://docs.crewai.com/en/tools/ai-ml/codeinterpretertool)
- [docs.crewai.com/en/concepts/checkpointing](https://docs.crewai.com/en/concepts/checkpointing)
- [crewai.com/pricing](https://www.crewai.com/pricing)
- [docs-platform.crewai.com/platform/en/guides/automation-triggers](https://docs-platform.crewai.com/platform/en/guides/automation-triggers.md)
- [docs.crewai.com/en/guides/frontend/channels](https://docs.crewai.com/en/guides/frontend/channels)
- [docs.crewai.com/en/learn/tool-hooks](https://docs.crewai.com/en/learn/tool-hooks)
- [docs-platform.crewai.com/platform/en/features/rbac](https://docs-platform.crewai.com/platform/en/features/rbac.md)
- [blog.crewai.com/crewai-amp-the-agent-management-platform](https://blog.crewai.com/crewai-amp-the-agent-management-platform/)
- [docs-platform.crewai.com/platform/en/features/hallucination-guardrail](https://docs-platform.crewai.com/platform/en/features/hallucination-guardrail.md)
- [docs-platform.crewai.com/platform/en/features/agent-control-plane/policies](https://docs-platform.crewai.com/platform/en/features/agent-control-plane/policies.md)
- [docs.crewai.com/en/concepts/llms](https://docs.crewai.com/en/concepts/llms)
- [docs-platform.crewai.com/platform/en/features/traces](https://docs-platform.crewai.com/platform/en/features/traces.md)
- [docs.crewai.com/en/concepts/testing](https://docs.crewai.com/en/concepts/testing)
- [docs-platform.crewai.com/platform/en/features/agent-control-plane/overview](https://docs-platform.crewai.com/platform/en/features/agent-control-plane/overview.md)
- [docs-platform.crewai.com/platform/en/guides/tool-repository](https://docs-platform.crewai.com/platform/en/guides/tool-repository.md)
- [docs.crewai.com/en/concepts/skills](https://docs.crewai.com/en/concepts/skills)
- [github.com/crewAIInc/crewAI](https://github.com/crewAIInc/crewAI)
- [docs.guild.ai/packages/agents-sdk](https://docs.guild.ai/packages/agents-sdk.md)
- [docs.guild.ai/guide/agent-types](https://docs.guild.ai/guide/agent-types.md)
- [docs.guild.ai/guide/guild-yaml](https://docs.guild.ai/guide/guild-yaml.md)
- [docs.guild.ai/integrations/overview](https://docs.guild.ai/integrations/overview.md)
- [docs.guild.ai/api-reference/mcp](https://docs.guild.ai/api-reference/mcp.md)
- [docs.guild.ai/platform/credentials](https://docs.guild.ai/platform/credentials.md)
- [docs.guild.ai/platform/credential-policies](https://docs.guild.ai/platform/credential-policies.md)
- [docs.guild.ai/platform/security-architecture](https://docs.guild.ai/platform/security-architecture.md)
- [docs.guild.ai/llms.txt](https://docs.guild.ai/llms.txt)
- [docs.guild.ai/platform/triggers](https://docs.guild.ai/platform/triggers.md)
- [guild.ai/product/ai-governance](https://www.guild.ai/product/ai-governance)
- [docs.guild.ai/platform/evaluations](https://docs.guild.ai/platform/evaluations.md)
- [docs.guild.ai/platform/publish-to-agent-hub](https://docs.guild.ai/platform/publish-to-agent-hub.md)
- [docs.guild.ai/cli/commands](https://docs.guild.ai/cli/commands.md)
- [docs.guild.ai/reference/pricing](https://docs.guild.ai/reference/pricing.md)

## Other comparisons

- [Guild vs. Claude Managed Agents](https://www.guild.ai/compare/claude-managed-agents)
- [Guild vs. AWS](https://www.guild.ai/compare/aws)
- [Guild vs. LangChain](https://www.guild.ai/compare/langchain)
- [Guild vs. Runlayer](https://www.guild.ai/compare/runlayer)
- [Guild vs. Arcade](https://www.guild.ai/compare/arcade)
- [Guild vs. Vercel eve](https://www.guild.ai/compare/vercel-eve)
- [Guild vs. OpenAI Agents API](https://www.guild.ai/compare/openai-agents-api)
- [Guild vs. Cursor Agent SDK](https://www.guild.ai/compare/cursor)
- [All comparisons](https://www.guild.ai/compare)
- [Book a demo](https://www.guild.ai/talk-to-sales)