Hospitality · AWS · 19 months
From weekly outages to a measured SLA
Mean time to recovery
12 months of NOC operation vs the 6 months prior.
−90%
Awards & Recognitions
Cloud managed services
We take day-to-day ownership of your cloud estate
Orion runs your cloud infrastructure under defined responsibilities, controlled access and governed escalation — while your organisation retains ownership and visibility.
Documented responsibility
Contract-defined coverage
You keep the accounts
Your organisationGoverns
Account ownership
Approval authority
Complete visibility
Status · decisions · evidence
Orion operationsOperates
Monitor
Respond
Change
Secure
Optimise
Alerts & telemetry
Approved changes
Your cloud estateStays
yours
Applications
Compute
Containers
Network
Data
Identity
Backup
Client results
What changed once Orion took over operations
Three anonymised engagements. Named references available under NDA.
Fintech · Azure · 11 months
A drifting cloud bill back under control
Monthly cloud spend
Two billing cycles after optimisation closed.
−33%
iGaming · AWS + on-premise · 2 years
Patching and recovery made auditable
Patch compliance
Two consecutive annual audit reviews.
+41 pts
Assurance
ISO/IEC 27001 certified
CMMI Level 3 appraised
SOC 2 Type II — audit underway
Data residency: India · Canada · EU
AWS & Azure certified engineers
What we run
Six operational areas, owned end to end
Each area comes with named deliverables — not best-effort attention.
Monitoring, alerting and incident response
Someone is watching the estate at 3am, and knows what to do when it pages.
You receive · Dashboards, tuned alert rules, runbooks, incident log
and monthly post-incident reporting.
Patching, upgrades and lifecycle
Patching happens on a schedule you can show an auditor, not when someone remembers.
You receive · Patch calendar, tested change windows, compliance
reporting, EOL register.
Backup, resilience and disaster recovery
Backups that have actually been restored, not just scheduled.
You receive · Backup policy per workload, quarterly restore-test
evidence, RTO/RPO statement, DR runbook.
Cloud security and compliance
Access, exposure and vulnerabilities reviewed continuously instead of before an audit.
You receive · IAM review, hardening baseline, vulnerability
reports, audit-ready control evidence.
Cloud cost governance
A cloud bill you can explain line by line — and reduce without touching capacity.
You receive · Per-team cost reporting, rightsizing plan,
commitment recommendations, anomaly alerts.
Infrastructure automation and change
Changes are made in code and reviewed, not clicked into a console and forgotten.
You receive · Terraform state and modules, change log, drift
reports, provisioning documentation.
Shared responsibility
Who owns what, layer by layer
Orion carries the operational middle of every layer. Accounts, approvals and business decisions stay with you.
Compute & OS
Hardware, hypervisor and runtime
availability.
OS and image patching, sizing, availability
configuration, host monitoring.
Application code, releases and business
acceptance.
Data & backup
Durable storage and replication
primitives.
Backup policy, retention and quarterly restore
tests with evidence.
Data classification and retention
requirements.
Identity & access
The IAM service and its
guarantees.
Role design, least-privilege review, joiners and
leavers, break-glass control.
Approving access and owning the corporate
directory.
Network & edge
Physical network and baseline DDoS
protection.
VPC/VNet configuration, firewall rules,
certificates, exposure review.
Permitted ingress and third-party
connectivity.
Security operations
Platform controls and provider
advisories.
Vulnerability remediation to SLA, log retention,
incident response and review.
Risk acceptance, policy and regulator
obligations.
Cost & capacity
Billing data and pricing
mechanics.
Tagging, rightsizing, commitment
recommendations, monthly variance reporting.
Budget ownership and reservation sign-off.
Change
Service change and deprecation
notices.
Change execution in agreed windows, rollback
plan, post-change checks.
CAB approval and the change-freeze calendar.
Indicative for a Standard-tier engagement. The signed matrix is produced per estate during transition.
Incident response
What happens after the first alert
A fixed escalation ladder, so ownership never depends on who happens to be awake. The lower line shows what your team hears at each step.
0–15 min
NOC engineer, L1/L2
Alert acknowledged, triage started and an incident channel opened.
Your on-call is notified
15–45 min
Senior cloud engineer, L3
Engaged if not contained. Workaround or rollback applied.
Service manager informed on your behalf
45–90 min
Service delivery manager
Takes over communication and engages cloud-provider support.
Your teams coordinated directly
90 min +
Delivery director
Executive escalation until service is restored.
Hourly written updates
Service tiers
Priced on coverage, not on hours logged
The shaded week shows exactly when each tier is watching. Firm pricing follows the free estate assessment.
Essential
12×5Small, stable estates that need ownership rather than round-the-clock cover.
M
T
W
T
F
S
S
P1 response
1 hour
Indicative
$3,400–5,200
per estate / month
- 12×5 monitoring with 1-hour P1 response
- Monthly patch cycle and change windows
- Backup monitoring and quarterly restore test
- Monthly service and cost report
Standard
24×5Production estates where downtime has a direct business cost.
M
T
W
T
F
S
S
P1 response
30 minutes
Indicative
$8,600–12,400
per estate / month
- 24×5 monitoring and incident response
- Patching, backup, DR testing and security review
- Named service manager and monthly review
- Defined resolution targets per service
Enterprise
24×7Regulated or multi-account estates with audit and compliance obligations.
M
T
W
T
F
S
S
P1 response
15 minutes
Indicative
$16,500+
per estate / month
- Dedicated operations pod and service manager
- Compliance evidence pack and audit support
- Quarterly DR exercise and architecture review
- Continuous-improvement backlog
Indicative ranges assume a single-cloud estate of up to 60 workloads. Cloud consumption is never included and never marked up.
The business case
Building a 24×5 rota in-house versus buying it
First-year cost of the same coverage, side by side.
Build in-house
$808,000
Orion Standard
$115,200
Five engineers $625,000
Tooling $48,000
Recruitment $75,000
Management & on-call $60,000
Standard tier, 12 months $103,200
Transition, one-off $12,000
Illustrative model, not a quote. Assumes five fully loaded North American cloud engineers at $125,000 each. Recruitment, attrition and rota cover sit with Orion under the managed model.
First 90 days
Operational responsibility moves across in stages
Your team leads at the start. Orion takes over as runbooks, access and escalation are proven — your governance never moves.
30Days
1–30
Transition in
- Assessment findings turned into a prioritised risk register
- Access, tooling and monitoring agents deployed
- Runbooks written for the top incident classes
- Shadow running alongside your team
60Days
31–60
Stabilise
- Alert noise cut, real pages tuned to failure modes
- Patch backlog cleared and change windows established
- Backup coverage completed and first restore test run
- IAM and network exposure reviewed and tightened
90Days
61–90
Run and optimise
- Service running to agreed SLA with monthly reporting
- Cost baseline established with per-team attribution
- First optimisation actions delivered and measured
- Improvement backlog agreed with your team
Frequently asked
Questions buyers ask before handing over operations
Access, coverage, exit and what stays yours — the parts that decide whether handing over operations is low risk.
A typical transition runs four to six weeks: five days of assessment, then discovery, tooling and access setup, shadow running, and formal service commencement. Smaller estates transition faster; regulated environments take longer because access approvals do.
Five working days. We review availability and single points of failure, monitoring and alerting coverage, patch and backup posture, restore-test history, IAM and network exposure, and your last three months of cloud billing. You receive a written findings report with prioritised risk and estimated effort — yours to keep, no obligation.
P1 response is 1 hour on Essential (12×5), 30 minutes on Standard (24×5) and 15 minutes on Enterprise (24×7). Resolution targets depend on the workload and are agreed per service in the SLA rather than quoted as a blanket number.
Yes. The accounts, root credentials, billing relationship and all infrastructure code stay yours. We work through federated, least-privilege roles that you can revoke at any time, and every action is logged in your own audit trail.
Exit is a documented procedure agreed at contract signature: 60 days notice, a written handover pack of runbooks, dashboards and change history, overlapped shadowing with your incoming team, and access revocation on an agreed date. No lock-in tooling, no proprietary agents you cannot remove.
No, and it is never marked up. Cloud spend stays on your own accounts under your own billing agreement. Our fee covers the service; cost optimisation work usually pays for a meaningful part of it.
Start with the assessment
Hand over cloud operations without giving up control
Five working days. A written findings report on availability risk, monitoring, patch and backup posture, access exposure and cloud spend — yours to keep, no obligation.
Written findings report, yours to keep
Prioritised risk register with estimated effort
No obligation to proceed
Book a free estate assessment
A service delivery lead replies within one business day.
Confidential. NDA available on request.
