# Openwork Project License: Understanding the MIT and Fair Source Dual-Licensing Model

> Understand the Openwork project license, a dual model combining MIT for core code and Fair Source for enterprise features. Learn about its licensing structure.

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

---

**The Openwork project uses a mixed-license model where the core codebase is governed by the permissive MIT License, while the enterprise-only code in the `/ee` directory falls under the more restrictive Fair Source License.**

The different-ai/openwork repository employs a sophisticated dual-licensing approach to balance open-source accessibility with commercial sustainability. Understanding the Openwork project license structure is essential for contributors, integrators, and enterprise users evaluating the codebase for production deployment.

## Mixed-License Model Overview

The repository implements a clear hierarchy of licenses depending on which directory you are working in. According to the source code analysis, the project explicitly separates open-source components from commercial features through directory-based licensing.

### Core Repository: MIT License

All files outside the `/ee` directory and other third-party folders are licensed under the **MIT License**. This permissive, BSD-style license allows free use, modification, distribution, and private or commercial exploitation, provided the copyright notice and permission notice are retained. The full license text resides in the top-level `LICENSE` file at the repository root.

### Enterprise Edition: Fair Source License

The `/ee` directory contains enterprise-only code governed by the **Fair Source License**. This license grants source-code access but limits commercial use without a paid subscription, creating a clear legal boundary between community and commercial functionality.

### Third-Party Components

Dependencies and third-party components maintain their original upstream licenses (e.g., Apache-2.0, BSD-3). These are cataloged in the `NOTICE` file at the repository root, ensuring compliance with upstream requirements.

## Key License Files and Their Locations

Several critical files define the legal framework of the project:

- **`LICENSE`** – Contains the MIT license text for the majority of the codebase and explains the mixed-license model.
- **`ee/LICENSE`** – Houses the Fair Source License governing the enterprise directory.
- **`NOTICE`** – Lists third-party components and their respective upstream licenses.
- **[`package.json`](https://github.com/different-ai/openwork/blob/main/package.json)** – Declares the project's open-source nature and points to the license file for npm tooling compatibility.

## Working with License Information Programmatically

You can access license metadata at runtime or display compliance information in documentation.

### Reading the License at Runtime

When building tooling or admin dashboards around Openwork, you may need to verify the license text programmatically:

```javascript
import { readFileSync } from 'fs';
import { resolve } from 'path';

// Resolve the repository root at runtime (adjust if packaged)
const repoRoot = resolve(import.meta.url, '..', '..');
const licensePath = resolve(repoRoot, 'LICENSE');

const licenseText = readFileSync(licensePath, 'utf8');
console.log('OpenWork License Summary:\n', licenseText.split('\n')[0]); // prints the first line

```

### Displaying License Badges

For documentation or README files, use standard badge syntax to indicate the dual-licensing nature:

```markdown
[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://github.com/different-ai/openwork/blob/dev/LICENSE)
[![License: Fair Source](https://img.shields.io/badge/License-Fair%20Source-blue.svg)](https://github.com/different-ai/openwork/blob/dev/ee/LICENSE)

```

## Summary

- The Openwork project license employs a mixed-model strategy with **MIT** for core code and **Fair Source** for enterprise features.
- The `LICENSE` file at the repository root governs all files outside the `/ee` directory.
- Enterprise functionality in `/ee` requires compliance with the Fair Source License terms.
- Third-party dependencies maintain their original licenses as documented in `NOTICE`.

## Frequently Asked Questions

### Is the Openwork project completely open source?

While the majority of the codebase is open source under the permissive MIT License, the enterprise components in the `/ee` directory use the Fair Source License, which restricts commercial use without a subscription. Third-party dependencies retain their original licenses as specified in `NOTICE`.

### Can I use Openwork commercially without restrictions?

The MIT-licensed core allows commercial use, modification, and distribution without fees. However, any usage of code from the `/ee` directory falls under Fair Source terms, which limit commercial deployment without obtaining a proper license or subscription from the maintainers.

### Where can I find the full license text for the enterprise components?

The complete Fair Source License text is located in `ee/LICENSE` within the repository. This file specifically governs all code contained in the `/ee` directory and related enterprise functionality according to the repository's license hierarchy.

### Do I need to include attribution when using Openwork in my project?

Yes, the MIT License requires retaining the copyright notice and permission notice found in the top-level `LICENSE` file. Additionally, you must comply with any attribution requirements specified in the `NOTICE` file for third-party components and respect the Fair Source restrictions if utilizing enterprise features from the `/ee` directory.