Licensing

Aegis uses its own source-available community license plus separate enterprise licensing.

This page explains the intended commercial shape for users and contributors. It is not legal advice. Review LICENSE.md and LICENSE_EE.md for the controlling terms, and consult counsel for production or commercial use.

Summary

• Community source is available under the Aegis Sustainable Use License.
• Personal, non-commercial, and internal business use are free.
• Commercial hosting, resale, embedding, white-labeling, managed customer deployments, and OEM use require a commercial or enterprise license.
• Enterprise-only source files, when present, are governed by LICENSE_EE.md.
• Aegis is source-available/fair-code. It is not OSI-approved open source.

What Is Free

You can use the community edition for:

• personal automation and research;
• local self-hosted agent workflows;
• internal company workflows for your own organization;
• private modifications for personal, non-commercial, or internal business use;
• non-commercial redistribution at no charge, provided license notices remain intact.

What Requires Commercial Permission

You need a separate commercial or enterprise license to:

• sell Aegis as a hosted service;
• host Aegis for customers or client tenants;
• embed Aegis in a commercial product;
• white-label Aegis;
• provide managed Aegis deployments where customers rely on your hosted instance;
• resell, sublicense, or package Aegis as part of a paid product;
• use enterprise-only files or features.

Consulting on a customer’s own Aegis instance may be acceptable under the community license when the customer controls and runs its own deployment, but customer-specific managed hosting or customer-facing access requires commercial review.

Planned Edition Boundary

Community edition should remain genuinely useful:

• local dashboard and command center;
• workflow execution;
• local project runs;
• coding, research, and planner workflows;
• basic connectors;
• local secrets storage;
• approval gates;
• trace and artifact history.

Commercial and enterprise editions may include:

• multi-user teams;
• SSO and directory sync;
• role-based access controls;
• managed backups and retention policies;
• organization-wide audit export;
• enterprise connector governance;
• policy templates;
• private-cloud or managed deployment support;
• commercial hosting, OEM, and embedded rights;
• support SLAs.

Contributor Expectations

Contributions are made under the repository license unless a separate agreement exists. By opening a pull request, you represent that you have the right to contribute the code and that the contribution can be licensed under the applicable Aegis license.

Do not submit third-party code unless its license is compatible with Aegis’s licensing model and attribution requirements are included.

Donations

Donations help support ongoing development but do not change the license terms.

Buying the maintainer a coffee is optional appreciation. It does not grant commercial hosting, embedding, resale, managed customer deployment, OEM, enterprise-feature, support, warranty, or sublicensing rights.

Use a commercial or enterprise agreement for commercial rights.

Naming

Use “fair-code” or “source-available” when describing Aegis licensing. Do not describe Aegis as open source unless the project later adopts an OSI-approved license.