License FAQ (AGPL v3)
Actyze is fully open source under the GNU Affero General Public License v3.0 (AGPL-3.0). There are no license keys, no feature gates, and no activation steps. Just docker-compose up and go.
Do I need a license key to use Actyze?
No. Actyze is free and open source. There are no license keys, activation codes, or feature restrictions. Every feature is available to everyone, unlimited.
How do I install Actyze?
Community edition (self-hosted): No license needed. Just run:
git clone https://github.com/actyze/dashboard-docker.git
cd dashboard
./docker/start.sh
That's it. All features are enabled by default.
Managed deployment (BYOC): If you want Actyze deployed and managed in your own cloud account (Bring Your Own Cloud), contact us for details.
Can I use Actyze internally at my company?
Yes, absolutely. You can deploy and use Actyze within your organisation for free, with no obligations. The AGPL only triggers when you distribute the software or provide it as a network service to external users.
Can I modify Actyze for internal use?
Yes. You are free to modify the source code to fit your internal needs — add integrations, change the UI, write custom plugins. As long as the modified version is only used internally by your employees, you have no obligation to share your changes.
Can I offer Actyze as a SaaS product?
Yes, with conditions. If you run a modified version of Actyze as a network service available to users outside your organisation (i.e., as a SaaS), the AGPL requires you to make the complete source code of your modified version available to those users.
If you prefer not to open-source your modifications, a commercial license is available that removes this requirement. Contact us for details.
Can I embed Actyze in my product?
Yes, with conditions. Embedding Actyze (or a modified version) in a product that you distribute or offer as a service to third parties triggers the AGPL's source-sharing requirements. You must make the source code available to your users.
Alternatively, a commercial license lets you embed Actyze without the AGPL obligations. Contact us for details.
Do I need to contribute my changes back to the Actyze project?
No. The AGPL requires you to share source code with your users (the people who interact with your deployment), not with the upstream Actyze project. That said, we welcome and encourage contributions — they help the entire community.
What about the old license key system?
Actyze previously used a license key activation system. That system has been completely removed. If you see references to Actyze_LICENSE_KEY or license validation endpoints in older documentation, they are outdated. Current versions of Actyze have no license enforcement whatsoever.
Summary
| Use Case | Obligation | Cost |
|---|---|---|
| Internal use (unmodified or modified) | None | Free |
| Self-hosted for your own employees | None | Free |
| Offered as a SaaS to external users | Share source with those users (or buy a commercial license) | Free (AGPL) or paid (commercial) |
| Embedded in a distributed product | Share source with recipients (or buy a commercial license) | Free (AGPL) or paid (commercial) |
| Contributing changes upstream | Appreciated but not required | Free |
| Managed deployment (BYOC) | None | Contact us |
Still have questions?
Reach out at hello@actyze.ai or visit actyze.ai/contact.