Cloud Managed Services

Scope is tailored to each client, but typically covers monitoring and alerting, incident management, patching and maintenance, backup and recovery testing, security posture reviews, access management, cost optimization and monthly reporting. Optional services include data platform operations, application support and infrastructure-as-code development. We document the scope, service levels and responsibilities in a service description before we start, so there are no surprises.

Support hours and response targets are agreed per contract and per priority level. Options range from business-hours coverage in your time zone to extended or round-the-clock coverage for critical production workloads. We define priorities with you, for example by user impact, and set response and update targets for each. Our Hanoi delivery hub allows us to provide working-hour overlap with clients in Asia-Pacific, Europe and North America.

Yes. Your cloud accounts, subscriptions or projects, data and infrastructure code remain yours. We access your environments through named, least-privilege roles that you can review and revoke at any time, with all actions logged. Billing stays with your cloud provider or reseller, unless agreed otherwise. If you end the service, we hand over documentation, runbooks and code so another team can take over smoothly.

Pricing is typically a monthly fee based on the size and complexity of the environment, the number of workloads in scope, the support hours and service levels required, and optional services such as application support or FinOps. An initial onboarding phase covers assessment, documentation and remediation of critical gaps. We provide a transparent proposal after the assessment and review the scope as your environment changes.

We start with an assessment and knowledge transfer from your current team or provider, then onboard monitoring, document runbooks and agree on escalation paths. Where possible we run a period of shadow support before taking primary responsibility. Critical risks discovered during assessment, such as missing backups or exposed resources, are remediated early. The transition plan is agreed in advance with clear milestones.

Yes. Many clients come to us with environments designed by internal teams or other providers. During the assessment we document the architecture, identify risks and technical debt, and agree on which improvements are required before or after we take over. If infrastructure is not yet defined as code, we can gradually bring it under code to make operations more reliable and changes easier to audit.