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 Workday Agent System of Record

CrewAI AMP

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

Workday Agent System of Record

Workday system of record to find, add, register, configure, monitor, and manage AI agents

Short answer

CrewAI AMP is CrewAI’s platform for building, deploying, and monitoring crews, while Workday Agent System of Record (ASOR), set up in each Workday tenant, registers and manages Workday-built, partner-built, and self-built agents.⁠Source 1, Source 2, Source 3 AMP deploys crews to managed infrastructure; ASOR records where each external agent is hosted and gives each agent a unique Workday identity.⁠Source 1, Source 4, Source 5

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.

These aren’t the same kind of product

Where they overlap
Both keep a catalog of agents and a record of their activity: AMP’s Agent Repositories and execution traces, and ASOR’s Agent Registry and audit trail report.⁠Source 2, Source 6, Source 7, Source 8
Where they differ
AMP builds, deploys, and runs CrewAI crews and flows.⁠Source 1, Source 9, Source 10 ASOR takes external agents’ definitions through an API; for agents that work with Workday, tools are Workday APIs.⁠Source 2
Running both
You register outside agents through ASOR’s API, and CrewAI agents can delegate tasks to remote A2A agents.⁠Source 11, Source 12 Neither vendor publicly documents using the two together.
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 13
  • Registry and governance: OfferedAgent Repositories⁠Source 6
  • Traffic between agents, tools, and models: OfferedCustom MCP server connections⁠Source 14
  • Agents across organizations: PreviewPublic A2A agents⁠Source 15

Workday Agent System of Record

  • Build agents: Not publicly documented
  • Host and run agents: Not publicly documented
  • Identity and access: OfferedAgent System User per agent⁠Source 5
  • Registry and governance: OfferedAgent Registry in Management Hub⁠Source 2
  • Traffic between agents, tools, and models: OfferedAgent Gateway for Workday APIs⁠Source 16
  • Agents across organizations: Not publicly documented

At a glance

TopicCrewAI AMPWorkday Agent System of Record
What it isCrewAI’s platform for deploying, monitoring, and scaling crews and agents in production.⁠Source 1A functional area you enable in each Workday tenant to find, add, register, configure, monitor, and manage AI agents.⁠Source 2, Source 3
Where agents runOn managed infrastructure.⁠Source 1 The Enterprise plan can run on CrewAI’s cloud, your own VPC, or your own infrastructure.⁠Source 17External agents are registered through the ASOR API with the URL where each one is hosted.⁠Source 4, Source 11
Agent identityPer-agent identity is not publicly documented. The Enterprise plan lists SSO with Microsoft Entra or Okta, and role-based access control.⁠Source 17Each agent has a unique Workday identity, using Agent System User accounts governed by Workday security policies and groups.⁠Source 5, Source 18
Pricing modelBasic is free, with 50 workflow executions a month.⁠Source 17 Enterprise is custom-priced.⁠Source 17No additional specific SKU for ASOR.⁠Source 2 Workday-built agents in production need a Flex Credits policy opt-in.⁠Source 2 A credit’s price is not publicly documented.
MaturityCrewAI’s platform took the AMP name in October 2025.⁠Source 19, Source 20Announced in February 2025; generally available since February 2026.⁠Source 21, Source 22

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

Workday Agent System of Record

Workday Agent System of Record (ASOR) is a functional area of a Workday tenant for finding, registering, configuring, monitoring, and managing AI agents.⁠Source 2, Source 3 Workday calls it the single source of truth for a company’s agents, whether Workday, the customer, or a partner built them.⁠Source 22

The differences that matter

  1. Building and hosting agents

    CrewAI AMP

    Teams build crews in code or in Crew Studio, then deploy them to managed infrastructure; Enterprise can also run in your own VPC.⁠Source 1, Source 17

    Workday Agent System of Record

    ASOR takes an external agent’s definition, with its hosting URL, through an API; Workday announced a low-code builder for its separate Workday Build.⁠Source 2, Source 4, Source 23, Source 24

    AMP deploys CrewAI Crews and Flows.⁠Source 10 Its docs don’t describe deploying agents built with other frameworks.

  2. Identity and access

    CrewAI AMP

    On Enterprise, role-based access can make a deployment private to allow-listed users and roles, with SSO through Microsoft Entra or Okta.⁠Source 13, Source 17

    Workday Agent System of Record

    Each agent has a unique Workday identity, and Workday security policies and groups control what it can reach.⁠Source 5, Source 18

    In ASOR’s delegate mode, access is the intersection of the user’s permissions and the agent’s allowed skills.⁠Source 5 AMP integrations can be scoped to a specific user’s account.⁠Source 25

  3. Remote and partner agents

    CrewAI AMP

    CrewAI agents can delegate tasks to remote A2A agents by URL; A2A server agents on AMP, in preview, support six authentication schemes.⁠Source 12, Source 15

    Workday Agent System of Record

    ASOR manages partner-built agents in your tenant; a definition can carry an ID locating the agent in the partner’s system.⁠Source 2, Source 3, Source 4

    Neither is publicly documented: bringing another company’s agents into an AMP organization’s repository or dashboard, or ASOR access controls held by the partner company.

