Skip to content
Talk to Us

Blocks.ai publishes this comparison and sells in this market. Every claim about another product links to a public source.

CrewAI AMP vs LangSmith

CrewAI AMP

Platform for deploying, monitoring, and scaling CrewAI crews and agents

LangSmith

Platform for observing, evaluating, and deploying agents

Short answer

Both are platforms to build, deploy, and monitor agents: CrewAI AMP deploys CrewAI crews and flows, while LangSmith Deployment runs agents from several frameworks, CrewAI included.⁠Source 1, Source 2, Source 3, Source 4, Source 5 Both have free plans; AMP’s Enterprise plan is custom-priced, and LangSmith’s Plus plan, which adds Cloud deployments, is $39 per seat a month, with usage metered in $1 units.⁠Source 6, Source 7, Source 8

By Blocks.ai teamLast checked

Where each one sits

Six layers of running AI agents at a company, and what each product’s own public sources say it covers.

Public sources · checked 2 October 2026
  • Offered
  • Preview
  • Not publicly documented

CrewAI AMP

  • Build agents: OfferedCrew Studio visual editor⁠Source 9
  • Host and run agents: OfferedManaged infrastructure for crews⁠Source 1
  • Identity and access: OfferedPer-deployment allow lists⁠Source 10
  • Registry and governance: OfferedAgent Repositories⁠Source 11
  • Traffic between agents, tools, and models: OfferedCustom MCP server connections⁠Source 12
  • Agents across organizations: PreviewPublic A2A agents⁠Source 13

LangSmith

  • Build agents: OfferedFleet agent builder⁠Source 4
  • Host and run agents: OfferedLangSmith Deployment runtime⁠Source 8
  • Identity and access: OfferedFleet per-agent permissions⁠Source 14
  • Registry and governance: OfferedCentralized registry in Deployment⁠Source 15
  • Traffic between agents, tools, and models: OfferedFleet forwards MCP tool calls⁠Source 16
  • Agents across organizations: Not publicly documented

At a glance

TopicCrewAI AMPLangSmith
What it isCrewAI’s platform for deploying, monitoring, and scaling crews and agents in production, extending its open-source framework.⁠Source 1LangChain calls it a platform for observing, evaluating, and deploying agents, with Fleet for creating agents without code.⁠Source 3, Source 4
Agents it deploysCrewAI Crews and Flows.⁠Source 2 AMP’s docs don’t describe deploying agents built with other frameworks.Deep Agents, LangChain, and LangGraph agents, plus others such as Google ADK, Strands, CrewAI, and AutoGen through a wrapper or the LangGraph Functional API.⁠Source 5
Where it runsOn managed infrastructure.⁠Source 1 The Enterprise plan can run on CrewAI’s cloud, your own VPC, or your own infrastructure.⁠Source 6LangChain’s cloud, where deployments need the Plus plan or above, or, on the Enterprise plan, BYOC on AWS, self-hosted, or hybrid.⁠Source 7, Source 8, Source 17, Source 18, Source 19
Access controlThe Enterprise plan lists role-based access control and SSO.⁠Source 6 Role-based access can make a deployment private to allow-listed users and roles.⁠Source 10Hosted agents take LangSmith API keys by default, or your own auth handlers.⁠Source 20 Role-based access control is an Enterprise feature.⁠Source 21
PricingBasic is free, with 50 workflow executions a month.⁠Source 6 Enterprise is custom-priced.⁠Source 6Developer has one free seat; Plus is $39 per seat a month; Enterprise is through sales.⁠Source 7 Usage is metered in LSUs at $1 each.⁠Source 7

What each one is

CrewAI AMP

CrewAI AMP is CrewAI’s platform for deploying, monitoring, and scaling crews and agents in production, extending its open-source framework.⁠Source 1 Teams build crews in code, or in Crew Studio with natural language and a visual editor.⁠Source 1, Source 9 CrewAI’s October 2025 launch post called it CrewAI AOP.⁠Source 22

LangSmith

LangChain describes LangSmith as a framework-agnostic platform for observing, evaluating, and deploying agents.⁠Source 3 LangSmith Deployment runs agents in production, and LangSmith Fleet creates and manages agents without code; LangChain positions Fleet for non-technical teams.⁠Source 3, Source 4, Source 8 Agents hosted elsewhere can send traces to LangSmith.⁠Source 19

