Documentation Index
Fetch the complete documentation index at: https://langchain-5e9cc07a-preview-mdrxyo-1777658790-7be347c.mintlify.app/llms.txt
Use this file to discover all available pages before exploring further.
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.
| Platform | Choose if… |
|---|
| LangSmith Fleet | You 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 Cowork | You 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 Quick | You are already on AWS and want an AI assistant with direct access to your AWS data sources and enterprise integrations. |
| Google Workspace Studio | Your organization runs on Google Workspace and you want no-code agents that work natively inside Gmail, Drive, and Sheets without leaving the Google ecosystem. |
Compare capabilities
- ❌ Not available
- ⚠️ Partial or limited
- — Not confirmed from public documentation
| Aspect | LangSmith Fleet | Claude Cowork | Amazon Quick | Google Workspace Studio |
|---|
| Primary use case | Teams 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 task | Individual knowledge work from the desktop (research, analysis, task delegation) | Enterprise AI assistance with deep AWS data and service integration | No-code agents tightly integrated with Google Workspace apps (Gmail, Drive, Sheets) |
| Model support | Model-agnostic: any LLM with an OpenAI-compatible or Anthropic-compatible API | Claude only | — | Gemini 3 |
| Interface | Web app, Slack app, Teams app, API | Desktop app (macOS, Windows) | Web app | Web app (Google Workspace) |
| Deployment | Cloud (LangSmith) or self-hosted | Local on device | Cloud (AWS-hosted) | Cloud (Google-hosted) |
| Self-hosting | ✅ Beta, contact sales for production readiness details | ❌ | ❌ | ❌ |
| Code export | ✅ Export to Deep Agents | ❌ | ❌ | ❌ |
| Observability | LangSmith tracing and evaluations at scale | — | — | Basic run history |
| Platform license | Proprietary | Proprietary | Proprietary | Proprietary |
| Code export license | MIT (Deep Agents) | N/A | N/A | N/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.
Claude 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.
Amazon Quick and Google 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.
Claude Cowork takes a similar approach with a “show me the plan first” model. Amazon Quick offers notifications but without a centralized inbox for reviewing actions across all agents.
Enterprise controls and access
Fleet provides RBAC, attribute-based access control, and per-agent sharing permissions (Clone, Run, and Edit) that Claude Cowork does not offer. This is a significant difference for organizations that need to manage which teams can access, run, or modify specific agents.
Amazon Quick and Google 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. Claude Cowork, Amazon Quick, and Google Workspace Studio all offer more granular spend controls. For enterprise billing options, contact sales.
Model flexibility
Fleet supports any LLM via the OpenAI or Anthropic chat spec, including models from OpenAI, Anthropic, Google, and self-hosted providers.
Claude Cowork is locked to Claude. Google Workspace Studio uses 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 Claude 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.
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.
Claude Cowork, Amazon Quick, and Google Workspace Studio each have audit and activity logs, but none match Fleet’s depth of tracing, evaluations, and debugging through a dedicated observability platform.
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. Claude Cowork stores data locally on device, making it the only platform in this comparison that keeps data entirely off external servers.
A ✅ indicates the integration is available; supported actions and depth vary by platform. See Fleet tool integrations for the full list of Fleet’s built-in integrations and what each one can do.
| Feature | Fleet | Claude Cowork | Amazon Quick | Google 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 | ✅ | ✅ | ✅ | ❌ |
| Webhooks | ✅ Webhooks | ❌ | ❌ | — |
Last updated April 21st, 2026. These products evolve quickly. If something has changed, please file an issue to help us keep this page current.
