# What Is the Role of the different-ai Organization in OpenWork?

> Discover the central role of the different-ai organization in OpenWork. They own and maintain the desktop app, Den control plane, and all release artifacts, ensuring a robust ecosystem.

- Repository: [Different AI/openwork](https://github.com/different-ai/openwork)
- Tags: getting-started
- Published: 2026-08-02

---

**The different-ai GitHub organization owns and maintains the entire OpenWork ecosystem, serving as the canonical source for the desktop application, Den control plane, and all release artifacts.**

The OpenWork project lives under the `different-ai/openwork` namespace, establishing the organization as the central steward of this AI-native workspace platform. As both the infrastructure provider and code maintainer, different-ai governs everything from source code distribution to cloud service endpoints that power team-wide OpenWork deployments.

## Repository Ownership and Canonical Source

The `different-ai` organization holds the canonical repository at `github.com/different-ai/openwork`, making it the single source of truth for the project. According to the repository's [`README.md`](https://github.com/different-ai/openwork/blob/main/README.md) (lines 1-3), this ownership structure ensures that all contributors and users pull from a trusted, organization-maintained codebase rather than community forks.

This centralized ownership extends beyond code hosting. The organization maintains the project's identity across package registries, as evidenced by the repository URL declared in [`packages/openwork-ui-mcp/package.json`](https://github.com/different-ai/openwork/blob/main/packages/openwork-ui-mcp/package.json): `git+https://github.com/different-ai/openwork.git`.

## The Den: Cloud Control Plane

A core responsibility of the different-ai organization is building and operating **OpenWork's Den**—the "control plane for managing OpenWork across a team or organization." As documented in [`README.md`](https://github.com/different-ai/openwork/blob/main/README.md) (lines 68-76), the Den encompasses both the Den API and Den web UI, providing centralized management for enterprise deployments.

The organization hosts these services on infrastructure that separates open-source components from proprietary cloud features. This distinction appears in the codebase where the Den's Helm charts and deployment configurations reside under the organization's container registry namespace.

## Release Pipeline and Distribution

All official OpenWork releases flow through the different-ai organization's infrastructure. The [`README.md`](https://github.com/different-ai/openwork/blob/main/README.md) (lines 45-48) confirms that desktop binaries, Electron installers, Docker images, and Helm charts publish exclusively from the `different-ai/openwork` repository.

Users download installers directly from organization-hosted release assets:

```bash
curl -L -o OpenWork.dmg \
  https://github.com/different-ai/openwork/releases/download/v0.18.13/OpenWork-mac-arm64-0.18.13.dmg

```

*Source: README.md, "Download OpenWork" section*

For enterprise deployments, the organization maintains the official Helm chart repository at `ghcr.io/different-ai/charts/openwork-ee`, as documented in [`packaging/helm/openwork-ee/README.md`](https://github.com/different-ai/openwork/blob/main/packaging/helm/openwork-ee/README.md).

## MCP and Cloud Endpoint Integration

The organization operates the Multi-Capability Protocol (MCP) endpoints that enable AI agents to interact with OpenWork services. The canonical MCP configuration points to `https://api.openworklabs.com/mcp/agent`—a URL owned and maintained by different-ai.

When configuring an AI agent to use OpenWork, users reference this organization-controlled endpoint in their [`opencode.json`](https://github.com/different-ai/openwork/blob/main/opencode.json):

```json
{
  "mcp": {
    "openwork": {
      "type": "remote",
      "enabled": true,
      "url": "https://api.openworklabs.com/mcp/agent",
      "oauth": {}
    }
  }
}

```

*Source: README.md, lines 45-58*

This endpoint configuration appears alongside the package metadata that defines how agents authenticate and communicate with cloud-hosted OpenWork instances.

## Deployment Infrastructure and Supply Chain

Beyond application code, the different-ai organization curates the entire deployment toolchain. The repository includes CI pipelines, Dockerfiles, and Helm charts that ensure a trusted supply chain for both open-source contributors and enterprise customers.

The Helm chart for OpenWork Enterprise Edition (EE) specifically references the `ghcr.io/different-ai` container registry:

```bash
helm upgrade --install openwork-ee \
  oci://ghcr.io/different-ai/charts/openwork-ee \
  --values values.yaml

```

*Source: packaging/helm/openwork-ee/README.md*

Additionally, [`docs/enterprise/outbound-access.json`](https://github.com/different-ai/openwork/blob/main/docs/enterprise/outbound-access.json) documents the network destinations required by the organization's services, including GitHub releases and Den APIs, providing transparency about the infrastructure footprint controlled by different-ai.

## Summary

- **The different-ai organization** owns the canonical `different-ai/openwork` repository, serving as the project's official maintainer and infrastructure provider.
- **The Den control plane**, including its API and web UI, is built, hosted, and operated by the organization for team-wide OpenWork management.
- **All release artifacts**—desktop binaries, Docker images, and Helm charts—publish exclusively under the different-ai namespace on GitHub and `ghcr.io`.
- **Cloud endpoints** like `api.openworklabs.com/mcp/agent` are maintained by the organization, providing the official integration points for AI agents.
- **Deployment assets** including CI pipelines, Helm charts, and Dockerfiles reside under the organization's governance, ensuring supply chain integrity.

## Frequently Asked Questions

### What specific repositories does the different-ai organization maintain for OpenWork?

The organization maintains the primary `different-ai/openwork` repository, which contains the desktop application source code, the Den control plane components, and all packaging assets including Helm charts and Docker configurations. This repository also hosts the release pipeline for both community and enterprise editions.

### How does the different-ai organization provide the Den control plane for OpenWork?

The organization builds and operates the Den as a cloud-hosted service accessible via `api.openworklabs.com`, providing the API and web UI necessary for managing OpenWork across teams. While the open-source repository contains the code, the hosted Den instances run on infrastructure controlled by different-ai, requiring proper authentication via the organization's MCP endpoints.

### Where does the different-ai organization publish OpenWork release artifacts?

Release artifacts publish to multiple locations under the organization's control: desktop installers upload to GitHub Releases under `different-ai/openwork`, container images push to `ghcr.io/different-ai`, and Helm charts distribute via the organization's GitHub Container Registry at `oci://ghcr.io/different-ai/charts/openwork-ee`.

### Is OpenWork open source if different-ai owns the repository?

Yes, OpenWork is open source under the different-ai organization's stewardship. The organization maintains the open-source codebase while also providing optional hosted services (the Den) that run on their infrastructure. Users can self-host components using the organization's published Docker images and Helm charts, or subscribe to the cloud-hosted Den for managed access.