Skip to main content
LangSmith Fleet is an enterprise agent platform for building, sharing, and governing agents across your organization. This page compares it with similar platforms to help you choose the right one for your team.
PlatformChoose if…
LangSmith FleetYou want to build and share purpose-built agents across your organization, stay model-agnostic, and keep full observability via LangSmith. Fleet is the only option with a self-hosted deployment path and the ability to export agents to code via Deep Agents.
Claude CoworkYou want to delegate open-ended tasks to Claude from the desktop for personal knowledge work, and on-device data storage meets your privacy requirements.
Amazon QuickYou are already on AWS and want an AI assistant with direct access to your AWS data sources and enterprise integrations.
Google Workspace StudioYour organization runs on Google Workspace and you want no-code agents that work natively inside Gmail, Drive, and Sheets without leaving the Google ecosystem.

Overview

  • ✅ Available
  • ❌ Not available
  • ⚠️ Partial or limited
  • — Not confirmed from public documentation
AspectLangSmith FleetClaude CoworkAmazon QuickGoogle Workspace Studio
Primary use caseTeams building purpose-built agents to share across an organization, with no-code creation and code export for custom deployments; individuals using a general-purpose chat agent for any taskIndividual knowledge work from the desktop (research, analysis, task delegation)Enterprise AI assistance with deep AWS data and service integrationNo-code agents tightly integrated with Google Workspace apps (Gmail, Drive, Sheets)
Model supportModel-agnostic: any LLM with an OpenAI-compatible or Anthropic-compatible APIClaude onlyGemini 3
InterfaceWeb app, Slack app, Teams app, APIDesktop app (macOS, Windows)Web appWeb app (Google Workspace)
DeploymentCloud (LangSmith) or self-hostedLocal on deviceCloud (AWS-hosted)Cloud (Google-hosted)
Self-hostingBeta, contact sales for production readiness details
Code exportExport to Deep Agents
ObservabilityLangSmith tracing and evaluations at scaleBasic run history
Platform licenseProprietaryProprietaryProprietaryProprietary
Code export licenseMIT (Deep Agents)N/AN/AN/A

Target users

Fleet covers both org-wide and personal use cases. Teams can build purpose-built agents to share across an organization (for example, a vendor intake agent that serves an entire ops org, or a weekly report agent that saves every account manager thirty minutes on Monday morning), and any user can get help with any task using any tool via Fleet’s general-purpose default chat. Cowork is designed for individual workflows: each user runs Claude on their own machine for open-ended task delegation, rather than building and sharing agents across a team. Quick and Workspace Studio are workforce-wide platforms built around answering questions and automating workflows, but not primarily designed for building and sharing purpose-built agents. Fleet also lets you set tool-level approval requirements so agents check with you before executing sensitive steps, with a centralized inbox for reviewing, editing, and approving actions. Cowork takes a similar approach with a “show me the plan first” model. Quick offers notifications but without a centralized inbox for reviewing actions across all agents.
FeatureFleetClaude CoworkAmazon QuickGoogle Workspace Studio
General-purpose chat agentFleet chat
No-code agent builder
Slack-native integrationNative Slack app
Microsoft Teams integrationTeams app
Scheduled runsSchedules
Sub-agentsSub-agents✅ Managed Agents
Skills systemSkills
Human-in-the-loopCentral approvals inbox✅ Plan-first approach⚠️ Notifications only
MCP clientRemote MCP servers
Web search✅ (via Exa, Tavily)✅ Built-in✅ Built-in

Enterprise controls and access

