# OpenWork Licensing Details: MIT Core, Fair Source Enterprise, and Third-Party Compliance

> Understand OpenWork licensing: MIT core code, Fair Source License for enterprise features, and third-party compliance. Get the details for the different-ai/openwork repository.

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

---

**The OpenWork project uses a multi-tier licensing model with MIT for core code, Fair Source License (FSL-1.1-MIT) for enterprise extensions in `/ee`, and original licenses for third-party dependencies.**

OpenWork by Different AI employs a carefully structured licensing approach that balances open-source accessibility with commercial protection. This guide breaks down exactly what you can and cannot do with each part of the codebase, citing the actual license files and source locations.

## Core Code: MIT License

All source files **outside** the `/ee` directory are released under the **permissive MIT License**. This is the most liberal open-source license, granting broad rights with minimal requirements.

Specifically, you may:

- Use the software for any purpose, including commercial use
- Copy, modify, and merge the code
- Publish, distribute, and sublicense
- Sell copies of the software

The sole requirement: preserve the original copyright notice and permission statement. The root [LICENSE](https://github.com/different-ai/openwork/blob/dev/LICENSE) file contains the full MIT text governing this portion of the codebase.

```ts
/**
 * Copyright (c) 2026 Different AI
 *
 * Licensed under the MIT License (see the LICENSE file at the repository root).
 */

export function helloWorld() {
  console.log('Hello, OpenWork!')
}

```

## Enterprise Extensions: Fair Source License (FSL-1.1-MIT)

The entire `/ee` directory operates under a custom **"Functional Source License, Version 1.1, MIT Future License"** — abbreviated as **FSL-1.1-MIT**. This is a Fair Source license that restricts certain commercial uses while allowing legitimate internal and research applications.

### Permitted Uses

- Internal business use within your organization
- Non-commercial educational purposes
- Non-commercial research

### Prohibited: Competing Use

The license explicitly forbids **"Competing Use"** — defined as commercial redistribution that substitutes for OpenWork software or any of its future offerings. This protects Different AI's commercial interests while maintaining transparency.

### Two-Year Conversion to MIT

After a **two-year grace period**, FSL-1.1-MIT code automatically converts to standard MIT licensing. This ensures long-term open-source availability while allowing the vendor to monetize new features during their initial development window.

The full terms reside in [ee/LICENSE](https://github.com/different-ai/openwork/blob/dev/ee/LICENSE).

```ts
/**
 * Copyright (c) 2026 Different AI
 *
 * Licensed under the Functional Source License, Version 1.1, MIT Future License
 * (see ee/LICENSE for full terms).
 */

export function enterpriseFeature() {
  // Enterprise-only implementation
}

```

## Third-Party Dependencies: Original Licenses

OpenWork incorporates third-party libraries that retain their **original upstream licenses**. These are preserved in:

- [`package.json`](https://github.com/different-ai/openwork/blob/main/package.json) — lists dependencies with license metadata
- `node_modules` tree — contains full license texts per package

The root LICENSE file explicitly states: *"All third party components ... are licensed under the original license provided by owner of the applicable component."*

## Quick Reference: License Boundaries

| Directory | License | Commercial Use | Key Restriction |
|-----------|---------|--------------|-----------------|
| Root (excluding `/ee`) | MIT | ✅ Full rights | Attribute copyright |
| `/ee` | FSL-1.1-MIT | ❌ Internal only | No "Competing Use" |
| `node_modules` | Various per package | Per upstream license | Compliance with original terms |

## Key Files for OpenWork Licensing Verification

- **[LICENSE](https://github.com/different-ai/openwork/blob/dev/LICENSE)** — MIT terms for core code; gateway reference to enterprise license
- **[ee/LICENSE](https://github.com/different-ai/openwork/blob/dev/ee/LICENSE)** — Complete FSL-1.1-MIT text for `/ee` directory
- **[package.json](https://github.com/different-ai/openwork/blob/dev/package.json)** — Dependency list with license information
- **[README.md](https://github.com/different-ai/openwork/blob/dev/README.md)** — Project overview with licensing summary

## Summary

- **MIT License** covers all core code outside `/ee`, enabling unrestricted commercial and non-commercial use with attribution
- **Fair Source License (FSL-1.1-MIT)** governs the `/ee` enterprise directory, permitting internal use and non-commercial research while blocking competing commercial redistribution
- **Automatic conversion** converts FSL-1.1-MIT code to MIT after two years
- **Third-party dependencies** maintain their original licenses, requiring separate compliance verification
- **Clear file structure** separates license tiers: check directory location to determine applicable terms

## Frequently Asked Questions

### Can I use OpenWork commercially without paying?

**Yes, for the core codebase.** The MIT-licensed portion outside `/ee` permits full commercial use, modification, and distribution. Only the `/ee` enterprise directory restricts commercial redistribution through the Fair Source License.

### What happens to Fair Source code after two years?

**It becomes MIT-licensed.** The FSL-1.1-MIT license includes an automatic conversion clause: two years after release, the code transitions to standard MIT terms, allowing unrestricted commercial use including competing products.

### Do I need to disclose my modifications to OpenWork?

**Only for the MIT portions, and only via attribution.** The MIT License requires preserving copyright notices but does not impose copyleft requirements. Modified versions need not be open-sourced. Fair Source code in `/ee` carries the same attribution requirement but adds the non-compete restriction during its initial two-year period.

### How do I identify which license applies to a specific file?

**Check the file path.** Files in `/ee` — including subdirectories — fall under FSL-1.1-MIT. All other source files use MIT. When in doubt, examine the nearest `LICENSE` file: `ee/LICENSE` for enterprise code, root `LICENSE` for everything else.