For security teams

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

TopicCrewAI AMPWorkday Agent System of Record
Network exposureA deployed crew’s API requires a bearer token.⁠Source 26, Source 27 Custom MCP servers AMP connects to must be internet-reachable.⁠Source 14Third-party agents call Workday APIs through Agent Gateway’s regional endpoint.⁠Source 16 Whether agents need an inbound endpoint isn’t publicly documented.
IdentityEnterprise lists role-based access control and SSO with Microsoft Entra or Okta.⁠Source 17 Per-agent identity is not publicly documented.Unique Workday identity per agent.⁠Source 5 External agents use OAuth 2.0 or signed JWTs; third-party (self-built) agents’ tokens last 4 hours.⁠Source 5, Source 28
Access changes and revocationOn Enterprise, a role permission allows deleting an automation.⁠Source 13, Source 17 Revoking a Platform API service account (beta) disables it immediately.⁠Source 29, Source 30Deactivating an agent hides it from users; Workday says the change can take up to a minute at Agent Gateway.⁠Source 2, Source 16
Audit trailExecution traces, exportable to your own OpenTelemetry collector.⁠Source 7, Source 31 AMP’s docs don’t describe a platform-wide audit log of admin events.An audit trail report covers agent transactions; delegated actions record both the agent and the user.⁠Source 5, Source 8
ComplianceCrewAI says it maintains a SOC 2 Type 2 certified security program.⁠Source 32Workday says its SOC 2 report covers Workday Enterprise Products; ASOR isn’t named.⁠Source 33

Full comparison

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

