EdictumLicensing
Edictum core is MIT. Edictum Control Plane is FSL-1.1-ALv2 (source-available, converts to Apache 2.0). No per-agent fees, no usage limits, no vendor lock-in.
Right page if: you need to understand the licensing terms for Edictum's core library and control plane before procurement or integration. Wrong page if: you need technical details about what each product does -- see https://docs.edictum.ai/docs/core-vs-control-plane. Gotcha: core library (MIT) has no copyleft obligations. Control Plane (FSL-1.1-ALv2) is source-available with a non-compete clause -- you can use, modify, and self-host freely, but cannot offer a competing product. The license converts to Apache 2.0 after two years.
Core Library — MIT
pip install edictum
The core library is MIT licensed. Use it in commercial, proprietary, or open-source projects without restriction. No copyleft obligations, no attribution requirements beyond the license file.
- Free, no usage limits
- No per-agent fees
- No telemetry or phone-home
- Zero runtime dependencies
Optional Server Surface — FSL-1.1-ALv2
Self-hosted operations surface. The Functional Source License (FSL-1.1-ALv2) applies to the server code.
- Free to self-host, modify, and use for any purpose except building a competing product
- No per-agent fees, no usage limits
- Source is fully available — read, audit, and modify the code
- Converts to Apache 2.0 after two years from each release date — at that point, all restrictions are removed
- No copyleft obligations — you do not have to release your modifications
What counts as a competing use? Offering the control plane (or a substantially similar product) as a commercial service to others. Using it internally, for consulting, or in connection with services you provide to your own customers is explicitly permitted.
Enterprise License
For organizations that need a commercial license without the non-compete clause, dedicated deployment support, SSO/SAML, or SLA-backed support:
Contact hello@edictum.ai.
No Vendor Lock-in
- Rulesets are YAML files you own and version in your repo
- The core library works fully standalone — no server dependency
- The optional server surface is self-hosted — your data stays on your infrastructure
- All audit events are yours — export via OTel, file sinks, or the API
- Switch from control-plane-managed to local rulesets at any time
FAQ
Can I use the core library in a proprietary product? Yes. MIT imposes no restrictions on commercial use.
Do I need to open-source my agent code if I use the optional server surface? No. The FSL has no copyleft clause. Your agent code uses the core library (MIT) and connects to the control plane via API. Neither license requires source disclosure.
What if I fork and modify the optional server surface? You can modify the optional server surface freely for any non-competing purpose. Unlike AGPL, the FSL does not require you to release your modifications. After two years, the Apache 2.0 conversion removes even the non-compete restriction.
Can I self-host the optional server surface for my company? Yes. Internal use is a permitted purpose regardless of company size.
Can I offer the optional server surface as a managed service to other companies? Not under the FSL — that would be a competing use. Contact hello@edictum.ai for a commercial license.
Last updated on