Monitoring & alerting
Metrics, logs and alerts for infrastructure, Kubernetes and databases, routed to the right people.
Managed Cloud · Production Operations
Cloud Managed Services for Production Workloads
MYC operates cloud infrastructure alongside your team: we watch it, respond when something breaks, keep it patched and backed up, and review capacity and cost so it keeps running as the business grows. Coverage hours, response targets and escalation paths are agreed per engagement.
Who it's for
Signs your cloud needs an operations team
Usually a small team is running production on top of its day job.
Without dedicated operations
- Alerts nobody owns, or so many that people stop reading them.
- Patching and upgrades keep getting postponed.
- Backups that have never been restored, so nobody knows if they work.
- Capacity surprises at the worst moment: a campaign, an event, month-end.
- A cloud bill that only grows, with no one reviewing it.
- Knowledge in one person's head.
With MYC operating alongside you
- Alert routing with owners and a clear escalation path.
- Scheduled patch windows and upgrade plans for clusters and databases.
- Tested restores with recovery objectives agreed per system.
- Capacity planning before known peaks, and autoscaling where it fits.
- Regular cost reviews with concrete savings actions.
- Runbooks and documentation your team can use too.
What's included
What our cloud managed services cover
Incident response
Triage, mitigation and escalation, followed by a written post-incident review.
Patching & upgrades
OS, Kubernetes and database updates in planned windows with rollback plans.
Backup & disaster recovery
Backup policies, restore tests and recovery runbooks for each critical system.
Capacity & performance
Capacity planning, autoscaling and performance tuning ahead of known peaks.
Cost optimization
Rightsizing, idle-resource cleanup and commitment reviews on a regular cadence.
Security hardening
Access reviews, least-privilege IAM, network rules and a self-hosted WAF where needed.
Self-hosted WAFReporting & reviews
Monthly report on incidents, changes, capacity and cost, reviewed together.
Platforms
Platforms and tools we operate
Huawei Cloud
Kubernetes
Huawei Cloud CCE
Linux VMs
PostgreSQL
MySQL
MongoDB / Percona
Redis
NGINX
Prometheus
Grafana
OpenSearch
PMM
GitLab CI/CD
Onboarding
How we take over operations
Onboarding is a project in its own right. Nothing is switched on blind.
-
01
Discovery
Inventory systems, dependencies, existing alerts, backups and known risks.
-
02
Access & tooling
Least-privilege access, monitoring agents and log shipping, agreed with your security team.
-
03
Runbooks & routing
Write runbooks for critical systems and set up alert routing and escalation.
-
04
Trial period
Run operations together while alert noise is tuned and runbooks are proven.
-
05
Steady state
Operations under the agreed coverage, response targets and change process.
-
06
Monthly review
Incidents, changes, capacity and cost reviewed against the goals we agreed.
Operating model
What each side owns
What we need from you
- A technical contact and an escalation contact
- Access through accounts you control
- Change windows that suit your business
What you get
- Named engineers who know your environment
- Runbooks and documentation you keep
- A monthly report and review
Out of scope unless agreed
- Application feature development
- Changes to application code
- Third-party systems we cannot access
Proof
Operations work we have delivered
Project
Enterprise managed service operations
Infrastructure operation and incident management with runbooks, SLO governance and monthly reporting.
Engineering
Observability with Huawei Cloud AOM/APM
Telemetry and alerting engineered for the operators who run the platform.
Case study
Keeping 19 production databases in sync
Operated a live migration pipeline with zero aggregate lag at verification.
FAQ
Cloud managed services questions, answered
What is included in cloud managed services?
Monitoring and alerting, incident response, patching and upgrades, backup and restore testing, capacity and cost reviews, security hardening and monthly reporting. The exact scope is written into each engagement.
What coverage hours do you provide?
Coverage hours, response targets and escalation paths are agreed per engagement, based on how critical each system is.
Can you take over an environment we built ourselves?
Yes. Onboarding starts with discovery and a trial period, so nothing changes until we understand your environment.
Which platforms do you manage?
Huawei Cloud, Kubernetes (Huawei Cloud CCE or self-managed), Linux VMs and the databases and middleware on them.
How do you handle access and credentials?
Through accounts and roles you control, with least privilege. Access can be reviewed and revoked at any time.
How is it priced?
Based on the number and criticality of systems and the coverage agreed, after the discovery phase.
Get Started
Talk to a cloud operations engineer
Tell us what you run and where it hurts today. We'll suggest what an operating model could look like.