Steady care for the cloud you already run
Business-hours care for your cloud: patching, upgrades, backups with restore tests, cost and capacity reviews, and a monthly written report.
Overview
Small teams build a platform, then move on to product work. Patches slip, managed database versions reach end of support, backups are never restored and the bill creeps up. None of it is urgent until it is.
We take on the routine work during business hours, inside your own cloud accounts. You get scheduled patching and upgrades, restore tests, cost and capacity reviews, and a monthly report of what we did and what needs a decision. This is not a 24/7 on-call service, and we will tell you if you need one.
Signs you need this
- Cloud provider emails warn about versions reaching end of support
- Nobody has restored a backup in the last year
- The monthly bill rises and no one has time to look at why
- Security patches wait until something forces them
What you get
- Onboarding review
- An inventory of accounts, services, versions, backups and access, with a list of urgent fixes.
- Patching and upgrades
- Scheduled operating system, Kubernetes, database and application upgrades in agreed maintenance windows.
- Backup and restore tests
- Backups checked against your policy, with a restore test each quarter and the results written down.
- Cost and capacity review
- Monthly look at spend, idle resources, commitments and growth, with recommendations you approve.
- Monthly report
- What changed, what was found, open risks and decisions needed from you, in plain language.
How the work runs
- 1
Onboarding
2 to 3 weeks
We get access, document the estate, set up monitoring we can see, and fix anything urgent.
- 2
Stabilise
4 to 6 weeks
We clear the backlog of overdue patches and upgrades and run the first restore test.
- 3
Steady state
Ongoing, monthly
Routine care on a fixed calendar, with a monthly report and a review call.
Timings depend on the size of your estate. The assessment fixes them before any build starts.
What you can check afterwards
- No managed service in scope runs a version past its end-of-support date
- A restore test record exists for each quarter, with the time it took
- Each monthly report lists changes made and decisions waiting on you
- Idle and oversized resources found in reviews are either removed or kept with a stated reason
Tools we work with
- AWS
- Microsoft Azure
- Google Cloud
- Kubernetes
- Terraform
- AWS Backup
- Velero
- Prometheus
- Grafana
- AWS Systems Manager
From our work
North American clients, delivered by the OpsBreak team
Running self-hosted platforms for clients
Self-hosted platforms kept running, patched and monitored
Questions buyers ask
- Do you offer 24/7 support?
- No. We work UAE and European business hours. If your service needs night cover, we will help you set up alerting and an on-call rota of your own.
- What access do you need?
- Named roles in your cloud accounts with the rights needed for maintenance, protected by your SSO and MFA. Everything we do is logged in your own audit trail.
- Does any data leave our accounts?
- No. We work inside your accounts and do not copy data out. Reports describe configuration and costs, not your customer data.
- What if we want to stop?
- You keep everything: code, runbooks and access. We remove our roles and hand over open items in a final report.
Talk to us about managed cloud operations.
Tell us what you run and where. We reply within one business day with questions or a quote.