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.

LangSmith vs Workday Agent System of Record

LangSmith

Platform for observing, evaluating, and deploying agents

Workday Agent System of Record

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

Short answer

LangChain calls LangSmith a platform for observing, evaluating, and deploying agents; Workday Agent System of Record (ASOR), set up in each Workday tenant, registers and manages agents.⁠Source 1, Source 2, Source 3 LangSmith runs agents in LangChain’s cloud (Plus plan or above) or, on Enterprise, your own infrastructure; ASOR gives each agent a unique Workday identity under Workday security policies.⁠Source 4, Source 5, Source 6, Source 7

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 registry of agents, set who can use each agent, and record agent activity, and both work with A2A.⁠Source 2, Source 8, Source 9, Source 10, Source 11, Source 12, Source 13, Source 14
Where they differ
LangSmith builds agents, in Fleet, and runs agents on LangSmith Deployment.⁠Source 4, Source 15 ASOR is set up per Workday tenant; for agents working with Workday, tools are Workday APIs.⁠Source 2, Source 3
Running both
Workday’s docs say you register external agents through the ASOR API, recording each one’s platform, or OTHER.⁠Source 16, Source 17 LangSmith’s docs say agents can send it traces from wherever they run.⁠Source 5
Public sources · checked 2 October 2026
  • Offered
  • Not publicly documented

LangSmith

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

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 6
  • Registry and governance: OfferedAgent Registry in Management Hub⁠Source 2
  • Traffic between agents, tools, and models: OfferedAgent Gateway for Workday APIs⁠Source 19
  • Agents across organizations: Not publicly documented

At a glance

TopicLangSmithWorkday Agent System of Record
What it isLangChain calls it a framework-agnostic platform for observing, evaluating, and deploying agents, with no-code agent building in LangSmith Fleet.⁠Source 1, Source 15A functional area you enable in each Workday tenant to find, register, configure, monitor, and manage AI agents.⁠Source 2, Source 3
Where it runsLangChain’s cloud, on GCP or AWS; or, on Enterprise, BYOC on AWS, self-hosted, or hybrid.⁠Source 5, Source 20, Source 21, Source 22Inside each Workday tenant.⁠Source 3 External agents are registered through the ASOR API with the URL where each one is hosted.⁠Source 16, Source 17
Identity and accessAPI keys or your own auth handlers on hosted agents; Fleet agents act with fixed or the user’s credentials.⁠Source 23, Source 24 Enterprise adds RBAC, and SAML SSO and SCIM on Cloud.⁠Source 25, Source 26A unique Workday identity per agent, using Agent System User accounts governed by Workday security policies and groups.⁠Source 6, Source 7
Pricing modelA Developer plan with one free seat, Plus at $39 per seat per month, and Enterprise through sales.⁠Source 22 Usage is metered in LSUs, $1 each.⁠Source 22No additional specific SKU for ASOR.⁠Source 2 Registering Workday-built agents in production requires opting in to the Universal Main Service Agreement and a Flex Credits policy.⁠Source 2 A credit’s price is not publicly documented.
Generally availableLangChain announced GA of LangGraph Platform (now Deployment) in May 2025 and Agent Builder (now Fleet) in January 2026.⁠Source 8, Source 27, Source 28, Source 29Generally available since February 2026.⁠Source 30

What each one is

LangSmith

LangChain describes LangSmith as a framework-agnostic platform for observing, evaluating, and deploying agents.⁠Source 1 LangSmith Deployment runs agents in production, and LangChain says Fleet lets teams, including non-technical ones, create and manage agents without code.⁠Source 1, Source 4, Source 15 Agents hosted elsewhere can send it traces.⁠Source 5

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 agents.⁠Source 2, Source 3 It covers agents built by Workday, partners, or the customer, though some, including agents for HiredScore and Evisort, are not part of it.⁠Source 2

