Stella Ops Placement Capacity Order

Template. An order made from this template is the accepted order under §2.3 of the Customer Agreement. It is where the purchased production permission is granted. A payment receipt, a product name or a description generated by a merchant of record does not grant or vary it (Customer Agreement §2.2b).

Form Version: 1.0.0 Order reference: [ORDER-ID]

1. Parties

2. Installation

The Installation is one logical control-plane deployment as defined in Additional Use Grant §2 of the LICENSE identified in §9.

3. Permission granted

The Licensor grants the Customer, for the term in §5, the express written permission to make internal production use of the Licensed Work on the Installation in §2, managing up to the authorised Placement capacity in §4 at any time, within the scope in §3a.

3a. Scope

• [ ] Internal production use by the Customer.
• [ ] Production use by the following affiliates, expressly authorised: [names, or “None”]
• [ ] Operation of the Licensed Work as a hosted, managed or other service for third parties, expressly authorised as follows: [description, or “Not authorised”]

Contractors acting for the Customer are covered only as part of the Customer’s own internal use. A provider serving several customers needs its own order.

4. Capacity and price

The fee applies to the authorised capacity as a whole: the first 20 Placements are not deducted. The minimum fee of 25 authorises up to 50 Placements.

Authorised Placement capacity is measured under the Managed Workload and Placement definitions in the identified Additional Use Grant, including qualifying scanning of installed workload images or deployable artifacts and the application of earlier scan results to them. A workload–Environment relationship counts only once even if several qualifying management activities apply to it.

Inadvertent overage. An inadvertent excess over the authorised capacity is additionally authorised for fourteen (14) days after the Customer first becomes aware of it, provided the Customer promptly reduces usage or obtains sufficient authorised capacity through an accepted order. This does not cover deliberate or repeated circumvention. A Placement count observed by the product does not by itself authorise any additional charge.

5. Term, renewal and cancellation

Expiry. The capacity in §4 is authorised for the term only. When the term ends without renewal, this paid permission ends, and production use continues only within the free grant of the LICENSE or another applicable permission. Expiry does not disable delivered software, stop customer workloads, or delete evidence, and it does not withdraw the authorisation that applied during the term.

6. Capacity changes

• Increase. Takes effect through an accepted order. The additional charge is prorated from the effective date of the increase and equals the difference between the old and the new total monthly fee, both calculated with the minimum of 25.
• Decrease. Takes effect at the next renewal.

7. Support reviews

Each review covers one issue identified in the review request and is accepted with an estimated delivery window. Support data is transferred only under the confidentiality and data-protection basis required by Customer Agreement §8.2.

8. Entitlement Record

Purpose and participants. The Licensor may provide a signed Entitlement Record concerning the capacity and term granted under this order and the applicable software licence. The record is supplied for licence administration within the relationship between the Licensor and the Customer identified in this order, using the Installation in §2. Persons administering the Installation on the Customer’s behalf may use the record for that purpose.

Contractual effect. The applicable software licence and this order determine the Customer’s rights. The Entitlement Record is an administrative record of those rights and does not independently enlarge, reduce, amend or replace them. An inaccurate or superseded record is subject to correction.

Local authentication and advisory status. The Installation may authenticate the record locally using the Licensor’s published licence-verification key and display the recorded capacity, term and related advisory information. Authentication concerns the origin and integrity of the Licensor’s record. It does not establish actual usage, the state of a deployment, execution of a scan, the identity or authority of a customer evidence-signing key, or compliance with an obligation. The record’s absence, expiry or indication of excess does not itself cause the software to stop operating; continued technical operation does not alter the rights granted by the applicable licence and this order.

Restricted purpose. The record is not supplied as an assurance credential for independent third-party reliance. The Customer must not present it as vendor verification of customer evidence, customer key ownership, security, compliance or operational events, or use it as an authority in an external evidence-verification chain.

Other disclosures. Nothing in this section prevents disclosure required by law or use of the parties’ contractual records in proceedings concerning their rights. Such disclosure does not expand the record’s stated purpose or constitute a separate assurance service supplied by the Licensor.

9. Incorporated terms

Acceptance of this order and of the Customer Agreement is recorded under Customer Agreement §11.

Form version 1.0.0 | Effective with release v1.0.0-RC1-<YYYYMMDD> (date set at publication) Questions? Contact sales@stella-ops.org