BY DEPLOYING, INSTALLING, OR ACCESSING THE ORION OS ARCHITECTURE — ORGANIZATIONAL RESOURCE & INTEGRATED OPERATIONS NETWORK ("THE SOFTWARE") — THE ENTITY ("THE LICENSEE") ACCEPTS THE TERMS OF THIS COMMISSION.
Deployment Record // Complete All Fields
| Field | Entry |
|---|---|
| Licensee (Entity / Organization) | |
| Authorized Representative | |
| Contact (Email / Comms) | |
| Tenant Slug | |
| Instance / License Key ID | |
| Licensed Major Version | |
| Activation Date | |
| Expiration Date (Activation + 1 Year) | |
| License Class (select one) | ☐ Standard Commission — $50 ☐ Operational Sustainment — $15 ☐ Evolutionary Upgrade — $35 |
I. The Commission (Grant of License)
1.1. Term-Limited Authorization
The Licensor grants The Licensee a non-transferable, non-exclusive license to operate the Current Generational Release of the ORION OS environment for a period of one (1) solar year from the date of activation.
1.2. Operational Scope (The Core Suite)
This license authorizes access to the full command suite as defined in the deployment manifest at the time of purchase. This includes, but is not limited to, modules for Operations, Dispatch, Roster, Comms, Calendar, Civitas, Intel, and Fleet Command, together with the companion Discord integration where provisioned. The exact application set available to The Licensee is governed by the licensed Major Version and the per-app permission grants configured within the instance.
1.3. Dedicated Instance & Data Sovereignty
Each deployment operates against a dedicated database account that The Licensee creates, owns, and controls. The Licensee provisions this database using tooling supplied by the Licensor and grants the Licensor connection credentials solely so the Software can operate against it. The Licensee may revoke or rotate those credentials at any time. The Licensee retains ownership of its database account and all organizational data within it. The Licensor retains all right, title, and interest in the Software, including its source code, schema, architecture, and design patterns. ORION OS is licensed, not sold.
1.4. Licensor Commitments
In exchange for the commission fee, the Licensor commits, for the duration of the term, to: (a) operate and maintain the platform and deliver the updates applicable to the license class; (b) respond to security defects with priority over feature work; (c) issue the Renewal Advisory described in Section V; (d) never sell, rent, or disclose Licensee data to third parties, display advertising within the Software, or access one tenant's data on behalf of another; and (e) handle data in accordance with the ORION OS Privacy Notice (OPN-1). Because The Licensee owns its database account outright, no event under this license — including expiration, non-renewal, or termination — deprives The Licensee of possession of its own data.
II. License Classes & Fees
2.1. Commission Schedule
Each commission is executed under one of the following license classes, as designated in the Deployment Record above. Fees fund the hosting, infrastructure, and continued development described in Section 1.4; they purchase platform operation, never custody of The Licensee's data:
| Class | Fee | Term | Entitlement |
|---|---|---|---|
| Standard Commission | $50 | 1 year | New deployment. Full Core Suite at the designated Major Version, including all intra-generational updates. |
| Operational Sustainment | $15 | 1 year | Renewal of an existing commission at the same Major Version. Includes security patches only; no feature additions. |
| Evolutionary Upgrade | $35 | 1 year | Unlocks the next Major Version generation and commences a new one-year term with full intra-generational updates. |
III. Evolution & Versioning Protocols
3.1. Incremental Maintenance (Intra-Generational)
Under a Standard Commission or Evolutionary Upgrade, all minor evolutionary steps within the active Major Version (e.g., vX.1, vX.2, vX.5) are included at no additional operational cost. These updates are automatically authorized to ensure system stability and security. Under Operational Sustainment, authorization is limited to security patches.
3.2. Generational Shifts (Cross-Generational)
This license is strictly bound to the Major Version generation designated at the time of initialization. Major generational leaps (e.g., upgrading from vX.0 to vY.0) are classified as new deployments. Access to future Major Version features and enhancements requires the purchase of an Evolutionary Upgrade license.
IV. Architectural Restrictions
4.1. Integrity of the Core
The Licensee shall not:
- Deconstruct: Reverse engineer, decompile, or disassemble the source code.
- Misappropriate: Copy the UI/UX design patterns for use in competing products.
- Subvert: Bypass security protocols, authentication gates, permission engine controls, or license verification modules.
- Re-Tenant: Sublicense, resell, or provision access to the instance for any organization other than the named Licensee.
V. Expiration & Renewal Cycle
5.1. The Expiration Horizon
The System is programmed to issue an automated "Renewal Advisory" to The Licensee thirty (30) days prior to the license expiration date.
5.2. The Grace State (Post-Expiration)
Upon expiration of the 1-year term, if no Operational Sustainment renewal or Evolutionary Upgrade is executed, The System will enter a Restricted Operation Mode (Grace State) for a duration of 14 days.
- Status: READ-ONLY (platform access).
- Capabilities: The Licensee may view and export data through the platform but may not input new commands, modify rosters, or assign assets. The Licensee's own database account remains fully under its direct control at all times, independent of platform status.
5.3. Terminal Shutdown
Following the conclusion of the 14-day Grace State, the instance will automatically decommission. Decommission revokes platform access and deletes the connection credentials and platform-side records held by the Licensor; it does not affect The Licensee's database account, which remains in The Licensee's possession together with all data in it. Platform access is restored when a new license key is provisioned.
VI. Third-Party Compliance (CIG)
6.1. Star Citizen / RSI Relation
The Licensee acknowledges that ORION OS is a third-party tool developed for the Star Citizen community.
- Fan Content Policy: Usage is subject to the Cloud Imperium Games (CIG) Fan Content Policy.
- Non-Affiliation: ORION OS is not an official CIG product.
VII. Operational Warranty (Disclaimer)
7.1. "As Is" Deployment
The Software is provided "AS IS." The Licensor makes no warranty that the software will be error-free or that access will be uninterrupted by changes in the Star Citizen backend API or third-party service providers, including database, hosting, and messaging platforms.
7.2. Limitation of Liability
The Licensor is not liable for data loss, operational failures, or loss of in-game assets resulting from the use of ORION OS.
VIII. Execution // Acceptance of Commission
By signing below, the parties execute this Commission under the license class designated in the Deployment Record, as of the Activation Date recorded above.
FOR THE LICENSOR (ORION OS)
Signature: ______________________ Printed Name: ______________________ Date: ____________
FOR THE LICENSEE
Signature: ______________________ Printed Name: ______________________ Date: ____________