The differences that matter

  1. Building and running agents

    LangSmith

    Fleet builds agents without code from a description or template, and LangSmith Deployment runs agents built with LangChain or other frameworks.⁠Source 4, Source 15, Source 31

    Workday Agent System of Record

    ASOR takes an external agent’s definition through an API; Workday announced a low-code agent builder for Workday’s separate Workday Build.⁠Source 2, Source 32

    The models behind Fleet’s three managed tiers may change over time.⁠Source 33 Which models ASOR supports or includes is not publicly documented.

  2. What an agent can reach

    LangSmith

    A Fleet agent acts with fixed credentials or the user’s own; on Enterprise, admins can grant or restrict users’ access to integrations and MCP servers.⁠Source 11, Source 24

    Workday Agent System of Record

    Workday security policies and groups set what each agent can access; acting for a user, an agent gets only what both may do.⁠Source 6, Source 7

    For callers, hosted LangSmith deployments use API keys by default or your auth handler; Workday’s Agent Interaction Policy sets which users may use an agent’s delegate-mode skills.⁠Source 23, Source 34

  3. Remote and partner agents

    LangSmith

    Fleet can share agents with individual users or your whole workspace, and Agent Server agents can talk to other A2A-compatible agents.⁠Source 11, Source 13

    Workday Agent System of Record

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

    For both, access controlled by a partner company that owns the agent is not publicly documented.

For security teams

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

TopicLangSmithWorkday Agent System of Record
Network exposureAgent Server has A2A and MCP endpoints.⁠Source 13, Source 35 For deployment updates, the data plane polls the control plane, never the reverse.⁠Source 10Third-party agents reach Workday APIs through Agent Gateway, a single regional endpoint.⁠Source 19 Inbound endpoint needs: not publicly documented.
IdentityHosted Agent Servers default to API keys; self-hosted ones have no default authentication.⁠Source 23 Cloud Enterprise adds SAML SSO and SCIM.⁠Source 26Unique identity per agent.⁠Source 6 External agents use OAuth 2.0 or signed JWTs; tokens for third-party (self-built) agents last 4 hours.⁠Source 2, Source 6, Source 36
Access changes and revocationFleet sharing can be revoked at any time, and organization admins can deactivate any member’s personal access token.⁠Source 11, Source 37Deactivating an agent hides it from users; the change may take up to a minute to reach Agent Gateway.⁠Source 2, Source 19
Audit trailEnterprise audit logs of admin and configuration actions, kept up to 400 days, can be pulled hourly into a SIEM.⁠Source 38An audit trail report covers agent transactions; delegated actions record both agent and user.⁠Source 6, Source 12 SIEM export is not publicly documented.
ComplianceLangChain lists SOC 2 Type II, ISO 27001:2022, GDPR, and HIPAA for LangSmith.⁠Source 39, Source 40Workday says its SOC 2 report covers Workday Enterprise Products; ASOR isn’t named.⁠Source 41 ISO 42001 covers Workday Platform.⁠Source 41

Full comparison

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