The differences that matter

  1. Which agents each one runs

    CrewAI AMP

    AMP deploys CrewAI Crews and Flows as automations.⁠Source 2 AMP’s docs don’t describe deploying agents built with other frameworks.

    LangSmith

    LangSmith Deployment runs agents from other frameworks too, such as Google ADK, Strands, CrewAI, and AutoGen, via a wrapper package or the LangGraph Functional API.⁠Source 5

    AMP can export OpenTelemetry traces to your own collector.⁠Source 23 Agents LangSmith doesn’t host can still send it traces, and the CrewAI framework is among its tracing integrations.⁠Source 19, Source 24

  2. Building agents without code

    CrewAI AMP

    In Crew Studio, you create automations from natural language and a visual workflow editor; you first configure an LLM connection with your own API key.⁠Source 9, Source 25

    LangSmith

    Fleet builds an agent from a description or a template, on managed model tiers that need no model-provider API key of your own.⁠Source 4, Source 26

    Both export to code: Crew Studio source downloads as a ZIP, and Fleet agents export to code via Deep Agents, the open-source runtime Fleet runs on.⁠Source 9, Source 14

  3. Controls for admins

    CrewAI AMP

    On Enterprise, custom roles can set most features to Manage, Read, or No access, and PII in execution traces can be masked.⁠Source 6, Source 10, Source 27

    LangSmith

    On Enterprise, admins can create custom roles, and audit logs record administrative and configuration actions, kept up to 400 days.⁠Source 21, Source 28

    Fleet also has per-agent Clone, Run, and Edit sharing permissions.⁠Source 14 Both can pause for a person: AMP flows at review points, Fleet agents before specific actions.⁠Source 29, Source 30

For security teams

What a security review asks, answered from each vendor’s public documentation.

TopicCrewAI AMPLangSmith
Network exposureOn Enterprise, AMP can run in your own VPC.⁠Source 6 Custom MCP servers it connects to must be internet-reachable.⁠Source 12Enterprise customers can reach LangSmith Cloud over AWS PrivateLink or GCP Private Service Connect, off the public internet.⁠Source 17
IdentityEnterprise lists role-based access control and SSO with Microsoft Entra or Okta.⁠Source 6 Per-agent identity is not publicly documented.Fleet agents can use fixed credentials or the user’s own.⁠Source 31 Cloud Enterprise customers can configure SAML SSO and SCIM.⁠Source 32
Access changes and revocationOn Enterprise, a role permission allows deleting an automation.⁠Source 6, Source 10 Revoking a Platform API service account (beta) disables it immediately.⁠Source 33, Source 34Fleet sharing can be revoked at any time.⁠Source 30 Admins can deactivate any member’s access token, effective within a minute.⁠Source 35
Audit trailExecution traces, exportable to your own OpenTelemetry collector.⁠Source 23, Source 36 AMP’s docs don’t describe a platform-wide audit log of admin events.Enterprise audit logs of admin actions, kept up to 400 days; your hourly job can forward them to a SIEM.⁠Source 28
ComplianceCrewAI says it maintains a SOC 2 Type 2 certified security program.⁠Source 37LangChain’s Trust Center lists SOC 2 Type II, ISO 27001:2022, GDPR, and HIPAA for LangSmith.⁠Source 38

Full comparison

18 criteria in five groups. Every cell links to its source, or says no public source answers it.