CrewAI AMP and Workday Agent System of Record compared on 18 criteria
CrewAI AMPWorkday Agent System of Record
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 1Set up in each Workday tenant to find, register, configure, monitor, and manage AI agents built by Workday, partners, or the customer.⁠Source 2, Source 3
MaturityCrewAI’s platform took the AMP name in October 2025.⁠Source 19, Source 20 The Platform API is in beta.⁠Source 30Announced in February 2025; generally available since February 2026.⁠Source 21, Source 22
Control
Agent registry and discoveryAgent Repositories, on both plans, let an organization store, share, and reuse agent definitions.⁠Source 6, Source 17 Automations is the operations hub for deployed crews.⁠Source 34The Agent Management Hub lists Workday-built, partner-built, and self-built agents with status.⁠Source 2 Some, such as HiredScore and Evisort agents, aren’t in ASOR.⁠Source 2
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 13, Source 17Each agent has a unique Workday identity, governed by security policies and groups.⁠Source 5, Source 18 An Agent Interaction Policy sets who may use its delegate-mode skills.⁠Source 35
Ownership, policy, and revocationOn Enterprise, custom roles can set most features to Manage, Read, or No access.⁠Source 13, Source 17 On both plans, flows can pause for human review.⁠Source 17, Source 36Admins set each agent’s skills and who can use it, and activate or deactivate it.⁠Source 2, Source 18 A deactivated agent is hidden from users and can be reactivated.⁠Source 2
Audit log and observabilityExecution traces from inputs to outputs, with OpenTelemetry export to your own collector.⁠Source 7, Source 31 AMP’s docs don’t describe a platform-wide audit log of admin events.An audit trail report covers agent transactions; delegated actions record the agent and the user.⁠Source 5, Source 8 Per-agent analytics reports cover Workday-built agents only.⁠Source 2
Connection
How agents connectCrews run on managed infrastructure, and a crew’s API is protected by a bearer token.⁠Source 1, Source 27 Custom MCP servers must be reachable from the internet.⁠Source 14Third-party agents reach Workday APIs through Agent Gateway, a single regional endpoint.⁠Source 16 Outbound-only use is not publicly documented.
Agents across organizationsCrewAI agents can delegate tasks to remote A2A agents by URL.⁠Source 12 A2A server agents on AMP, in preview, support six authentication schemes.⁠Source 15ASOR manages partner-built agents; a definition can carry an ID locating each one in the partner’s system.⁠Source 2, Source 4 Partner-held controls are not publicly documented.
Protocol supportCrewAI agents can act as A2A clients and servers; A2A server agents on AMP are in preview.⁠Source 12, Source 15 AMP can connect to MCP servers and offers Export as MCP.⁠Source 14, Source 34API registration is based on the A2A Agent Card.⁠Source 4 Outside assistants can call the Self-Service Agent over A2A, and tool search can filter by SOAP, REST, or MCP.⁠Source 37, Source 38
Frameworks, models, and clouds supportedDeploys CrewAI Crews and Flows.⁠Source 10 Crew Studio source downloads as a ZIP for work in code.⁠Source 9 AMP’s docs don’t describe deploying other frameworks’ agents.Registration records each agent’s platform, or OTHER.⁠Source 4 Workday names the Gemini Enterprise app as an outside assistant able to call its Self-Service Agent.⁠Source 37
Operations
Deployment options and data residencyThe Enterprise plan can run on CrewAI’s cloud, your own VPC, or your own infrastructure.⁠Source 17 Data residency commitments are not publicly documented.Set up in each Workday tenant.⁠Source 3 Agent Gateway has public endpoints in eight regions, including the US and EU.⁠Source 16 A self-hosted option is not publicly documented.
Compliance attestationsCrewAI says it maintains a SOC 2 Type 2 certified security program.⁠Source 32 Its trust center lists a HIPAA audit report from February 2026.⁠Source 32Workday says its SOC 2 report covers Workday Enterprise Products and its ISO 42001 certificate covers Workday Platform; ASOR isn’t named.⁠Source 33
Support and SLACommunity support on both plans; dedicated and Slack or Teams support on Enterprise.⁠Source 17 An uptime SLA is not publicly documented.Workday says its company-wide support is 24/5, with severity 1 cases 24/7/365, or 24/7/365 with Success Plans.⁠Source 39 An ASOR uptime SLA is not publicly documented.
Time and effort to get runningThe deploy guide starts from a crew that already runs locally.⁠Source 27 Crew Studio needs an LLM connection first.⁠Source 40 Enterprise includes a 45-day onboarding.⁠Source 17Enable the ASOR functional area and set its security policies.⁠Source 3 Registering an external agent includes finding the IDs of the Workday APIs it will use.⁠Source 11
Pricing model and public pricesBasic is free, with 50 workflow executions a month.⁠Source 17 Enterprise is custom-priced.⁠Source 17No additional specific SKU for ASOR.⁠Source 2 Workday-built agents in production need a Flex Credits policy opt-in.⁠Source 2 A credit’s price is not publicly documented.
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 9You provide an external agent’s definition through an API.⁠Source 2 Workday announced the low-code Flowise Agent Builder for its separate Workday Build in 2025.⁠Source 23, Source 24
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 40Workday’s AI agents use large language models.⁠Source 2 Which models ASOR supports or includes is not publicly documented.
Integrations and ecosystemCrewAI says Crew Studio can connect to more than 1,000 applications.⁠Source 41 A Marketplace lists integrations, internal tools, and reusable assets.⁠Source 42In February 2026, Workday said more than 65 partners were connecting agents to ASOR.⁠Source 22 Workday says partner agents have been on its Marketplace since June 2025.⁠Source 43

Which to choose

Choose CrewAI AMP if

  • Your teams build with CrewAI and want one platform to deploy, monitor, and scale crews in production.⁠Source 1, Source 10
  • You want people to build crews with or without code, in Crew Studio, from natural language and a visual workflow editor.⁠Source 9, Source 40, Source 44
  • You want somewhere to run your crews: AMP deploys them to managed infrastructure, and Enterprise can run in your own VPC.⁠Source 1, Source 17
  • Your crews work with many apps: CrewAI says Crew Studio can connect to more than 1,000, in CRM, support, messaging, and more.⁠Source 41

Choose Workday Agent System of Record if

  • You already run Workday and want agent governance in the same tenant, with no additional specific SKU to buy for ASOR.⁠Source 2, Source 3
  • You want each agent to have a unique Workday identity, governed by the security policies and groups you already use.⁠Source 5, Source 18
  • You want an agent acting for a user limited to what both may do, with audit entries naming both.⁠Source 5
  • You want Workday-built, partner-built, and self-built agents listed with their status in one Agent Management Hub.⁠Source 2

Questions buyers ask

Can Workday Agent System of Record manage agents built outside Workday?

