OpenWork vs Claude Cowork on 3P
Keep Bedrock, Vertex, or Foundry. Add any model, and share skills and MCP servers with every teammate.
Enterprise binary deploys with your existing tooling.
Enterprise, 3P, or OpenWork
25 capabilities, checked against each vendor's own docs. Yes, Partial, or No for what ships today.
| Capability | Claude Enterprise | Claude on 3P | OpenWork |
|---|---|---|---|
| Where you use it | |||
| Desktop app for macOS and Windows | Yes | Yes | Yes |
| Desktop app for Linux | Partial1 | Partial2 | Yes |
| Full workspace in a web browser | Yes | No | Yes3 |
| Start work from Slack | Yes | No | Yes4 |
| Phone app | Yes | No | NoPlanned |
| Your skills and connections inside Claude Code, Codex, and Cursor | No | No | Yes5 |
| What the agent can do | |||
| SKILL.md skills and Claude-format plugins | Yes | Yes | Yes |
| MCP connectors with OAuth, set up once for everyone | Yes | Yes6 | Yes |
| Built-in browser the agent drives | Yes | Yes | Yes |
| Computer use with desktop apps | Partial7 | No | Yes8 |
| Artifacts and interactive app views | Yes | Yes | Yes9 |
| Projects to group related chats and files | Yes | Yes | Partial10 |
| Memory across chats | Yes | Yes11 | Partial12 |
| Isolated sandbox for agent commands | Yes | Yes | Partial13 |
| Automations | |||
| Scheduled and triggered tasks | Yes | Yes | Partial14Planned |
| Keeps running with your laptop closed | Yes15 | No16 | Yes17 |
| Run history, retries, and approvals | Yes | Yes | Partial18Planned |
| Control and deployment | |||
| Any model, including open-weight and self-hosted | No | Partial19 | Yes |
| Prompts stay in your cloud, vendor telemetry off | No20 | Yes21 | Yes |
| Share skills, plugins, and MCP servers with your team | Yes | Partial22 | Yes |
| SSO, SCIM, teams, and custom roles | Yes | Partial23 | Yes |
| Desktop policies and version control | Yes | Yes | Yes24 |
| Spend limits per team or person | Yes | Partial25 | Yes |
| Usage analytics, OpenTelemetry, and audit log | Yes | Partial26 | Partial27Planned |
| Self-host the control plane, with open source code | No | No | Yes |
| Yes, of 25 | 19+2 partial | 12+6 partial | 18+6 partial |
| Price per person, per month | $20 + usage | No seat fee | Free, or from $10 |
- 1Claude Desktop on Linux is in beta. Source
- 2Linux settings are documented, but the 3P install guide lists only macOS and Windows. Source
- 3OpenWork Web runs on OpenWork Cloud or your own deployment. Source
- 4An admin turns on OpenWork in Slack for the organization. Source
- 5One MCP URL carries your organization's skills and connections. Source
- 6Admins push managed MCP servers, including OAuth, by console or MDM. Source
- 7In beta, on macOS and Windows. Source
- 8On macOS and Windows. Source
- 9Artifacts, live artifacts, and MCP Apps in chat and on dashboards. Source
- 10Work is organized in workspaces and folders. Claude projects are not migrated automatically yet. Source
- 11Stored on the device. Chat-history search is not available on 3P. Source
- 12The agent can search and read past chats when asked; nothing is remembered automatically. Source
- 13Agent work can run in isolated cloud computers; there is no local sandbox yet. Source
- 14Automations run on a schedule on desktop or in the cloud; event triggers are next. Source
- 15Scheduled tasks can move to the cloud. Source
- 16Sessions run on the device. Source
- 17Cloud Automations run in OpenWork Cloud or on your own runners. Source
- 18Run history, receipts, and missed-run recovery ship; approvals in the middle of a run are next. Source
- 19Claude models; others only through an Anthropic-compatible gateway you run. Source
- 20Inference runs on Anthropic's API. Source
- 21On Bedrock or Vertex. On Foundry, Anthropic processes conversations. Source
- 22Through a plugin marketplace you host in git or over HTTPS, plus MDM. Source
- 23Through the Enterprise Admin Console, hosted by Anthropic and provisioned on request. Source
- 24Model access, allowed versions, and agent permissions for commands, file edits, websites, and local skills and MCP servers. Source
- 25Per-user token limits; dollar budgets live in your cloud or gateway. Source
- 26OpenTelemetry export; the Compliance API only in Admin Console organizations, and no Analytics API. Source
- 27Usage analytics and an audit log with API and CSV export ship; OpenTelemetry export is next. Source
Planned links to the public roadmap and never counts as Yes. Sources, checked 2026-10-27:3P feature matrix3P overview3P plugins and MCPClaude Desktop on LinuxClaude in SlackClaude computer useClaude Enterprise pricingOpenWork roadmapOpenWork pricing
Why teams on 3P switch
Keep your cloud account and committed spend
Send routine work to lower-cost models
Share skills and MCP servers without MDM profiles
Run alongside Claude Desktop while teams switch
Frequently asked questions
- What is Claude Desktop on 3P?
- Claude Desktop, including Cowork, sending inference to Bedrock, Vertex, Foundry, or your own gateway. There is no seat fee. It is built for Claude models; others need an Anthropic-compatible gateway you run.
- Can OpenWork use my Bedrock, Vertex, or Foundry account?
- Yes, plus any OpenAI-compatible gateway. Your existing cloud commitments keep applying.
- How do we share skills and MCP servers?
- Admins publish them once in OpenWork Cloud and assign them to teams. Each person signs in to MCP connections as themselves.
- Can we self-host OpenWork?
- Yes, with Helm on Kubernetes, Docker Compose for evaluation, or beta Terraform modules for AWS, Google Cloud, and Azure. Enterprise costs the same cloud or self-hosted.
- Does OpenWork have a mobile app?
- Not yet; it is on the public roadmap. OpenWork runs on macOS, Windows, Linux, and in the browser, and your team can start work from Slack today.
Keep your cloud. Choose your models.
See OpenWork on your own gateway, with your skills shared.
Same price cloud or self-hosted.