Commercial model
Orbit commercial model
How Orbit is licensed: source-available, one organisation per licence, full source code always included, and an annual fee by quotation — kept separate from Microsoft licensing and implementation. The executed agreement remains authoritative for a specific engagement.
Source-available, not open-source
Orbit is source-available software licensed to individual client organisations by RME Solutions Technology — it is not an open-source project accepting outside contributions to a shared codebase, and not a shared multi-tenant SaaS platform.
A licensed client receives the Software’s full source code, not a compiled or obfuscated build. Source-available is not the same as open-source: the licence does not grant the redistribution or sublicensing rights an open-source licence would. This page is a plain-language summary of the commercial shape; the executed agreement is the operative reference for a specific customer.
One licence, one organisation, one tenant
Orbit proposals are scoped to a named customer organisation and its Microsoft 365 tenant, for self-hosted use. A second organisation or tenant needs a second licence.
- Full source code is included with every licence — there is no separate tier for reading the code.
- Redistribution, resale, sublicensing and hosting the Software (or a derivative) for a third party are not permitted.
- A second organisation or Microsoft 365 tenant requires a second licence.
- The named legal entity, tenant and any related-entity treatment are recorded in the executed agreement.
Fees, setup and support
The Orbit licence fee is billed annually and priced by quotation, based on the client’s scale and requirements. Setup and implementation — Entra ID app registration, SharePoint list provisioning, branding and initial configuration — are not bundled into the licence fee; they are available as a separately contracted, one-off engagement.
Microsoft licences, cloud services and third-party subscriptions remain customer-supplied unless expressly included in the agreement. Support is governed by the same agreement as the licence and any setup engagement.
Procurement checklist
Before purchase, confirm the licensed entity and tenant, selected modules, implementation scope, support service levels, update entitlement, Microsoft prerequisites and any customer-specific terms.