Orbit ITSM documentation

Orbit in detail.

The control model, the limits, the evidence and the deployment boundary, kept here so the home page stays short. All the guides are on the documentation index.

Jump to: Product · Screens · Architecture · Standards · Suitability · Licensing

A useful front door for IT

One experience. The service records you already own.

Orbit is a focused service-management layer for Microsoft 365. It gives employees an approachable place to ask for help and gives the service team structured, auditable work behind the scenes.

Good morningHow can IT help?
RE
02Request a serviceStart with the right form and approvals
03Track my workClear status, comments and history
Access requestAwaiting manager approval
In review
01

Requests and incidents

Guided intake, ownership, priority, comments, status and history.

02

Catalogue and approvals

Configurable services and forms with documented approval states.

03

Assets and lifecycle work

Link service work to assets, onboarding, offboarding and fulfilment.

04

Knowledge and operations

Reusable guidance, service oversight and evidence-ready records.

Illustrative product view. Features and presentation are configured per deployment.

See the live experience

The demo runs as Vertex Group, a fictional organisation, with fictional data.

Real screens, not mockups

See Orbit from both sides of the desk.

These are current screenshots from the public Orbit demo tenant—the same portal your staff sign into, and the same queue your IT team runs from, shown here with sample data.

What your staff see

Everyday requests, guided end to end

A calm home screen, a catalogue built around your services and clear status on every request—so fewer of them become a phone call to IT.

What your IT team sees

The operational view behind the portal

The queue your team actually works from, approvals awaiting a decision, and the asset records tickets refer back to.

The demo runs as Vertex Group, a fictional organisation, with fictional data.

A legible technical boundary

Built around Microsoft 365—not beside it.

The standard Orbit deployment is a static React application. People sign in with Microsoft Entra ID; the browser works with Microsoft Graph and SharePoint Online under the signed-in user’s delegated access.

Cloudflare delivers that static application from its global edge: TLS encryption and DDoS protection are included, and there is no application server for your team to run or patch.

  • SharePoint Lists remain the primary service-data store.
  • Tenant identity, branding and catalogue are deployment configuration.
  • Power Automate is used only where selected workflows require it.
  • Strict writes can add an authenticated server-side control where required.
  • Cloudflare hosts and delivers the application files only—ticket and tenant data never leaves Microsoft 365.
Open the architecture guide
People
EmployeesBrowser + Microsoft identity
Service teamRole-aware operating views
Experience
Orbit ITSMStatic web application
No ticket or tenant data stored at the edgeRuns on Cloudflare
Your tenant
Entra ID + GraphIdentity and delegated access
SharePoint OnlineLists, permissions and records
Power AutomateOptional tenant workflows

Standards and governance

Built to support good practice. No certificate claims.

Orbit helps you run service management and keep records an auditor can follow. It does not certify a deployment, or replace the controls, ownership and assurance your organisation must operate.

ITIL and ISO/IEC: aligned, not certified.

Service management

ITIL-aligned ways of working

Structured intake, ownership, approvals, knowledge, change and service records support disciplined ways of working.

Management systems

Mapped to ISO/IEC standards

Our documentation shows which Orbit features support ISO/IEC 20000-1, 27001 and 27002 practices. It makes no conformity claims.

Due diligence

Claims you can check

Each public guide lists the source documents it draws on, so you can trace a statement back. Internal drafts stay private.

ArchitectureSecurity boundaryAssurance checklistStandards applicabilityOperational ownership

Suitability at a glance

A strong fit when Microsoft 365 is already home.

A good product decision includes the awkward questions. These are the starting conditions we would examine before recommending a deployment.

Strong fit

Orbit is worth a close look if you…

  • run your organisation on Microsoft 365 and SharePoint Online;
  • want a branded service portal without a separate SaaS data silo;
  • value source access and tenant-specific configuration; and
  • can assign service, platform and security ownership.
Design review

Plan the control model carefully if you need…

  • strict server-side authorization for sensitive write paths;
  • premium/custom connectors or high-volume automation;
  • guest, cross-tenant or complex Conditional Access scenarios; or
  • formal retention, DLP, backup or data-residency controls.
Different pattern

The standard model is not designed as…

  • a multi-customer shared SaaS platform;
  • a replacement for SharePoint Online;
  • a certification or compliance guarantee; or
  • a zero-ownership turnkey managed service.

Licensing, plainly stated

Orbit’s licence and Microsoft’s licences, kept separate.

Orbit has its own commercial licence. Your organisation also supplies the Microsoft entitlements required by the solution design.

Review the licensing guide
LayerWhat to allow forWhen
OrbitOne Microsoft 365 tenant per organisation, with full source code always included. One flat annual licence per organisation (not per agent, no tiers): Ask us. Setup is a separate one-off engagement, from A$4,000.Required
Microsoft 365User licensing that includes SharePoint Online, plus Entra app registration and approved permissions.Required
Power AutomateAppropriate use rights for selected flows, ownership context and connector types.By design
Power Apps, Dataverse, Power BIOnly where optional apps, premium data services or reporting are adopted.Optional

Pricing

Setup from A$4,000, then one flat annual licence for the whole organisation. Your Microsoft licences are yours and are not part of Orbit’s price. See pricing on the home page or compare with per-agent pricing.

Microsoft licensing, connector classification and tenant policy can change. The intended design and user population must be checked with your Microsoft licensing administrator before production deployment.

Delivery partnerships

RME Solutions is a Cloudflare Partner and a Microsoft Partner.

Built on Microsoft 365 Runs on Cloudflare

Cloudflare Partner

RME provisions and operates each client’s delivery on Cloudflare—the edge network, TLS and DDoS protection behind every Orbit deployment.

Microsoft Partner

Orbit is designed for, and deployed into, the Microsoft 365 platform your organisation already runs.

Partner status reflects RME’s membership in each programme—not Microsoft or Cloudflare certification, endorsement or co-sell of Orbit.