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 ebd869191b46c2be818695ec338dbd95a083330fe2ceddad8c05b821bb714e3a. The Annex A text below has SHA-256 54a28530095cc00c87b719c2f77f34c2e4dba59bec85f1b74460a56408f4d99c. The complete LICENSE with that SHA-256 is distributed in release v1.0.0-RC1-<YYYYMMDD> (its bundle and images) and is retained byte-exact in that release’s source at docs/legal/busl/licence-texts/ebd869191b46c2be818695ec338dbd95a083330fe2ceddad8c05b821bb714e3a.txt.
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
LICENSEit shipped with. TheLICENSEin the publishedv1.0.0andv1.0.1images limits each Installation to three Environments and one hundred New Hash Scans in any rolling 24-hour period. Source distributed from 2026-10-27 until the Effective Date carries an earlier Placement grant (LICENSESHA-2569febee768b22bdc8c688ea89da04673eb8fe7a8af2ba034581b9cf9498d6d35d) and stays under it; this permission is available for that source too. 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: 54a28530095cc00c87b719c2f77f34c2e4dba59bec85f1b74460a56408f4d99c
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 a native application workload comprising one or more
deployable artifacts — for which the Installation either (a) gates,
promotes or deploys releases, or (b) scans an image or deployable
artifact or applies the results of an earlier scan to it while that
image or artifact is installed as part of that workload in an
Environment of that Installation.
- An image or deployable artifact is "installed" in an Environment
when it forms part of a deployed application workload assigned to
that Environment, whether the workload is currently running or
temporarily stopped. Merely storing an image or artifact in a
registry, cache, backup or unused local store does not constitute
installation, including when the files remain after the workload
has been removed or retired.
- The Installation "applies the results of an earlier scan" when it
associates, presents or uses those results as applicable scan
information for a workload whose image or deployable artifact is
installed in an Environment of that Installation. Merely retaining,
retrieving, exporting or displaying a report solely as historical
evidence, without such application to an installed workload, does
not qualify. An operator's reading or use of a report outside the
Installation does not, by itself, qualify.
- "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. It
also counts when the Installation scans, or applies the results of
an earlier scan to, the workload's image or deployable artifact
while it is installed as part of that workload in that Environment.
- Replicas, restarts, redeployments, image or version changes, and
multiple files that form one native workload do not create
additional Placements. Repeated scans and reports do not create
additional Placements for a workload–Environment relationship
already counted. A qualifying scan, or a qualifying application of
an earlier scan's results, may bring a previously uncounted
workload–Environment relationship into the Placement count. A
relationship that qualifies through more than one management
activity counts once. Components of the Licensed Work itself are
not Placements.
- Where a qualifying scan or application of earlier scan results
concerns an image or deployable artifact installed as part of more
than one workload–Environment relationship within that
Installation, each such relationship counts separately. Image or
artifact digests identify the installed content; they do not
replace workload or Environment identities.
- Scanning an image or deployable artifact installed in no
Environment of that Installation does not, by itself, create a
Placement.
- Installed workload–Environment relationships may be established
from deployment records, connected inventory or the operator's
supplementary declaration. For purposes of this Additional Use
Grant, you must include in the Placement count every qualifying
relationship, including those not reflected in the automatic
inventory. Loss of observation alone does not establish that a
workload has been uninstalled or withdrawn from management.
- A Placement ends when all management of that Managed Workload in
that Environment actually ends, or when the workload is removed and
no other management activity keeps the relationship active.
Completion of a scan does not by itself end a Placement. Retaining
historical evidence or reports does not, by itself, create,
reactivate or keep a Placement 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.