CrewAI AMP and LangSmith compared on 18 criteria
CrewAI AMPLangSmith
What it is
What it is and who it’s forCrewAI’s platform for deploying, monitoring, and scaling crews and agents in production.⁠Source 1 It extends CrewAI’s open-source framework.⁠Source 1LangChain calls it a framework-agnostic platform for observing, evaluating, and deploying agents.⁠Source 3 It positions its no-code part, Fleet, for non-technical teams.⁠Source 3, Source 4
MaturityCrewAI’s platform took the AMP name in October 2025.⁠Source 22, Source 39 The Platform API is in beta.⁠Source 34LangChain announced GA of LangGraph Platform (now Deployment) on 14 May 2025 and Agent Builder (now Fleet) on 13 January 2026.⁠Source 15, Source 40, Source 41, Source 42
Control
Agent registry and discoveryAgent Repositories, on both plans, share agent definitions.⁠Source 6, Source 11 Automations is the hub for deployed crews.⁠Source 43 Listing non-CrewAI agents: not publicly documented.LangChain says Deployment manages agents in a centralized registry with versioning and rollbacks.⁠Source 15, Source 44 Listing agents hosted elsewhere is not publicly documented.
Identity and access controlEnterprise lists role-based access control, which can make a deployment private to allow-listed users and roles, and SSO with Microsoft Entra or Okta.⁠Source 6, Source 10Hosted agents use LangSmith API keys by default, or your auth handlers.⁠Source 20 Fleet has per-agent Clone, Run, and Edit permissions.⁠Source 14 RBAC is Enterprise.⁠Source 21
Ownership, policy, and revocationOn Enterprise, custom roles can set most features to Manage, Read, or No access.⁠Source 6, Source 10 On both plans, flows can pause for human review.⁠Source 6, Source 29Fleet agent cards show the owner, sharing can be revoked at any time, and pausing an agent’s channels pauses it.⁠Source 30, Source 42, Source 45 Fleet has spend limits.⁠Source 46
Audit log and observabilityExecution traces from inputs to outputs, with OpenTelemetry export to your own collector.⁠Source 23, Source 36 AMP’s docs don’t describe a platform-wide audit log of admin events.Enterprise audit logs of admin and configuration actions, kept up to 400 days.⁠Source 28 Each deployment gets a tracing project.⁠Source 47
Connection
How agents connectCrews run on managed infrastructure, and a crew’s API is protected by a bearer token.⁠Source 1, Source 48 Custom MCP servers must be reachable from the internet.⁠Source 12On self-hosted LangSmith with Deployment, agents run behind an ingress you configure.⁠Source 49 Enterprise can reach LangSmith Cloud over AWS PrivateLink.⁠Source 17
Agents across organizationsCrewAI agents can call remote A2A agents; AMP’s A2A server agents are in preview.⁠Source 13, Source 50 An access model for another organization’s agents is not publicly documented.Agent Server agents can talk to other A2A-compatible agents.⁠Source 51 An access model for another organization’s agents is not publicly documented.
Protocol supportA2A server agents on AMP, in preview, serve REST and JSON-RPC, with gRPC if enabled.⁠Source 13 AMP can connect to MCP servers and offers Export as MCP.⁠Source 12, Source 43Agent Server supports A2A over JSON-RPC only, with documented gaps, and can expose agents as MCP tools.⁠Source 51, Source 52 Fleet discovers tools from remote MCP servers.⁠Source 16
Frameworks, models, and clouds supportedDeploys CrewAI Crews and Flows.⁠Source 2 Crew Studio source downloads as a ZIP for work in code.⁠Source 9 AMP’s docs don’t describe deploying other frameworks’ agents.Deployment runs Google ADK, Claude Agent SDK, Strands, CrewAI, and AutoGen agents via a wrapper package or the LangGraph Functional API.⁠Source 5
Operations
Deployment options and data residencyThe Enterprise plan can run on CrewAI’s cloud, your own VPC, or your own infrastructure.⁠Source 6 Data residency commitments are not publicly documented.Cloud on GCP (US, EU, APAC) or AWS (US).⁠Source 17 On Enterprise: BYOC (GA on AWS), self-hosted, or hybrid.⁠Source 7, Source 18, Source 19 Moving between Cloud regions isn’t supported.⁠Source 53
Compliance attestationsCrewAI says it maintains a SOC 2 Type 2 certified security program.⁠Source 37 Its trust center lists a HIPAA audit report from February 2026.⁠Source 37LangChain’s Trust Center lists SOC 2 Type II, ISO 27001:2022, GDPR, and HIPAA, with a 2026 SOC 2 Type II report and ISO 27001 certificate.⁠Source 38
Support and SLACommunity support on both plans; dedicated and Slack or Teams support on Enterprise.⁠Source 6 An uptime SLA is not publicly documented.Base, Standard, and Premium support plans.⁠Source 54 Reasonable commercial efforts toward 99.5% API uptime for SaaS, measured quarterly.⁠Source 54
Time and effort to get runningThe deploy guide starts from a crew that runs locally; CrewAI says a first deployment typically takes around a minute.⁠Source 48 Enterprise includes a 45-day onboarding.⁠Source 6Cloud deployment needs Plus or above and an API key.⁠Source 55 Self-hosting the Deployment control plane needs Kubernetes and Enterprise.⁠Source 8
Pricing model and public pricesBasic is free, with 50 workflow executions a month.⁠Source 6 Enterprise is custom-priced.⁠Source 6Developer: free, one seat.⁠Source 7 Plus: $39 per seat a month, with one free small serverless deployment.⁠Source 7 Enterprise: contact sales.⁠Source 7 Usage is metered in LSUs, $1 each.⁠Source 7
Building
Agent building toolsBuild crews in code or in Crew Studio, an AI-assisted workspace that uses natural language and a visual workflow editor.⁠Source 1, Source 9Fleet builds agents from a description or a template, without code.⁠Source 4 Code-first agents can be deployed with the LangGraph CLI and app templates.⁠Source 8
Model accessCrewAI’s docs say any LLM provider CrewAI supports can be used, with your own API key; the Crew Studio setup guide lists OpenAI or Azure.⁠Source 25Fleet’s managed tiers (Fast, Pro, Max) need no model-provider key of your own; custom models aren’t in that picker.⁠Source 26 LangChain says closed or open models work.⁠Source 3
Integrations and ecosystemCrewAI says Crew Studio can connect to more than 1,000 applications.⁠Source 56 A Marketplace lists integrations, internal tools, and reusable assets.⁠Source 57Fleet has built-in tools such as Gmail, Slack, and GitHub.⁠Source 26 LangChain says Fleet agents work in Slack, Teams, and Gmail.⁠Source 58

