Licensing / two clear paths

Open by default. Commercial when needed.

The Community release candidate is AGPL-3.0-or-later. Commercial agreements cover closed-source use and license-enforced Pro capabilities.

Community Edition

No license fee

The complete core framework under AGPL-3.0-or-later.

  • Memory palace storage and provenance
  • Hybrid retrieval and context assembly
  • Three-layer memory lifecycle
  • CLI, MCP server, FastAPI, and local observatory
  • Optional LangChain and LangGraph adapters
  • Basic encrypted LAN P2P sharing
Deploy Community

Pro Edition

Terms by agreement

Commercial use without AGPL disclosure obligations plus implemented licensed controls.

  • Compliance erasure and audit operations
  • SQLCipher or Fernet encryption at rest
  • Storage-layer multi-tenant isolation
  • Live P2P key rotation and persistent replay protection
  • Priority support and SLA options
  • Long-term support releases
Request a quote
Lummenna Pro brand artwork
Lummenna Pro

01 / Boundaries

Present capability is not roadmap.

Future enterprise work is excluded from current grants until implemented and license-gated.

Edition boundaries reflected by the current entitlement registry.
CapabilityCommunityProCurrent state
Core memory, retrieval, lifecycle, API, dashboardIncludedIncludedImplemented
Closed-source or hosted use without AGPL obligationsNoPer agreementCommercial grant
Compliance erasure and custom PII governanceNoLicensedImplemented and gated
Encryption at restNoLicensedImplemented and gated
Non-default tenant isolationNoLicensedImplemented and gated
Advanced P2P key rotation and durable replay storeNoLicensedImplemented and gated
SSO, scale-out HA, team analytics, PITRNoNot included yetRoadmap, not available

02 / Terms

Questions before deployment.

When is a commercial license needed?
When you need closed-source or hosted use without AGPL obligations, a Pro capability, or your organization prohibits AGPL dependencies.
How is a license verified?
A signed key is supplied through LUMMENNA_LICENSE_KEY and verified locally without a license-server request.
Are roadmap capabilities included?
No. Planned features are not part of a license grant until implemented and entered into the enforceable registry.