Fleet provides RBAC, attribute-based access control, and per-agent sharing permissions (Clone, Run, and Edit) that Cowork does not offer. This is a significant difference for organizations that need to manage which teams can access, run, or modify specific agents. Quick and Workspace Studio inherit access controls from their respective cloud platforms (AWS IAM and Google Workspace roles), but neither offers Fleet’s per-agent permission model. Fleet manages spending at the workspace level rather than through per-user or per-team caps. Cowork, Quick, and Workspace Studio all offer more granular spend controls. For enterprise billing options, contact sales.
FeatureFleetClaude CoworkAmazon QuickGoogle Workspace Studio
Role-based access controlRBAC with per-tool permissions✅ SCIM-based groups and roles✅ AWS IAM✅ Google Workspace roles
Attribute-based access controlPer MCP server and integration
Per-agent sharing and permissionsClone, Run, and Edit access per agent
Credential model (fixed or per-user)Configurable per agent
Spend limits⚠️ Managed at workspace level
SCIM provisioning
Audit trailStructured LangSmith traces⚠️ Basic run history

Model flexibility

Fleet supports any LLM via the OpenAI or Anthropic chat spec, including models from OpenAI, Anthropic, Google, and self-hosted providers. Cowork is locked to Claude and Workspace Studio to Gemini 3. Amazon Quick’s supported models are not confirmed from public documentation. Google Workspace Studio is included in Google Workspace Business and Enterprise plans with no separate purchase, but it works only within the Google ecosystem. Amazon Quick requires existing AWS infrastructure and does not include a bundled productivity suite. Fleet and Cowork are largely ecosystem-agnostic.

Memory, self-updates, and learning

Fleet agents can persist context across conversations using a dedicated memory system, and can update their own instructions, add tools, or remove tools as they learn from interactions. Of the four platforms compared here, only Fleet supports agent self-modification.
FeatureFleetClaude CoworkAmazon QuickGoogle Workspace Studio
Long-term memoryPersistent memory files across sessions
Thread-scoped context
Self-updating agentsAgents can add tools, remove tools, and update their own instructions
Approval gate for memory writesConfigurable per agent

Observability and governance

Fleet’s clearest advantage is its native connection to LangSmith. Every agent run is traced in LangSmith, making it easy to debug performance and run evaluations at scale. The other three have audit and activity logs, but none match Fleet’s depth of tracing, evaluations, and debugging through a dedicated observability platform.
FeatureFleetClaude CoworkAmazon QuickGoogle Workspace Studio
Native tracingLangSmith traces for every run⚠️ Basic
EvaluationsLangSmith evaluations

Code export and hosting

Fleet lets you export any agent you build to code via Deep Agents, the open-source agent runtime that Fleet runs on. Exported agents are MIT-licensed and can be deployed independently of Fleet, modified in code, or integrated directly into your own applications via the API. None of the other platforms in this comparison offer a code export path. Fleet is the only platform in this comparison with a self-hosted deployment option. For teams with compliance requirements, self-hosted and BYOC (bring your own cloud) configurations let you run Fleet entirely within your own infrastructure. Amazon Quick offers enterprise-grade AWS infrastructure natively. Google Workspace Studio adheres to Google Workspace data commitments. Cowork stores data locally on device, making it the only platform in this comparison that keeps data entirely off external servers.
FeatureFleetClaude CoworkAmazon QuickGoogle Workspace Studio
Cloud-hosted
Self-hostedBeta, contact sales for production readiness details
Custom modelsAny OpenAI- or Anthropic-compatible API⚠️ Custom models via Bedrock
Call agents from your appAPI access✅ Managed Agents API✅ Amazon Quick API
Export to codeExport to Deep Agents

Integrations and tools

FeatureFleetClaude CoworkAmazon QuickGoogle Workspace Studio
Google Workspace (Gmail, Drive, Sheets, Docs)✅ Plugin✅ Native
Microsoft 365 (Outlook, Teams, SharePoint, Excel)✅ Plugin
GitHub✅ Plugin
Slack✅ Native
CRM (Salesforce, HubSpot)✅ Plugin
Project management (Linear, Jira, Notion)✅ Plugin
Custom tools via MCP
WebhooksWebhooks
In the integrations table above, ✅ indicates the integration is available. Depth and supported actions vary by platform. See Fleet tool integrations for the full list of Fleet’s built-in integrations and what each one can do.
For pricing and SLA information, contact sales.
Last updated April 21st, 2026. These products evolve quickly. If something has changed, please file an issue to help us keep this page current.