湖南华邦互联网科技有限公司 HuaBang Internet Technology
ProductsOverviewDomestic PaaSGlobal PaaSPrivate DeploymentTechnologyOverviewARM InfrastructureAndroid VirtualizationContainerizationResource OrchestrationMedia TransportSolutionsOverviewCloud Phone + AIGovernmentEnterpriseCustom DeliveryCase StudiesNewsAboutContact
中文 EN
PUBLIC CLOUD · CN

Domestic PaaS Public Cloud

Treat cloud Android instances as orchestration-ready resources: provision on demand, isolate by tenant, and integrate through APIs instead of manual desktop tools.

POSITIONING

An orchestration-ready mobile runtime

Built for customers who need to run mobile applications at scale without building their own data centre. Compute, system images, runtime instances and operational data are organised into standard resources that a business system can create, configure and recycle through APIs.

  • Designed for business systems

    APIs, not manual clicks, are the primary interface.

  • Metered resources

    Instances, storage and bandwidth are counted per tenant.

  • Upgrade without disruption

    Images and platform versions are separated for staged rollouts and rollback.

RESOURCE MODELTENANT → INSTANCE
TENANT
Tenant & quota
IMAGE
Image version
INSTANCE
Runtime instance
POLICY
Network & policy
METER
Usage & billing
API
OpenAPI
CAPABILITY

Core functions

A description of platform function structure; the exact scope depends on the service edition you subscribe to.

  • Create and recycle

    Create instances by image and specification, with batch operations and lifecycle tracking.

  • Health and status

    Runtime state, resource usage and abnormal events in one view.

  • Remote control channel

    Screen and input channels for debugging, inspection and manual intervention.

  • Batch tasks

    Configure, restart or switch images across many instances.

  • Image versions

    Layered storage with published versions and rollback.

  • Device parameters

    Model, resolution and network parameters configurable per tenant.

  • Init scripts

    Initialise the environment on first boot for consistency.

  • App distribution

    Distribute packages by tenant or group.

  • Tenancy and roles

    Tiered authorisation with auditable operations.

  • Metering and billing

    Usage by instance duration, specification and resources.

  • Operations dashboard

    Tenant scale, resource usage and task execution.

  • Alerts

    Threshold alerts with callbacks and notifications.

  • REST APIs

    Instances, images, tasks and metering exposed as resources.

  • Auth and signatures

    Key-based request signing with tenant isolation.

  • Event callbacks

    State changes and task results pushed instead of polled.

  • SDK and samples

    Examples in common languages to shorten onboarding.

  • TECHNOLOGY STACK

    Four-layer technology architecture

    A complete layered system from ARM silicon to application services. Layers are decoupled through stable interfaces and support public, private and hybrid deployment.

    Four-layer technology architecture
    Capability layerInterface / resource boundary
    Application layerAPPLICATION
    Social & content appsMulti-account ops
    Enterprise appsBusiness on cloud
    Cloud gamingReal-time rendering
    AI agent runtimeAgent execution
    REST / WebSocket / SDK
    PaaS platform layerPLATFORM
    Multi-tenancyTenant
    OpenAPI gatewayOpenAPI
    Resource schedulingScheduler
    Device & instance opsDevice Ops
    Operations & billingBilling
    Tenant isolation / metering / auth
    Android runtime layerANDROID RUNTIME
    Custom AOSPAOSP
    Android imagesImage
    Container unitContainer
    Cloud runtimeRuntime
    Image delivery / instance lifecycle
    ARM infrastructureINFRASTRUCTURE
    ARM SoC arraySoC Array
    High-density racksRack Server
    Distributed storageStorage
    Network & edgeNetwork / Edge
    ARM64 compute poolMulti-tenant isolationOpen APIPrivate delivery

    This diagram explains the technical structure and component boundaries. Actual implementation and delivery scope are defined in the agreed solution.

    SPECIFICATION

    Specification and delivery

    The table describes capability boundaries; specifications and pricing are confirmed through sales.

    ItemDescription
    ArchitectureARM64 compute pool
    Instance specsCPU / memory / storage combinations, per provisioning catalogue
    ImagesStandard customised AOSP image; customer-specific builds supported
    NetworkPublic access and private interconnect configured per scenario
    APIREST OpenAPI with auth, callbacks and samples
    Lead timeStandard services online; custom work scheduled by project
    SupportPlatform-operated maintenance with ticketing and technical support
    FAQ

    Frequently asked

    A cloud phone instance delivers an Android runtime as the unit of service, focused on mobile application lifecycle, device parameter simulation and screen channels. A virtual machine delivers a general-purpose operating system.

    The console is for debugging and inspection. At scale, integrate instance management through the OpenAPI into your business systems.

    Standard APIs and callbacks are provided; adaptation scope is confirmed during onboarding assessment.

    Yes. The same platform kernel can be deployed into a customer-owned resource pool.

    CLOUD PHONE + AI

    A managed Android runtime for AI workflows

    Use cloud phone instances, images and available platform APIs as the mobile runtime layer for agent development, app testing or training environments. Model and app compatibility are assessed by project.

    Explore AI scenarios

    Need an onboarding assessment?

    Share your scenario, instance scale and integration requirements; we will propose a resource and API model.