Licensing Details for Archify: MIT License Terms and Usage Rights

Archify is distributed under the MIT License, a permissive open-source license that grants users broad rights to use, copy, modify, merge, publish, distribute, sublicense, and sell the software, provided the original copyright notice and license text are retained.

The repository tt-a1i/archify provides an architecture diagram generation tool released under clear and permissive terms. Understanding the licensing details for archify is essential for developers who want to integrate, modify, or redistribute the code in open-source or proprietary projects.

Understanding the MIT License for Archify

The project uses the MIT License, which is stored in the LICENSE file at the repository root. According to the tt-a1i/archify source code, this file contains the full license text and specifies the copyright holders as © 2026 tt-a1i (Archify) and © 2025 Cocoon AI (for the original "architecture-diagram-generator").

Because MIT is a copy-left-free license, it imposes minimal restrictions on how you can use the software. You may incorporate Archify into proprietary applications without disclosing your own source code, provided you maintain the original attribution.

Permissions and Requirements

The MIT License defines specific permissions you receive and obligations you must fulfill when using the code.

Allowed actions:

• Commercial use without fees or royalties
• Modification and creation of derivative works
• Distribution in source or binary form
• Sublicensing to third parties

Required obligations:

• Include the copyright notices for both tt-a1i and Cocoon AI in all copies
• Include the full license text in any distribution
• State any significant changes made to the software (recommended practice)

The license explicitly disclaims liability, stating the software is provided "as is" without warranty of any kind.

License Files and Locations in the Repository

The licensing details for archify are documented across several canonical files in the repository structure:

• LICENSE — Contains the complete MIT license text and dual copyright notices at /cache/repos/github.com/tt-a1i/archify/main/LICENSE
• README.md — Displays the MIT license badge and links to the license section
• archify/SKILL.md — Confirms the skill contract inherits the same MIT licensing terms
• archify/schemas/README.md — Documents that the JSON schemas are covered by the MIT license

License Badge in Documentation

The README.md file includes a visual indicator referencing the license status:

![License](https://img.shields.io/badge/license-MIT-22c55e?style=flat-square)

You can also reference the license file directly in your documentation:

The project is released under the [MIT License](https://github.com/tt-a1i/archify/blob/main/LICENSE).

Implementing License Compliance

When creating new source files within a fork or redistribution of Archify, include the standard MIT header to ensure clear attribution.

/* 
 * MIT License
 * Copyright (c) 2026 tt-a1i (Archify)
 * Copyright (c) 2025 Cocoon AI (original "architecture-diagram-generator")
 *
 * Permission is hereby granted, free of charge, to any person obtaining a copy
 * of this software and associated documentation files (the "Software"), to deal
 * in the Software without restriction, including without limitation the rights
 * to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
 * copies of the Software, and to permit persons to whom the Software is
 * furnished to do so, subject to the following conditions:
 *
 * The above copyright notice and this permission notice shall be included in
 * all copies or substantial portions of the Software.
 *
 * THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
 * IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
 * FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
 * AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
 * LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
 * FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS
 * IN THE SOFTWARE.
 */

Summary

• Archify is released under the MIT License, a permissive license allowing commercial and private use.
• Copyright holders are tt-a1i (2026) and Cocoon AI (2025); both notices must be preserved in all distributions.
• The canonical license text resides in the root LICENSE file, with additional references in README.md and archify/SKILL.md.
• No source code disclosure is required for proprietary use, but you must retain the original license and copyright notices.
• The software is provided without warranty, and authors assume no liability for claims or damages.

Frequently Asked Questions

Can I use Archify in commercial projects?

Yes. The MIT License explicitly permits commercial use, including selling the software or incorporating it into proprietary products. You do not need to pay fees or obtain additional permissions, but you must include the copyright notices and full license text in your distribution.

What copyright notices must I preserve when redistributing Archify?

You must preserve both copyright notices: © 2026 tt-a1i (Archify) and © 2025 Cocoon AI (original "architecture-diagram-generator"). These notices must appear in all copies or substantial portions of the software, along with the permission notice from the LICENSE file.

Is Archify considered copyleft software?

No. Unlike GPL or other copyleft licenses, the MIT License is copy-left-free. You can integrate Archify into closed-source projects without disclosing your own source code or using the same license for your derivative works. The only requirement is maintaining the original attribution and license text.

Where can I find the official license text?

The official license text is located in the LICENSE file at the root of the tt-a1i/archify repository. You can view it directly at /cache/repos/github.com/tt-a1i/archify/main/LICENSE or via the GitHub web interface. The README.md also contains a link to this file and a license badge for quick reference.

{
  "mcpServers": {
    "instagit": {
      "command": "npx",
      "args": ["-y", "instagit@latest"]
    }
  }
}