Which to choose

Choose CrewAI AMP if

  • You build with CrewAI and want CrewAI’s own platform to deploy, monitor, and scale crews and flows in production.⁠Source 1, Source 2
  • You want people to build crews without code, by chat or in Crew Studio’s visual workflow editor.⁠Source 9, Source 25, Source 59
  • You want many app connections: CrewAI says Crew Studio can connect to more than 1,000 applications.⁠Source 56
  • You want PII in execution traces detected and masked automatically, on Enterprise.⁠Source 6, Source 27

Choose LangSmith if

  • Your agents use several frameworks: LangSmith Deployment runs LangGraph agents and others, such as Google ADK, Strands, CrewAI, and AutoGen.⁠Source 5
  • You want to trace agents built on many stacks: any OpenTelemetry-compatible app, or integrations such as OpenAI, Anthropic, and CrewAI.⁠Source 24, Source 60
  • You want people to build agents without code, which LangChain positions for non-technical teams, and without their own model API key.⁠Source 3, Source 4, Source 26
  • You want list prices: Plus is $39 per seat a month, and usage is metered in units costing $1 each.⁠Source 7

Questions buyers ask

Can LangSmith run or trace CrewAI crews?

Yes. LangSmith Deployment runs CrewAI agents through the LangGraph Functional API, and LangSmith’s tracing integrations include the CrewAI framework.⁠Source 5, Source 24 AMP itself deploys CrewAI Crews and Flows; its docs don’t describe deploying agents built with other frameworks.⁠Source 2

How is each one priced?

CrewAI’s Basic plan is free with 50 workflow executions a month, and Enterprise is custom-priced.⁠Source 6 LangSmith’s Developer plan has one free seat, Plus is $39 per seat a month, Enterprise is through sales, and usage is metered in LangChain Standard Units, $1 each.⁠Source 7

Can either one be self-hosted?

Both offer it on their Enterprise plans.⁠Source 6, Source 19 CrewAI’s can run on CrewAI’s cloud, your own VPC, or your own infrastructure.⁠Source 6 LangSmith’s offers BYOC, generally available on AWS, or self-hosting in your own Kubernetes cluster, including for air-gapped use.⁠Source 8, Source 18

Do they support A2A and MCP?

CrewAI agents can act as A2A clients and servers; A2A server agents on AMP are in preview.⁠Source 13, Source 50 AMP can connect to MCP servers and offers Export as MCP.⁠Source 12, Source 43 LangSmith’s Agent Server supports A2A over JSON-RPC, with documented gaps, and can expose agents as MCP tools.⁠Source 51, Source 52

How we compare

Read the full method

Every claim on this page links to a public source. Where none answers a question, the page says so.

We re-check every fact at least every 90 days. This page was last checked .

Something wrong or out of date? Tell us and we’ll correct it.

Sources