Yes: the ASOR API defines and registers an external agent in one step, and the Agent Management Hub manages self-built and partner-built agents.⁠Source 2, Source 11 Per-agent analytics reports cover Workday-built agents only, and some, such as HiredScore and Evisort agents, aren’t in ASOR.⁠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 17 ASOR needs no additional specific SKU.⁠Source 2 Workday-built agents in production need a Flex Credits policy opt-in, with complimentary credits to start.⁠Source 2, Source 45 A credit’s price is not publicly documented.

Do CrewAI AMP and Workday Agent System of Record support A2A and MCP?

AMP can connect to MCP servers, and CrewAI agents can act as A2A clients; AMP’s A2A server agents are in preview.⁠Source 12, Source 14, Source 15 Workday bases API registration on A2A Agent Cards, outside assistants can call its Self-Service Agent over A2A, and tool search can filter by MCP.⁠Source 4, Source 37, Source 38

Can either one be self-hosted?

CrewAI’s Enterprise plan can be deployed on CrewAI’s cloud, your own VPC, or your own infrastructure.⁠Source 17 ASOR is set up in each Workday tenant.⁠Source 3 For ASOR, a self-hosted option is not publicly documented.

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

50 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:abcdefghijklmno

  2. Source 2: About Workday Agents (Workday Administrator Guide) Workday · checked Back:abcdefghijklmnopqrstuvwxyz2728

  3. Source 3: Set Up Agent System of Record (Workday Administrator Guide) Workday · checked Back:abcdefghi

  4. Source 4: ASOR API Documentation v1.2 (Workday/asor on GitHub) Workday · checked Back:abcdefghi

  5. Source 5: Concept: Agent Security (Workday Administrator Guide) Workday · checked Back:abcdefghijkl

  6. Source 6: Agent Repositories CrewAI · checked Back:abc

  7. Source 7: Traces CrewAI · checked Back:abc

  8. Source 8: FAQ: Agent Security (Workday Administrator Guide) Workday · checked Back:abc

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

  10. Source 10: Prepare for Deployment CrewAI · checked Back:abcd

  11. Source 11: Register External Agents (Workday Administrator Guide) Workday · checked Back:abcde

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

  13. Source 13: Role-Based Access Control (RBAC) CrewAI · checked Back:abcde

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

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

  16. Source 16: Concept: Workday Agent Gateway (Workday Administrator Guide) Workday · checked Back:abcde

  17. Source 17: Pricing | CrewAI CrewAI · checked Back:abcdefghijklmnopqrst

  18. Source 18: Setup Considerations: Agent Security (Workday Administrator Guide) Workday · checked Back:abcde

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

  20. Source 20: Changelog (CrewAI docs) CrewAI · checked Back:ab

  21. Source 21: The Next Generation of Workforce Management is Here - Workday Unveils New Agent System of Record Workday · checked Back:ab

  22. Source 22: The Workday Agent System of Record Is Now Generally Available Workday · checked Back:abcd

  23. Source 23: Workday Unveils Workday Build, Giving Developers the Tools to Build the Future of Work Workday · checked Back:ab

  24. Source 24: Workday Build | Workday US Workday · checked Back:ab

  25. Source 25: Tools & Integrations CrewAI · checked Back to text

  26. Source 26: Kickoff Crew CrewAI · checked Back to text

  27. Source 27: Deploy to AMP CrewAI · checked Back:abc

  28. Source 28: Concept: External Agent ASU Considerations (Workday Administrator Guide) Workday · checked Back to text

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

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

  31. Source 31: OpenTelemetry Export CrewAI · checked Back:ab

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

  33. Source 33: Workday Compliance | Workday US Workday · checked Back:ab

  34. Source 34: Automations CrewAI · checked Back:ab

  35. Source 35: Concept: Agent Interaction Policy (Workday Administrator Guide) Workday · checked Back to text

  36. Source 36: Flow HITL Management CrewAI · checked Back to text

  37. Source 37: Connect External Agents to Workday Using A2A (Workday Administrator Guide) Workday · checked Back:abcd

  38. Source 38: Concept: ASOR Agent Resource Search API (Workday Administrator Guide) Workday · checked Back:ab

  39. Source 39: Workday Support | Workday US Workday · checked Back to text

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

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

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

  43. Source 43: Workday Announces New AI Agent Partner Network and Agent Gateway Workday · checked Back to text

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

  45. Source 45: Workday Flex Credits | Workday US Workday · checked Back to text

  46. Source 46: Why Blocks? Blocks.ai · checked Back to text

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

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

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

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