Additional permission for earlier versions of Stella Ops Suite

Issued by: Е-САЛЮШЪНС ЕООД (e-Solutions EOOD), UIC (EIK) 175177528, the Licensor named in LICENSE. Effective Date: the publication date of release v1.0.0-RC1-<YYYYMMDD> (date set at publication). Before that date this document has no effect. Annex A identity: the Additional Use Grant of release v1.0.0-RC1-<YYYYMMDD>, carried in a LICENSE file with SHA-256 9febee768b22bdc8c688ea89da04673eb8fe7a8af2ba034581b9cf9498d6d35d. The Annex A text below has SHA-256 578649f131556a8dfd1ee99a30a1b777c217a5b412320f93613d1a46a9f7b7ac.

Permission

For each version of the Licensed Work first distributed by the Licensor before the Effective Date, the Licensor additionally permits recipients to use that version under the Additional Use Grant reproduced in Annex A, subject to the conditions of that grant.

This permission supplements and does not withdraw or vary permissions already applicable to that version. A recipient may rely on either applicable grant in its entirety for the relevant use; conditions from different grants may not be combined to create a permission neither grant provides.

The original version’s Change Date and Change License remain unchanged.

What this means in practice

This section explains the permission above. It does not change it.

Nothing is withdrawn. Each earlier version stays under the LICENSE it shipped with. The LICENSE in the published v1.0.0 and v1.0.1 images limits each Installation to three Environments and one hundred New Hash Scans in any rolling 24-hour period. What earlier publications carried is recorded in the historical distribution evidence.
Earlier statements are preserved as distributed. The Community Plugin Grant Addendum 1.0.0 distributed with some earlier versions states three Environments and 999 Scans per calendar day for Plugins. The Licensor corrects that inconsistency prospectively, in Addendum 2.0.0. It does not treat the earlier statement as ineffective, and it assesses a recipient’s actual grant before asserting non-compliance or requesting payment.

Neither grant is always more generous. That is why both stay available:

Estate	Earlier environment-based grant	Annex A placement grant
30 services × 3 environments = 90 placements	Potentially free, subject to the applicable scan limit and other conditions	Requires paid capacity
5 services × 4 environments = 20 placements	Exceeds the three-environment limit	Within the free placement limit
15 services × 4 environments = 60 placements	Exceeds the three-environment limit	Requires paid capacity

One grant at a time. A recipient cannot combine, for example, the earlier grant’s unlimited services with Annex A’s unlimited environments.

Annex A — Additional Use Grant (immutable)

The text between the markers is the Additional Use Grant of release v1.0.0-RC1-<YYYYMMDD>, unchanged. Its SHA-256 is taken over the lines from Additional Use Grant: to the line ending Change License., with LF line endings and one trailing LF. To check it against a LICENSE file of that release:

sed -n '/^Additional Use Grant:/,/Change License\.$/p' LICENSE | sha256sum
# expected: 578649f131556a8dfd1ee99a30a1b777c217a5b412320f93613d1a46a9f7b7ac

Additional Use Grant:
    You may make production use of the Licensed Work, free of charge, provided
    that you comply with ALL of the following conditions:

    1) No SaaS / No Hosted or Managed Service for Third Parties.
       You may not use the Licensed Work to provide a hosted service, managed
       service, service bureau, or any other software-as-a-service offering to
       third parties.

       For purposes of this grant, a "Third Party Service" means any offering
       in which a person or entity other than your own organization (including
       your Affiliates, and your and their employees and contractors) directly
       or indirectly:
         (a) accesses the functionality of the Licensed Work (including via a
             network, API, web UI, or automated access); OR
         (b) receives the results/outputs of the Licensed Work as a service; OR
         (c) benefits from the Licensed Work being run primarily on that third
             party's behalf (including scanning, analysis, or reporting).

       "Affiliate" means any entity that controls, is controlled by, or is
       under common control with you.

    2) Free Usage Limit — per Installation.
       When relying on the free production permission provided by this
       Additional Use Grant, each Installation may manage no more than twenty
       (20) active Placements at any time, except to the extent that
       additional capacity is expressly authorised by the Licensor.

       Definitions for this grant:
         - "Installation" means a single logical control-plane deployment of
           the Licensed Work's server components operated by or for a single
           legal entity. Cluster nodes, database replicas and failover
           components that form the same deployment together count as one
           Installation. Independently operated deployments are separate
           Installations.

         - "Environment" means a distinct release-control or deployment
           destination managed by the Installation. A tenant, workspace or
           project does not create an additional Environment merely because it
           is an organisational label. The number of Environments is not
           limited.

         - "Managed Workload" means an application workload — a container
           service, or an artifact deployed to a host — whose releases the
           Installation gates, promotes or deploys, or whose image the
           Installation scans while that image is installed in an Environment
           of the Installation. Scanning an image that is installed in no
           Environment creates no Placement.

         - "Placement" means one active Managed Workload–Environment
           relationship, identified consistently across releases and versions.
           A Placement counts whether the Installation performs the deployment
           itself or gates or promotes a release deployed by another tool.
           Replicas, restarts, redeployments, image or version changes, and
           multiple files that form one native workload do not create
           additional Placements, and neither do scans or reports. Components
           of the Licensed Work itself are not Placements.

         - A Placement ends when management of that Managed Workload in that
           Environment actually ends. Retaining historical evidence about it
           does not keep it active.

       An inadvertent excess over the applicable Placement capacity is
       additionally authorised for fourteen (14) days after you first become
       aware of it, provided you promptly reduce usage or obtain sufficient
       authorised capacity. This permission does not cover deliberate or
       repeated circumvention.

    3) Plugins (free to build and distribute).
       You may develop, use, publish, and distribute plugins, extensions,
       connectors, and integrations ("Plugins") that interoperate with the
       Licensed Work through the Licensed Work's public plugin interfaces.

       You do not need to pay the Licensor to create or distribute Plugins.
       You may license Plugins under terms of your choice (including proprietary
       terms), PROVIDED that the Plugin does not include, copy, or modify any
       portion of the Licensed Work's source code.

       A Plugin that includes, copies, or modifies any portion of the Licensed
       Work is a derivative work of the Licensed Work and is subject to this
       License.

    4) Production use outside this Additional Use Grant.
       Production use not permitted by this Additional Use Grant or another
       independently applicable licence permission requires the Licensor's
       express written permission. That permission may be provided through an
       accepted order under the Licensor's Customer Agreement specifying the
       authorised Installation, Placement capacity, permitted use and
       applicable period.

       A standard Placement subscription authorises internal production use
       within its stated scope. Operating the Licensed Work as a hosted,
       managed or other service for third parties requires express
       authorisation for that activity in the applicable order.

    5) Community Plugin Grant Addendum.
       See LICENSE-ADDENDUM-COMMUNITY-PLUGIN-GRANT.md, distributed with the
       same version of the Licensed Work, for additional terms governing
       plugin development, distribution, and community use.

    6) Other permissions preserved.
       This Additional Use Grant provides permissions additional to those
       independently granted by the Business Source License 1.1. Its
       conditions do not restrict rights independently available under that
       licence or under the applicable Change License.