65 public sources, each with the date we checked it. Every one opens in a new tab.

  1. Source 1: CrewAI AMP (platform docs introduction) CrewAI · checked Back:abcdefghijk

  2. Source 2: Prepare for Deployment CrewAI · checked Back:abcdef

  3. Source 3: LangSmith: The Agent Engineering Platform LangChain · checked Back:abcdefgh

  4. Source 4: No-code agents with LangSmith Fleet LangChain · checked Back:abcdefgh

  5. Source 5: Deploy other frameworks LangChain · checked Back:abcdef

  6. Source 6: Pricing | CrewAI CrewAI · checked Back:abcdefghijklmnopqrstuv

  7. Source 7: LangSmith Plans and Pricing LangChain · checked Back:abcdefghijk

  8. Source 8: LangSmith Deployment LangChain · checked Back:abcdefg

  9. Source 9: Crew Studio CrewAI · checked Back:abcdefg

  10. Source 10: Role-Based Access Control (RBAC) CrewAI · checked Back:abcdef

  11. Source 11: Agent Repositories CrewAI · checked Back:ab

  12. Source 12: Custom MCP Servers CrewAI · checked Back:abcde

  13. Source 13: A2A on AMP CrewAI · checked Back:abcde

  14. Source 14: Agent platform comparison LangChain · checked Back:abcd

  15. Source 15: LangSmith Deployment LangChain · checked Back:abc

  16. Source 16: Remote MCP servers LangChain · checked Back:ab

  17. Source 17: Cloud (SaaS) LangChain · checked Back:abcd

  18. Source 18: Bring Your Own Cloud (BYOC) LangChain · checked Back:abc

  19. Source 19: Set up LangSmith LangChain · checked Back:abcde

  20. Source 20: Authentication & access control LangChain · checked Back:ab

  21. Source 21: Role-based access control LangChain · checked Back:abc

  22. Source 22: CrewAI AMP - The Agent Management Platform CrewAI · checked Back:ab

  23. Source 23: OpenTelemetry Export CrewAI · checked Back:abc

  24. Source 24: LangSmith Observability LangChain · checked Back:abcd

  25. Source 25: Enable Crew Studio CrewAI · checked Back:abc

  26. Source 26: Essentials LangChain · checked Back:abcd

  27. Source 27: PII Redaction for Traces CrewAI · checked Back:ab

  28. Source 28: Audit logs LangChain · checked Back:abc

  29. Source 29: Flow HITL Management CrewAI · checked Back:ab

  30. Source 30: Access & oversight LangChain · checked Back:abc

  31. Source 31: Agent identity LangChain · checked Back to text

  32. Source 32: Authentication methods LangChain · checked Back to text

  33. Source 33: Service accounts CrewAI · checked Back to text

  34. Source 34: Introduction (CrewAI Platform API) CrewAI · checked Back:ab

  35. Source 35: Overview (administration) LangChain · checked Back to text

  36. Source 36: Traces CrewAI · checked Back:ab

  37. Source 37: Trust Center - CrewAI CrewAI · checked Back:abc

  38. Source 38: Trust Center - LangChain LangChain · checked Back:ab

  39. Source 39: Changelog (CrewAI docs) CrewAI · checked Back to text

  40. Source 40: LangGraph Platform is now Generally Available: Deploy & manage long-running, stateful Agents LangChain · checked Back to text

  41. Source 41: Now GA: LangSmith Agent Builder LangChain · checked Back to text

  42. Source 42: LangSmith Fleet changelog LangChain · checked Back:ab

  43. Source 43: Automations CrewAI · checked Back:abc

  44. Source 44: Assistants LangChain · checked Back to text

  45. Source 45: Manage agent settings LangChain · checked Back to text

  46. Source 46: Manage workspace administration LangChain · checked Back to text

  47. Source 47: LangSmith control plane LangChain · checked Back to text

  48. Source 48: Deploy to AMP CrewAI · checked Back:ab

  49. Source 49: Enable additional LangSmith features LangChain · checked Back to text

  50. Source 50: Agent-to-Agent (A2A) Protocol (CrewAI framework docs) CrewAI · checked Back:abc

  51. Source 51: A2A endpoint in Agent Server LangChain · checked Back:abcd

  52. Source 52: MCP endpoint in Agent Server LangChain · checked Back:ab

  53. Source 53: Regions FAQ LangChain · checked Back to text

  54. Source 54: Support Plans LangChain · checked Back:ab

  55. Source 55: Deploy your app to cloud LangChain · checked Back to text

  56. Source 56: Crew Studio: The Automated Agent Builder CrewAI · checked Back:ab

  57. Source 57: Marketplace CrewAI · checked Back to text

  58. Source 58: LangSmith Fleet LangChain · checked Back to text

  59. Source 59: CrewAI agent management platform page CrewAI · checked Back to text

  60. Source 60: Trace with OpenTelemetry LangChain · checked Back to text

  61. Source 61: Why Blocks? Blocks.ai · checked Back:ab

  62. Source 62: What is Blocks? Blocks.ai · checked Back to text

  63. Source 63: Your company's private network Blocks.ai · checked Back to text

  64. Source 64: Network requirements Blocks.ai · checked Back to text

  65. Source 65: Solutions: Agent sprawl Blocks.ai · checked Back to text