What is the License for Archify? MIT License Terms Explained

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 in all copies or substantial portions.

Archify, hosted at tt-a1i/archify on GitHub, is released under one of the most permissive open-source licenses available. The MIT License allows both personal and commercial use with minimal restrictions, making it ideal for integrating into proprietary projects. Understanding the specific terms and attribution requirements ensures compliance when using or redistributing this architecture diagram generator.

MIT License Permissions and Grant of Rights

According to the LICENSE file in the repository root, the MIT License grants extensive freedoms to users of Archify. You are explicitly permitted to:

• Use the software for any purpose, including commercial applications
• Copy, modify, merge, and publish derivative works
• Distribute, sublicense, and sell copies of the software
• Permit others to do the same

The license covers the entire codebase, including original work derived from the "architecture-diagram-generator" by Cocoon AI. The copyright notices specify: © 2026 tt-a1i (Archify) and © 2025 Cocoon AI (original "architecture-diagram-generator"). These dual copyright notices must be preserved in any redistribution or substantial use of the code.

Compliance Requirements and Legal Obligations

While the MIT License imposes minimal restrictions, specific conditions must be met to maintain legal compliance. The license requires that you include the above copyright notice and the full permission notice in all copies or substantial portions of the software. This applies to both source code distributions and compiled binary releases.

The software is provided "as is" without warranty of any kind, express or implied. The authors expressly disclaim liability for any claim, damages, or other liability arising from the use or distribution of the software. Because the MIT License is copy-left-free, you may incorporate Archify into proprietary closed-source projects without disclosing your own source code, provided you retain the original attribution notices.

Locating License Information in the Repository

Several files throughout the tt-a1i/archify repository contain licensing information and attribution requirements.

The LICENSE File

The root-level LICENSE file contains the complete MIT license text, including both copyright notices for tt-a1i and Cocoon AI. This file serves as the authoritative source for all legal terms governing the use, modification, and redistribution of Archify.

README.md License Badge

The README.md file displays a license badge referencing the MIT license and links directly to the license section. This provides immediate visual confirmation of the project's open-source status and offers quick navigation to the full legal text at the repository root.

Supporting Documentation Files

Additional project components inherit the same MIT licensing terms:

• archify/SKILL.md - Describes the skill contract and operates under the MIT License
• archify/schemas/README.md - Documents JSON schemas and is explicitly covered by the MIT License

These files ensure consistent licensing across all components and documentation within the Archify project.

Proper Attribution Examples

When incorporating Archify into your own projects, use these templates to ensure proper attribution and compliance.

Adding the MIT Header to Source Files

Include this header at the top of any source files derived from or incorporating Archify code:

/* 
 * 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.
 */

Displaying the License Badge in Documentation

For Markdown-based project documentation, include the official MIT license badge to signal compliance:

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

Referencing the License in Documentation

When mentioning Archify in your project attribution or documentation files, link directly to the license:

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

Summary

• Archify uses the MIT License, a permissive open-source license allowing unrestricted commercial use, modification, and distribution.
• Dual copyright holders must be acknowledged: © 2026 tt-a1i (Archify) and © 2025 Cocoon AI (original architecture-diagram-generator).
• Attribution requirements mandate preserving both copyright notices and the full permission text in all redistributions, whether source or binary.
• Copy-left-free status enables integration into proprietary projects without requiring source code disclosure or license inheritance.
• License documentation is available in LICENSE, README.md, archify/SKILL.md, and archify/schemas/README.md.

Frequently Asked Questions

Is Archify free for commercial use?

Yes, the MIT License explicitly permits commercial use without fees, royalties, or usage restrictions. You can deploy Archify in commercial products, SaaS platforms, or enterprise environments. The only requirement is retaining the original copyright notices and license text in your distribution or documentation.

Do I need to open-source my project if I use Archify?

No. The MIT License is non-viral and copy-left-free, meaning you are not obligated to disclose your source code or apply the MIT License to your own work. You may incorporate Archify into closed-source proprietary projects, provided you include the MIT license notice and both copyright attributions for the Archify components you use.

Who holds the copyright for Archify?

Copyright is held by two entities: tt-a1i holds the copyright for the Archify project (© 2026), while Cocoon AI retains copyright for the original "architecture-diagram-generator" codebase (© 2025). Both copyright notices appear in the LICENSE file and must be preserved together when redistributing any portion of the software.

Where can I find the full license text for Archify?

The complete MIT license text is located in the LICENSE file at the repository root. You can access it directly at https://github.com/tt-a1i/archify/blob/main/LICENSE. Additionally, the README.md contains a license badge and section link, while archify/SKILL.md and archify/schemas/README.md confirm that those components operate under the same MIT licensing terms.

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