Skip to content
KaryaFlow OS

Operating models

Licensing and responsibilities

General information about planned operating models; signed terms govern any actual use.

Last updated 29 July 2026

General information

This page explains the intended distinction between KaryaFlow operating models. It is not a licence grant, service commitment or offer to activate production use. Any software rights or managed services require a reviewed written agreement.

One software core

Self-Managed and Evlyr are planned ways to operate the same KaryaFlow core. The difference is who takes responsibility for the environment, implementation, operations and support.

Self-Managed planning

A Self-Managed agreement would need to identify the software version, permitted use, support boundary and the organisation responsible for infrastructure, identity, security operations, monitoring, backups, recovery, upgrades, provider accounts and user support.

Evlyr design partnership

An Evlyr agreement would need to define the managed environment, implementation scope, responsibilities, service commitments, data handling and commercial terms. No SLA or managed-service commitment is created by this website.

Third-party services

Connected providers and bundled third-party components may carry their own terms. Provider accounts, usage charges and rights remain subject to the selected provider and the relevant deployment agreement.

Plan an evaluation

Review Self-Managed planning, explore an Evlyr design partnership, or contact us to discuss evaluation criteria and responsibilities.