Business Source License 1.1 Parameters Licensor: Е-САЛЮШЪНС ЕООД (e-Solutions EOOD), a company registered in Bulgaria under UIC (EIK) 175177528, with its seat at 61 Bratya Buxton Blvd., Block B, Floor 5, Apt. 7, 1618 Sofia, Bulgaria Licensed Work: Stella Ops Suite (www.stella-ops.org), a product of the Licensor, offered under the trading name "Stella Ops". The Licensed Work is Copyright (c) 2026 Е-САЛЮШЪНС ЕООД (e-Solutions EOOD), UIC (EIK) 175177528. 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. This section 1 does not prohibit using the Licensed Work within your own organization to build, test, release, or deploy your own software, including applications, websites, or APIs made available to your customers or other third parties, merely because those third parties use or benefit from that software. Such use or benefit does not, by itself, constitute a Third Party Service or mean that the Licensed Work is run primarily on their behalf under paragraph (c). This clarification does not permit an offering that otherwise falls within paragraph (a), (b), or (c). 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. 7) Stella Ops Router and Stella Ops Workflow. Use of Stella Ops Router or Stella Ops Workflow as an integrated part of the Stella Ops Suite, to perform Suite functionality under an applicable Suite authorisation, is covered by that authorisation and is not subject to the standalone component's free-use thresholds. Standalone production use of either component is outside this Suite Additional Use Grant. Such use requires permission under the applicable component licence, an applicable commercial order, or another independently available authorisation. Merely installing, registering or connecting a Suite instance does not make an otherwise standalone component deployment an integrated Suite use. Change Date: The earlier of 2030-01-20, or four years from the date of the first publicly available distribution of the specific version of the Licensed Work under this License. Change License: Apache License, Version 2.0 For information about alternative licensing arrangements for the Licensed Work, please contact sales@stella-ops.org. ------------------------------------------------------------------------------- Business Source License 1.1 License text copyright © 2017 MariaDB Corporation Ab, All Rights Reserved. "Business Source License" is a trademark of MariaDB Corporation Ab. Terms The Licensor hereby grants you the right to copy, modify, create derivative works, redistribute, and make non-production use of the Licensed Work. The Licensor may make an Additional Use Grant, above, permitting limited production use. Effective on the Change Date, or the fourth anniversary of the first publicly available distribution of a specific version of the Licensed Work under this License, whichever comes first, the Licensor hereby grants you rights under the terms of the Change License, and the rights granted in the paragraph above terminate. If your use of the Licensed Work does not comply with the requirements currently in effect as described in this License, you must purchase a commercial license from the Licensor, its affiliated entities, or authorized resellers, or you must refrain from using the Licensed Work. All copies of the original and modified Licensed Work, and derivative works of the Licensed Work, are subject to this License. This License applies separately for each version of the Licensed Work and the Change Date may vary for each version of the Licensed Work released by Licensor. You must conspicuously display this License on each original or modified copy of the Licensed Work. If you receive the Licensed Work in original or modified form from a third party, the terms and conditions set forth in this License apply to your use of that work. Any use of the Licensed Work in violation of this License will automatically terminate your rights under this License for the current and all other versions of the Licensed Work. This License does not grant you any right in any trademark or logo of Licensor or its affiliates (provided that you may use a trademark or logo of Licensor as expressly required by this License). TO THE EXTENT PERMITTED BY APPLICABLE LAW, THE LICENSED WORK IS PROVIDED ON AN “AS IS” BASIS. LICENSOR HEREBY DISCLAIMS ALL WARRANTIES AND CONDITIONS, EXPRESS OR IMPLIED, INCLUDING (WITHOUT LIMITATION) WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, NON-INFRINGEMENT, AND TITLE. MariaDB hereby grants you permission to use this License’s text to license your works, and to refer to it using the trademark “Business Source License”, as long as you comply with the Covenants of Licensor below. Covenants of Licensor In consideration of the right to use this License’s text and the “Business Source License” name and trademark, Licensor covenants to MariaDB, and to all other recipients of the licensed work to be provided by Licensor: 1. To specify as the Change License the GPL Version 2.0 or any later version, or a license that is compatible with GPL Version 2.0 or a later version, where “compatible” means that software provided under the Change License can be included in a program with software provided under GPL Version 2.0 or a later version. Licensor may specify additional Change Licenses without limitation. 2. To either: (a) specify an additional grant of rights to use that does not impose any additional restriction on the right granted in this License, as the Additional Use Grant; or (b) insert the text “None”. 3. To specify a Change Date. 4. Not to modify this License in any other way.