LangSmith and Workday Agent System of Record compared on 18 criteria
LangSmithWorkday Agent System of Record
What it is
What it is and who it’s forLangChain calls it a framework-agnostic platform for observing, evaluating, and deploying agents.⁠Source 1 LangChain says no-code Fleet is for non-technical teams.⁠Source 1, Source 15Set up in each Workday tenant to find, register, configure, monitor, and manage AI agents; Workday calls it an agent analytics hub for IT and business leaders.⁠Source 2, Source 3, Source 42
MaturityLangChain announced GA of LangGraph Platform (now Deployment) on 14 May 2025 and Agent Builder (now Fleet) on 13 January 2026.⁠Source 8, Source 27, Source 28, Source 29Announced in February 2025; generally available since February 2026.⁠Source 30, Source 43 Agent Gateway was announced in June 2025.⁠Source 44
Control
Agent registry and discoveryLangChain says Deployment manages agents through a centralized registry with versioning.⁠Source 8, Source 45 Listing agents hosted elsewhere is not publicly documented.The Agent Management Hub lists Workday-built, partner-built, and self-built agents with status.⁠Source 2 Some, such as HiredScore and Evisort agents, are outside ASOR.⁠Source 2
Identity and access controlAPI keys or your own auth handlers on hosted agents.⁠Source 23 Fleet agents use fixed or the user’s credentials.⁠Source 24 Enterprise adds RBAC, plus SAML SSO on Cloud.⁠Source 25, Source 26Each agent has a unique Workday identity, governed by security policies and groups.⁠Source 6, Source 7 Acting for a user, an agent gets only what both may do.⁠Source 6
Ownership, policy, and revocationFleet shows each agent’s owner, has per-agent Clone, Run, and Edit permissions revocable at any time, and supports spend limits.⁠Source 9, Source 11, Source 29, Source 46Admins set each agent’s skills and who can use it, and activate or deactivate it.⁠Source 2, Source 42 A deactivated agent is hidden from users and can be reactivated.⁠Source 2
Audit log and observabilityEnterprise audit logs of admin and configuration actions, kept up to 400 days.⁠Source 38 Each deployment gets a tracing project; Fleet traces include tool calls.⁠Source 10, Source 11An audit trail report covers agent transactions; delegated actions record the agent and the user.⁠Source 6, Source 12 Per-agent analytics reports cover Workday-built agents only.⁠Source 2
Connection
How agents connectOn self-hosted LangSmith with Deployment, agents run behind an ingress you configure.⁠Source 47 Enterprise can reach LangSmith Cloud over AWS PrivateLink.⁠Source 20Third-party agents must route Workday API traffic through Agent Gateway, a single regional endpoint.⁠Source 19 Outbound-only use is not publicly documented.
Agents across organizationsFleet can share agents with users or your workspace; Agent Server agents can talk to other A2A agents.⁠Source 11, Source 13 A cross-company access model is not publicly documented.ASOR manages partner-built agents; a definition can carry an ID locating each one in the partner’s system.⁠Source 2, Source 17 Partner-held controls are not publicly documented.
Protocol supportAgent Server supports A2A over JSON-RPC, with documented gaps, and can expose agents as MCP tools.⁠Source 13, Source 35 Fleet discovers tools from remote MCP servers.⁠Source 18API registration is based on the A2A Agent Card.⁠Source 17 Outside assistants can call the Self-Service Agent over A2A; tool search can filter by SOAP, REST, or MCP.⁠Source 14, Source 48
Frameworks, models, and clouds supportedDeployment runs agents built with Google ADK, Claude Agent SDK, Strands, CrewAI, AutoGen, and other libraries.⁠Source 31 Agents run elsewhere can send it traces.⁠Source 5API registration records each agent’s platform, or OTHER.⁠Source 17 Workday names Google Gemini Enterprise as an outside assistant able to call its Self-Service Agent.⁠Source 14
Operations
Deployment options and data residencyCloud on GCP (US, EU, APAC) or AWS (US).⁠Source 20 BYOC on AWS, or self-hosted or hybrid, on Enterprise.⁠Source 5, Source 21, Source 22Set up in each Workday tenant.⁠Source 3 Agent Gateway endpoints: US, EU, UK, Canada, Australia, Singapore, India, Japan.⁠Source 19 Self-hosting: not publicly documented.
Compliance attestationsLangChain’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 39Workday says its SOC 2 report covers Workday Enterprise Products.⁠Source 41 Its ISO 42001 certificate covers named products including Workday Platform; ASOR isn’t named.⁠Source 41
Support and SLABase, Standard, and Premium support plans.⁠Source 49 Reasonable commercial efforts toward 99.5% API uptime for SaaS, measured quarterly.⁠Source 49Workday says its company-wide support is 24/5, with severity 1 cases 24/7/365, or 24/7/365 with Success Plans.⁠Source 50 An ASOR uptime SLA is not publicly documented.
Time and effort to get runningCloud deployment needs the Plus plan or above and an API key.⁠Source 51 Self-hosting the Deployment control plane needs Kubernetes, self-hosted LangSmith, and Enterprise.⁠Source 4Enable 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 16
Pricing model and public pricesDeveloper plan with one free seat; Plus $39 per seat per month; Enterprise via sales.⁠Source 22 Usage is metered in LSUs, $1 each.⁠Source 22No 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 toolsFleet builds no-code agents from a description or template.⁠Source 15 Agents in code can be deployed with the LangGraph CLI and app templates.⁠Source 4You provide an external agent’s definition through an API.⁠Source 2 Workday announced the low-code Flowise Agent Builder for Workday’s separate Workday Build in 2025.⁠Source 32
Model accessLangChain says LangSmith works with closed or open models.⁠Source 1 Fleet’s managed picker has three tiers (Fast, Pro, Max), not custom models.⁠Source 33Workday’s AI agents use large language models.⁠Source 2 Which models ASOR supports or includes is not publicly documented.
Integrations and ecosystemFleet has built-in tools such as Gmail; LangChain says its agents work in Slack, Teams, and Gmail.⁠Source 33, Source 52 Tracing integrates with OpenAI, Anthropic, and more.⁠Source 53In February 2026, Workday said more than 65 partners were connecting agents to ASOR.⁠Source 30 Workday says partner agents reached Workday Marketplace in June 2025.⁠Source 44

Which to choose

Choose LangSmith if

  • You want one platform to build, deploy, and observe agents: no-code agents in Fleet, and agents from many frameworks on Deployment.⁠Source 1, Source 15, Source 31
  • You need LangSmith’s control plane and Agent Servers in your own infrastructure, for full data residency or air-gapped use, on Enterprise.⁠Source 4
  • Non-technical teams should build agents without code, from a description or template, and use them in Slack, Teams, or Gmail.⁠Source 1, Source 15, Source 52
  • You want to trace agents wherever they run, from any OpenTelemetry-compatible app or through integrations such as OpenAI, Anthropic, and CrewAI.⁠Source 5, Source 53, Source 54

