uloog Managed Cloud (MSP)

We operate your own cloud accounts, with response targets written into the contract.

uloog engineers handle monitoring and alerting, incident response, backups and restore drills, patching and change management. They work through access you grant and can revoke at any time.

uloog is the managed cloud brand of OPA (Tianjin) Technology Co., Ltd. OPA signs the contract, delivers the service and issues its invoices.

Macro photograph of optical fibres carrying small points of green light
Independence statement

What we do

  • Work as an independent technical service provider in cloud accounts that you own.
  • Plan, migrate, build and operate, and charge you only for our own services.
  • Recommend platforms and purchase options on technical and cost grounds.
  • Hand back every document, script and configuration we produce.

What we never do

  • Resell or distribute cloud services, or take a margin on your cloud bill.
  • Pay cloud providers on your behalf or issue invoices for cloud resources.
  • Offer white-label cloud, pooled resources, consolidated billing or a cloud uptime SLA of our own.
  • Claim partner tiers, certifications or provider discounts that we do not hold.
You pay your cloud provider directly. Contracts and invoices for cloud resources stay between you and your provider. Our contracts and invoices cover only our services. We currently have no reseller or partner agreement with any provider and receive no commissions or referral fees. If any of this changes, we will tell you in writing before making any recommendation.

01Included

What each plan includes.

All plans include the same scope. Resource limits, hours and response targets vary.

Monitoring and alerting

We deploy baseline monitoring in the same region as your workloads. We agree alert rules during onboarding.

Incident response

We turn alerts into tickets, handle them and identify the root cause. We provide a written review within 5 business days of every P1 incident.

Backups and restore drills

We check backup jobs against your policy, then perform and record restore drills.

Patching

We agree a monthly patch window with you. It includes pre-checks and rollback.

Change management

Every change follows a change request, risk assessment, your approval, execution, verification and closure.

Health checks and reporting

A weekly health check and monthly report cover incidents, changes, capacity and open risks.

Problem management

If the same alert occurs three times in 30 days, we open a problem ticket to remove the cause.

Engineer hours

A monthly pool of engineer hours covers requests outside routine operations.

02Plans

Three plans, one open today.

We sell a plan only when the team covering its on-call service is in place. We are taking registrations of interest for Standard and Advanced. They open in 2027.
M1Available now

uloog Essential

US$890/ monthCNY 6,000 / month

+ US$1,190 onboarding

Up to 30 managed resources on 1 cloud, up to 3 accounts. Business hours are 09:00 to 18:00 (UTC+8). 12 engineer hours included per month.

M2Registration of interest

uloog Standard

US$2,230/ monthCNY 15,000 / month

+ US$2,970 onboarding

Up to 80 resources on up to 2 clouds, up to 10 accounts. 24×7 response for P1 incidents. 30 engineer hours per month.

M3Registration of interest

uloog Advanced

US$4,750/ monthCNY 32,000 / month

+ US$5,940 onboarding

Up to 200 resources on up to 3 clouds. Adds security operations and FinOps recommendations. 60 engineer hours per month.

A registration of interest is not an order and does not create an obligation. When the plan opens, we will contact you with the final terms. Prices exclude tax.

03Service levels

Written response targets.

These targets cover our response and handling. We do not promise availability of your cloud provider’s platform. The provider remains responsible under its contract with you.
TargetEssential (M1)Standard (M2)Advanced (M3)
P1: service down1 business hour15 min, 24×7. Plan within 1 h15 min, 24×7. Engineer until restored
P2: degraded4 business hours1 h (business hours). 4 h (other)1 h, 24×7
P3: request / minor2 business days1 business day4 business hours
Standard change lead time5 business days3 business days2 business days
ReportingMonthly reportMonthly + quarterly reviewMonthly + quarterly + FinOps

Service credits: If we miss the P1 response target once in a month, we credit 5% of that month’s fee. If we miss it twice or more, we credit 10%. Credits are capped at 20% of the monthly fee. Business hours are 09:00-18:00 China Standard Time (UTC+8), Monday to Friday, excluding public holidays in mainland China.

04Responsibilities

Who is responsible for each area.

Each managed service contract sets out these responsibilities to avoid confusion during an incident.
AreaYouuloogCloud provider
Cloud accounts, billing and invoicesYou own and payNoneBills you directly
Underlying platform availabilityNoneNoneResponsible
Monitoring, alerting and incident responseApproves runbooksResponsibleNone
Backups and restore drillsSets policyExecutes and recordsProvides the service
Changes to productionApprovesPlans and executesNone
Compliance obligations (e.g. MLPS and sector rules)AccountableTechnical supportPlatform controls
Regulatory incident reportingAccountableNotifies you within 30 min of a suspected major incidentNone
Personal data: purposes of processingDecidesProcesses only on your instructionsNone

05Onboarding

Six steps before we take on-call duty.

Service starts only after you sign off the last step, not when the contract is signed.
  1. 01

    Asset inventory

    We list every resource in scope with its owner and criticality.

  2. 02

    Access

    We use delegated roles at three levels: read-only monitoring, routine operations and approved change. See security and access.

  3. 03

    Monitoring and alert baseline

    We deploy monitoring in your region. We agree alert thresholds and routing.

  4. 04

    Backup check

    We verify existing backups against your recovery objectives and list gaps.

  5. 05

    Runbooks

    We write procedures for your top incidents and routine tasks.

  6. 06

    Sign-off

    Service levels start once you confirm the scope, contacts and escalation paths.

Routine cadence

  • Weekly health check
  • Monthly patch window
  • Monthly operations report
  • Problem review for repeated alerts

06Not included

Limits of uloog Managed Cloud.

We state these limits before service starts to avoid common misunderstandings.
  • We do not resell cloud services or provide white-label cloud, consolidated billing or pooled resources.
  • We do not guarantee uptime for your cloud provider’s platform.
  • We do not change application code unless separately contracted.
  • We do not provide generative AI services to you or your users.
  • At this time, we do not provide remote privileged operations for critical information infrastructure operators.

07Exit

An exit plan from day one.

The contract sets out the exit steps if you end the service.
  • Within 30 days, we deliver documentation, infrastructure code and monitoring configuration to you.
  • Within 24 hours after the end date, we remove all our access and give you written confirmation listing each role and key.
  • We do not export your data from your environment by default.

08Questions

Frequently asked questions.

Do you need our root or owner credentials?
No. We never hold root, owner or billing credentials. Access is through delegated roles that you create, scope and can revoke.
What counts as a managed resource?
A managed resource is a VM, managed database instance, Kubernetes cluster, load balancer or similar component that we monitor and operate. We list each one at onboarding. If the count exceeds the plan limit by more than 10%, you move to the next plan from the following month or pay a per-resource fee. See pricing.
Is monitoring 24×7 on Essential?
Monitoring and alert collection run continuously. On Essential, our engineers respond during business hours (09:00-18:00 UTC+8). Standard includes 24×7 response for P1 incidents and opens in 2027.
Where are your engineers located?
Our engineers are in mainland China. They access your environment remotely from China through the roles you grant. If that matters for your compliance, read how we engage before contacting us.

Talk to us about uloog Essential.

Tell us which cloud you use and roughly how many resources you have. We will confirm fit, onboarding dates and the contract.