The Workflow licence in plain words

This page explains the licence in plain words. It grants no right and changes none: the LICENSE of the version you use, and your Order if you have one, govern.

What is free

  • Production use of an installation with up to 50 Designated Workflows, counted cumulatively, free of charge, as long as the installation is not used to provide a hosted service for third parties.
  • Your own business includes the applications and services you make available to your customers, and workflow configuration your customers perform inside your own application.
  • The Business Source License 1.1 also lets anyone copy, modify and redistribute the code and use it outside production, at any count.

What counts

  • A Designated Workflow is a distinct logical workflow, identified by its name, that has at any time been designated for production use in the installation: through the definition store, the workflow catalogue in code or other production configuration.
  • The count is cumulative. A workflow, once designated, keeps counting: changing the version it runs, removing, replacing or retiring it, or finishing its executions does not lower the count.
  • Versions do not count, and neither do executions, steps, workers or replicas. A workflow registered in code and stored in the definition store counts once; renaming or re-registering the same workflow does not add one.
  • Calling an installation development, test or staging does not exempt its production use. Non-production use needs no order.
  • An installation is one coordinated workflow system: its replicas, workers and failover instances count together, and rebuilding, restoring or migrating it does not reset its count. Genuinely separate systems are separate installations.
  • While you rely on the free use, you count the Designated Workflows yourself, including workflows registered only in code. You do not report the count to us.

A notice level is not a limit

Above 25 recorded workflow names the engine writes an informational notice in its log and its licence status. This technical counter is not the contractual count: it counts the names the engine recorded, including names used only outside production. The notice level is not a limit: crossing it does not mean you need an order, and it creates no fee.

The engine reads its licence status offline and only reports it: it never refuses a registration, an import or an execution, never stops and never contacts us. That it keeps running does not show that a use is permitted: the licence and any Order decide.

If you go over by mistake

An accidental excess over 50 Designated Workflows, or over the capacity your Order authorises, is permitted from its start until 14 days after you first become aware of it. By then, obtain enough capacity or another permission, or stop the production use that nothing covers; removing or retiring workflows does not lower the cumulative count. This does not cover deliberate or repeated circumvention, and crossing the notice level does not start the 14 days.

Embedded in a product you deliver

Embedded use

Under the component Additional Use Grants, you can operate the Router or Workflow engine for your own business within the applicable free limits, or under an applicable standard capacity Order. This includes applications and services used by your customers, subject to the embedded-production boundary below.

These grants do not by themselves authorise production operation of the Router gateway or Workflow engine as an embedded part of a third-party commercial software product. That boundary applies to any such commercial software product, including products that do not compete with a gateway or workflow platform.

Such production use requires express permission in an applicable Order unless another independently applicable licence or permission already authorises it, including an effective Change License.

This boundary concerns production operation. It does not restrict independently available copying, redistribution or non-production permissions, and it does not apply to the packages and corresponding source independently licensed under Apache-2.0 in the accompanying release-specific licensing manifest. Permission to distribute your own application code or workflow definitions does not, by itself, grant permission to operate an embedded server or runtime.

An applicable existing Order can contain the necessary express permission. A separate transaction is unnecessary merely because the permission has a separate scope.

That permission costs nothing: an Order gives it with a no-fee embedded line for each end-customer installation (Customer Agreement, Schedule 3, C.4).

Hosted service for third parties

Providing a general workflow platform on which third parties deploy and operate their own workflows is a hosted service for third parties. It is outside the free use and outside a standard order, and needs an Order that names that permission, its scope and its price; ask for a quote. A contractor that operates your installation on your behalf does not make it a hosted service.

Apache-2.0 packages and the component licence

The Workflow packages carry the Workflow licence. The shared foundation packages they use, such as StellaOps.Canonical.Json and StellaOps.Components.Licensing, carry the Apache License 2.0.

Your workflow definitions and application code are yours: you may write, compile, use and distribute them under terms of your choice, together with the abstraction and contract assemblies they need. Running the engine itself in production stays under the Workflow licence or your Order.

Each Apache-2.0 package carries this statement in its README:

The packages StellaOps.Canonical.Json, StellaOps.Components.Licensing, StellaOps.Cryptography.Abstractions, StellaOps.Cryptography.DefaultProvider, StellaOps.DependencyInjection, StellaOps.Messaging, StellaOps.Messaging.Transport.InMemory, StellaOps.Messaging.Transport.Postgres, StellaOps.Messaging.Transport.Valkey, StellaOps.Microservice, StellaOps.Microservice.AspNetCore, StellaOps.Microservice.SourceGen, StellaOps.Plugin, StellaOps.Router.Common, StellaOps.Router.Transport.InMemory, StellaOps.Router.Transport.Messaging, StellaOps.Router.Transport.RabbitMq, StellaOps.Router.Transport.Tcp, StellaOps.Router.Transport.Tls and StellaOps.Router.Transport.Udp are licensed under the Apache License, Version 2.0. They comprise the shared foundation packages, the general Messaging packages and the Router client packages (the client SDK, the client contracts and the client transports).

The Stella Ops Router gateway, the server transports and the rate-limiting packages, and the Stella Ops Workflow packages, are separate packages. They are licensed under the Business Source License 1.1 with the Additional Use Grant of the Router or Workflow licence. Those licences govern those separate packages only. They place no condition on the use of the Apache-licensed packages.

"Stella Ops" is a trading name of Е-САЛЮШЪНС ЕООД (e-Solutions EOOD). Use of the Licensor's trade names and marks is governed by section 6 of the Apache License, Version 2.0. That section permits use as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file.

Change Date: Apache-2.0 after four years

Each version of the Workflow engine changes to the Apache License 2.0 on its Change Date: the fourth anniversary of that version's first public distribution. Each version has its own date, written into its LICENSE at release.

The licence file

  • An order comes with a vendor-signed licence file, or the same record as a single text value, for the installation. The engine reads it offline, for its licence status and notices only.
  • With a file that matches the installation and covers the running version, “Licensed to” and the name agreed in the Order appear in the engine's SVG diagrams, in its startup log and an hourly log line, and in its health and licence API output.
  • The file records your Order. It grants no right by itself, and a missing file or a notice withdraws no permission. Free use needs no file.

Full licence texts

Each package carries its LICENSE and NOTICE files, with the release fields (version, release tag and commit, Change Date) filled in when the version is released. Until the first release, the licensing guide and Schedule 3 of the Customer Agreement state the terms.