uloog
中文

Outsourcing & implementation

Migrations and platform builds, delivered under a written statement of work.

Your SOW defines the outcome and acceptance criteria. Standard scope has a fixed price, and we hand over everything we build. We are accountable for the agreed result, not merely the hours worked.
Discuss a projectProject pricing
A crane lifting a prefabricated building module into place
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.
Project delivery under a statement of work. We deliver agreed outcomes and manage our own engineers. We do not place individuals under your day-to-day management, and we do not provide labor dispatch or staff augmentation.

01Standard projects

Fixed scope, fixed price or a custom SOW.

Standard scopes cover most first projects. We quote larger projects as custom SOWs using the same method.

P2

Cloud migration: standard wave

We migrate a defined group of systems from an IDC, an on-premises environment or another cloud into your target cloud account.

Scope includes

  • Up to 20 VMs, 2 databases (≤500 GB each) and 3 applications
  • A wave plan, runbook and rollback plan for each system
  • A pilot move, then production cutover in agreed windows
  • 14 days of hypercare after the final cutover
US$17,800CNY 120,0006 weeks plus 14 days of hypercare

P3

DevOps & container platform

We build a production-ready delivery platform on your cloud provider's managed Kubernetes service.

Scope includes

  • One managed Kubernetes cluster, including ingress, secrets and autoscaling
  • CI/CD pipelines for up to 5 services
  • Infrastructure-as-code baseline for the platform
  • Monitoring and logging baselines with alert routing
US$13,400CNY 90,0004 weeks

SOW

Custom engineering project

Landing zones, multi-account setups, disaster-recovery builds, observability, database migrations, IaC refactoring and similar work.

Scope includes

  • Scope, deliverables and acceptance criteria written for each project
  • Payments by milestone
  • The same delivery method, documentation and handover standards
Quoted per SOW. Time and materials at US$90 / CNY 600 per hour

02Suitable scenarios

When implementation is a fit.

This service suits projects with a clear target and involvement from the team that will own the result.
  • You have completed an assessment, with us or another party, and are ready to move the first wave.
  • Your developers deploy manually and you need repeatable pipelines and environments.
  • You are launching in a new overseas region and need the platform built to the same standard as at home.
  • Your team owns the systems but cannot run a migration alongside daily work.

03Method

How we deliver a project.

Every project follows the same stages. The SOW sets the dates and acceptance criteria.
  1. 01

    Discovery

    We confirm inventory, dependencies and constraints. We agree change windows and communication channels.

  2. 02

    Plan and runbooks

    We write a runbook and rollback plan for each system, then review them with your owners before changes begin.

  3. 03

    Pilot

    We first migrate or build a representative component, then update the plan based on the result.

  4. 04

    Waves and cutover

    Production changes take place in agreed windows, and each is tied to an approved ticket. At each checkpoint, we confirm whether to proceed.

  5. 05

    Hypercare

    After cutover, we provide extra support, check daily and maintain a defect log.

  6. 06

    Acceptance and handover

    We confirm acceptance against the SOW criteria, deliver the handover pack, and either remove our access or transfer it to a managed service contract.

04Handover

You own the agreed deliverables.

Ownership of deliverables transfers to you after payment, as set out in the SOW.
  • Infrastructure-as-code repositories in your own source-control system.
  • Architecture diagrams, runbooks and an operations handbook.
  • Monitoring and alerting configuration.
  • A list of all access we held and written confirmation that we removed it.

Common tools

  • Terraform / OpenTofu
  • GitLab CE or your existing platform
  • Managed Kubernetes services
  • Provider-native migration and backup services
  • Zabbix and cloud-native monitoring

05Project delivery

Common questions.

What happens if the scope changes during the project?
We send a written change request that states the effect on effort, price and dates. We bill no work outside the SOW until you approve it.
Do you work on-site?
We deliver remotely by default. We can arrange on-site work in Tianjin and Beijing; travel is billed at cost. We do not currently offer on-site delivery outside that area.
Who pays for the cloud resources used during migration?
You pay your provider directly from your own account. Our invoices cover our services only. See our independence statement.
Can you continue running the systems after the project?
Yes. uloog Managed Cloud can take over after the project. For many projects, managed-service onboarding is the last handover step.

Planning a migration or platform build?

Send us the approximate size and target. We will reply with questions or a proposed standard scope.

Discuss a projectuloog Managed Cloud