Choose Workday Agent System of Record if

  • Your agents mostly work in Workday, and each should have its own Workday identity under your existing security policies and groups.⁠Source 2, Source 6, Source 7
  • You want an agent acting for a user limited to what both may do, with audit entries naming both.⁠Source 6
  • You want Workday-built, partner-built, and self-built agents listed with their status in one Agent Management Hub.⁠Source 2
  • 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

Questions buyers ask

Can either one manage agents built elsewhere?

You register external agents through ASOR’s API, and ASOR manages self-built and partner-built agents; per-agent analytics reports cover Workday-built agents only.⁠Source 2, Source 16 LangSmith Deployment runs agents from other frameworks, and agents run elsewhere can send it traces.⁠Source 5, Source 31 Listing those in its registry is not publicly documented.

How is each one priced?

LangSmith: a Developer plan with one free seat, Plus at $39 per seat a month, and usage metered in LSUs, $1 each.⁠Source 22 ASOR needs no additional specific SKU; Workday-built agents in production need a Flex Credits policy opt-in.⁠Source 2 A credit’s price is not publicly documented.

Do they support MCP and A2A?

LangSmith’s Agent Server supports A2A, with documented gaps, and can expose agents as MCP tools.⁠Source 13, Source 35 Workday bases external agent registration on the A2A Agent Card and lists MCP as a tool type; outside assistants can call its Self-Service Agent over A2A.⁠Source 14, Source 17, Source 48

Can either one be self-hosted?

LangSmith can: self-hosted, hybrid, and BYOC (on AWS) are Enterprise plan options, and self-hosted LangSmith Deployment covers full data residency or air-gapped use.⁠Source 4, Source 5, Source 21, Source 22 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

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

  1. Source 1: LangSmith: The Agent Engineering Platform LangChain · checked Back:abcdefghi

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

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

  4. Source 4: LangSmith Deployment LangChain · checked Back:abcdefghi

  5. Source 5: Set up LangSmith LangChain · checked Back:abcdefghi

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

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

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

  9. Source 9: Agent platform comparison LangChain · checked Back:abc

  10. Source 10: LangSmith control plane LangChain · checked Back:abc

  11. Source 11: Access & oversight LangChain · checked Back:abcdefg

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

  13. Source 13: A2A endpoint in Agent Server LangChain · checked Back:abcdef

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

  15. Source 15: No-code agents with LangSmith Fleet LangChain · checked Back:abcdefghi

  16. Source 16: Register External Agents (Workday Administrator Guide) Workday · checked Back:abcd

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

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

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

  20. Source 20: Cloud (SaaS) LangChain · checked Back:abc

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

  22. Source 22: LangSmith Plans and Pricing LangChain · checked Back:abcdefgh

  23. Source 23: Authentication & access control LangChain · checked Back:abcd

  24. Source 24: Agent identity LangChain · checked Back:abc

  25. Source 25: Role-based access control LangChain · checked Back:ab

  26. Source 26: Authentication methods LangChain · checked Back:abc

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

  28. Source 28: Now GA: LangSmith Agent Builder LangChain · checked Back:ab

  29. Source 29: LangSmith Fleet changelog LangChain · checked Back:abc

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

  31. Source 31: Deploy other frameworks LangChain · checked Back:abcd

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

  33. Source 33: Essentials LangChain · checked Back:abc

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

  35. Source 35: MCP endpoint in Agent Server LangChain · checked Back:abc

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

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

  38. Source 38: Audit logs LangChain · checked Back:ab

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

  40. Source 40: LangSmith shared responsibility model LangChain · checked Back to text

  41. Source 41: Workday Compliance | Workday US Workday · checked Back:abcd

  42. Source 42: Workday Agent System of Record | Workday US Workday · checked Back:ab

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

  44. Source 44: Workday Announces New AI Agent Partner Network and Agent Gateway Workday · checked Back:ab

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

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

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

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

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

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

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

  52. Source 52: LangSmith Fleet LangChain · checked Back:ab

  53. Source 53: LangSmith Observability LangChain · checked Back:ab

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

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

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

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

  58. Source 58: Solutions: Partner networks Blocks.ai · checked Back to text

  59. Source 59: Pricing Blocks.ai · checked Back to text