# different-ai/openwork License: Complete Guide to MIT and Fair Source Licensing

> Understand the different-ai/openwork license. Discover the MIT and Fair Source licensing details for core code and enterprise features. Get the full guide here.

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

---

**The different-ai/openwork repository uses a dual-license model: MIT License for the core codebase and Functional Source License (FSL-1.1-MIT) for the enterprise `/ee` directory, with third-party dependencies retaining their original licenses.**

OpenWork, developed by Different AI, implements a **multi-tier licensing structure** designed to balance open-source accessibility with commercial protection. This article breaks down the exact licensing terms, file locations, and implications for developers using or contributing to the project.

## Core Code: MIT License

All source files **outside** the `/ee` directory fall under the permissive **MIT License**. This includes the majority of the OpenWork functionality available to the general public.

According to the [LICENSE](https://github.com/different-ai/openwork/blob/dev/LICENSE) file at the repository root, the MIT terms grant you the right to:

- Use, copy, modify, and merge the software
- Publish, distribute, sublicense, and/or sell copies
- Include in private or commercial projects

The only requirement is retaining the original copyright notice and permission statement in all copies or substantial portions of the software.

### MIT License Header Example

When adding new files to the MIT-licensed portion of the codebase, use this header format:

```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 `/ee` directory is governed by a custom **"Functional Source License, Version 1.1, MIT Future License"** (abbreviated **FSL-1.1-MIT**). This Fair Source model creates a transition path from protected to fully open source.

The [ee/LICENSE](https://github.com/different-ai/openwork/blob/dev/ee/LICENSE) file specifies:

| Permission | Condition |
|------------|-----------|
| Internal business use | Allowed |
| Non-commercial education | Allowed |
| Non-commercial research | Allowed |
| **Competing Use** | **Explicitly forbidden** |

**Competing Use** is defined as commercial redistribution that substitutes the OpenWork software or any of its future offerings.

After a **two-year grace period**, code in `/ee` automatically converts to MIT License, matching the core codebase terms.

### Fair Source License Header Example

For files inside the `/ee` directory, apply this header:

```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

Any external libraries included in the repository retain their **original licenses**. The top-level `LICENSE` file explicitly states: "All third party components ... are licensed under the original license provided by the owner of the applicable component."

Dependency licenses are tracked in:

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

You must comply with upstream terms when distributing derivative works.

## License Boundaries at a Glance

- **MIT License** → Root-level source files, general functionality, broad adoption encouraged
- **FSL-1.1-MIT** → `/ee/*` enterprise features, commercial use restricted initially, converts to MIT after 2 years
- **Original licenses** → All `node_modules` dependencies, compliance required per-package

## Key License Files

| File | Purpose |
|------|---------|
| `LICENSE` (root) | MIT terms for core code, pointer to enterprise license |
| `ee/LICENSE` | Full FSL-1.1-MIT text for `/ee` directory |
| [`package.json`](https://github.com/different-ai/openwork/blob/main/package.json) | Dependency manifest with license metadata |
| [`README.md`](https://github.com/different-ai/openwork/blob/main/README.md) | Project overview with licensing summary |

## Summary

- **different-ai/openwork** combines **MIT** and **Fair Source** licensing in a single repository
- Core functionality is fully open source under MIT — free for any use with attribution
- Enterprise features in `/ee` are **FSL-1.1-MIT**: free for internal, educational, and research use, but restricted from competing commercial redistribution
- All `/ee` code becomes **MIT-licensed automatically after 2 years**
- Third-party dependencies are **not re-licensed** — verify individual package terms in [`package.json`](https://github.com/different-ai/openwork/blob/main/package.json)

## Frequently Asked Questions

### What is the different-ai/openwork license for commercial use?

The core codebase under MIT License permits commercial use without restriction. The `/ee` enterprise directory permits internal commercial use but forbids "Competing Use" — creating redistributed products that compete with OpenWork. After two years, `/ee` code converts to MIT and full commercial use is allowed.

### Can I fork and modify the openwork repository?

Yes. The MIT License explicitly grants the right to fork, modify, merge, and redistribute the core code. For `/ee` content, you may fork and modify for internal use, education, or non-commercial research, but cannot distribute competing commercial products until the two-year conversion period expires.

### What happens to the /ee license after 2 years?

Per the FSL-1.1-MIT terms, code in the `/ee` directory automatically converts to MIT License after a 24-month period from release. At that point, all MIT permissions apply including unrestricted commercial use, sublicensing, and resale.

### How do I check if a specific file is MIT or Fair Source licensed?

Check the file path. Any file inside the `ee/` directory is FSL-1.1-MIT. All other source files default to MIT License as specified in the root `LICENSE` file. The license header comment in each file also indicates its governing terms.