Hardware and software must align
Device procurement and platform compatibility need to be considered as one architecture.
VMAOS Kunlun / Hardware + platform delivery
Cloud phone infrastructure, built for your enterprise
VMAOS Kunlun brings ARM devices, environment deployment and PaaS delivery together. Build and manage a cloud phone platform in an agreed enterprise environment.
VMAOS / 03Solution illustration
Enterprise environmentON-PREMISES
ARM device cluster
Kunlun PaaS platform
Enterprise systems
Built for
- Large enterprises
- Infrastructure teams
- Organizations with local deployment needs
01 / THE CHALLENGE
Make local deployment clearer to manage
Start with common business needs and find an approach that fits your current stage.
Environment readiness takes work
Facilities, networks and clusters require site-specific preparation and technical coordination.
Separate purchases add integration
Compatibility, validation and responsibilities need early agreement across delivery stages.
Every enterprise is different
Capacity, management needs and existing networks shape the deployment approach.
02 / CAPABILITIES
From hardware to platform, a connected delivery path
Coordinate devices, infrastructure and platform software around your actual environment. Agree the scope before implementation and validation.
Hardware and device procurement
Plan suitable ARM devices and related hardware for workloads, capacity and deployment conditions.
02
Environment and cluster deployment
Prepare rack installation, the operating environment and necessary networking for the site.
03
PaaS platform delivery
Deploy Kunlun software with agreed environment adaptation, configuration and business integration.
04
Local operations and management
Run the platform in the agreed environment, with operations and support responsibilities defined per project.
03 / ARCHITECTURE
From your facility to your workflows
The site, ARM cluster, PaaS platform and business systems form distinct delivery layers. Actual topology follows your environment.
Illustrative deployment architecture. Hardware scale, network topology and high availability are not assumed. Security boundaries, external network dependencies and support require project-specific agreement.
- 01 / Environment
Enterprise facility / agreed deployment site
Confirm racks, power, networking and on-site coordination.
- Facilities
- Network planning
- Site readiness
- 02 / Infrastructure
ARM device cluster
Organize devices, compute and network resources to agreed specifications.
- ARM devices
- Compute and storage
- Cluster network
- 03 / Platform
VMAOS Kunlun PaaS
Configure and adapt the platform for resource management.
- Deployment
- Resource management
- Integration
- 04 / Business
Cloud phone instances and enterprise systems
Validate application environments and business workflows.
- Android instances
- Enterprise workflows
- Operations
04 / IMPLEMENTATION
From idea to implementation, with clear priorities
A suggested implementation path. Stages, timing and support are agreed for the actual project.
- 01
Discover
Review workloads and local operating requirements.
- 02
Design
Agree architecture, specifications and scope.
- 03
Prepare hardware
Arrange procurement to the agreed plan.
- 04
Deploy environment
Prepare the site, network and cluster.
- 05
Deliver the platform
Deploy, configure and integrate software.
- 06
Accept and support
Review acceptance criteria and operational handover.
05 / BUSINESS VALUE
More space for your business to grow
Coordinated hardware and software
Plan devices and platform compatibility within a single delivery approach.
Fit your actual environment
Design around facilities, networks and business requirements.
Clarify operating responsibilities
Agree resource management, acceptance criteria and ongoing support.
06 / QUESTIONS
A few things to know before you start
Is Kunlun just a software license?
No. Kunlun combines ARM hardware planning and procurement, environment and cluster deployment, PaaS delivery and local operations. The actual delivery list is agreed for each project.
Can we reuse an existing facility or ARM devices?
Share the site conditions, hardware models and network details for assessment. Reuse depends on compatibility, capacity, operating conditions and platform adaptation; existing devices are not automatically assumed to be suitable.
Does private deployment mean fully offline operation?
Not necessarily. Local deployment describes where and how the platform runs. External network dependencies, updates and security policies require separate evaluation against your needs and actual product capabilities.
How are delivery timing and support agreed?
They depend on hardware readiness, the site, integration scope and validation requirements. Define the delivery list, acceptance criteria, responsibilities and support during design, with the contract as the final reference.
LET’S BUILD TOGETHER
Plan infrastructure around your enterprise
Share your device scale, environment and business goals. Let’s map a practical path from hardware to platform.
Discuss private deployment
Connect directly with our business team on WeChat, WhatsApp or Telegram.