Skip to content
KaryaFlow OS

Community and commercial boundary

Licensing without the fog machine

KaryaFlow Community declares AGPL-3.0-only source and an intended deployable-appliance release contract. Commercial services, genuinely separate modules and the brand have distinct boundaries.

Last updated 22 July 2026

KaryaFlow Community core

This repository declares the KaryaFlow Community core under the GNU Affero General Public License version 3, identified as AGPL-3.0-only, for material the project is authorised to license. Subject to that licence, recipients may run, study, copy, modify and redistribute the covered code.

The licence text in the source repository is authoritative for covered material. A licence file does not cure missing ownership or third-party permissions. Read the official GNU AGPL text; this page is a practical product boundary, not legal advice.

Modified network versions

AGPL section 13 adds a network-use condition. If you modify the covered program and let users interact with that modified version remotely, the program must offer those users an opportunity to receive the corresponding source for that version, without charge, through a standard network method.

Copyright and licence notices, source-offer behaviour and corresponding-source obligations must be preserved as the licence requires. Installing unmodified KaryaFlow for your own business does not transfer ownership of your business data to the project.

Source plus deployable appliance

The intended Community release contract is public source paired with a realistic installation path: versioned container images, Docker Compose, guided configuration, diagnostics, backup, restore, upgrade, sample data, deterministic troubleshooting and full export.

No public release is currently certified. Release claims are evidence-bound: an image is described as official, signed or reproducible only when the exact release tag and digest carry that evidence. See Product availability for the current boundary.

Evlyr and commercial modules

Evlyr's management or control plane, implementation services and genuinely separate premium adapters or modules may be supplied under proprietary commercial terms only where the supplier holds all rights needed to do so. Merely calling code a separate module does not remove AGPL obligations from a combined or derivative work, and the commercial layer does not change the AGPL licence on covered Community code.

Customer-specific configuration and business data remain customer-owned subject to the applicable agreement. Rights in generic extensions funded by a customer must be stated in that agreement; no ownership transfer or proprietary-module availability should be inferred from this page.

Names and logos

The code licence does not grant permission to brand a modified product or hosted service as KaryaFlow or Evlyr. Truthful references to the Community project are addressed by the separate TRADEMARKS.md policy shipped with the source, subject to applicable law.

A materially modified fork should use a distinct name and logo and must not imply endorsement, certification or official support.

Contributions and dual licensing

The project intends to require a contributor licence agreement that allows accepted contributions to remain in the AGPL Community edition while permitting the project steward to relicense them. Contributors retain ownership of their work.

External code intake is currently closed because the receiving legal entity and counsel-approved signing workflow have not been finalised. A pull request alone is not treated as consent to unfinished terms.

Provenance and dependency status

The repository was separated from a larger system. Its first public release remains gated on a path-level copyright, provenance, asset and dependency-licence audit. The presence of an AGPL file does not prove that the project can relicense material it does not own.

Qualified Indian software-IP counsel should review ownership assignments, the dual-licensing structure, contribution agreement and notices before release. No provenance-complete claim is made here.

Questions about a specific use?

Review the official AGPL text, the licence file shipped with the source and this deployment's corresponding-source status. The reserved legal@karyaflow.com receipt path is not yet release-verified, so do not rely on it until a verified contact is published. Obtain your own legal advice for a deployment or redistribution decision.