AR Cloud is a connected service that allows Magic Leap 2 devices to access large-scale spatial data. This spatial data can be managed on the web-based console where digital twin administrators create Shared Spaces, manage device-side scans, and merge scans to contribute to larger-scale Spaces. AR Cloud admins are able to import and export spatial maps, manage large-scale digital twin deployments, and monitor Magic Leap 2 device access.
See our guide on required licensing to be able to use AR Cloud on your device(s):
AR Cloud allows users to go beyond the limitations of their Magic Leap 2 devices. The following features help enhance a user’s Magic Leap 2 experience:
- Co-present experiences – allows multiple users to experience the same digital content in the same place through shared maps and their spatial anchors.
- Large spatial maps (>10,000m2) – without AR Cloud, each device has a limit of five Local Spaces of ~250m2.
- Device access to an unlimited amount of Spaces – Magic Leap 2 devices can gain unlimited access to shared Spaces, as opposed to the 5 stored locally.
Choose your Installation
AR Cloud can be installed to support both Virtual Machine installations and enterprise installations. Choose the correct installation for your needs. You can always change or update your installation later.
Virtual Machine Installation
- Utilizes Virtual Machines and OTA/UTM files for an all in one installation.
- Runs on a desktop or laptop meeting the minimum specifications.
- Used to support a small number of devices (3 or less).
- Used by developers creating applications which utilize AR Cloud.
- Runs on cloud providers such as AWS, GCP and Azure.
- Runs on custom servers meeting the minimum specifications.
- Fully scalable and customizable.
- Used to support a larger number of devices.
- Used by enterprises supporting production solutions.
|16GB per Node
|32GB per Node
|CPU (x64) cores
|CPU (Apple Silicon) (OVA)
|1 GB Wifi 6
|1 GB Wifi 6
Compute platform optimizations: For optimal performance, it is suggested to use
microarchitectures that support
x86-64-v3. It is suggested to use
x86-64-v3 nodes1 for the best performance.
- Compute nodes:\
GCP: All example machine types support
x86-64-v3. Microarchitectures used for specific machine types can be found here.\ AWS: All example machine types support
x86-64-v3. Microarchitectures used for specific machine types can be found here.\ Azure: All example machine types support
x86-64-v3. Microarchitectures used for specific machine types can be found here and here↩
Familiarity with the following tools is required to install AR Cloud for all cloud installations.
After installation of AR Cloud, we welcome you to try our first-party, Open Source project, Leap Brush.
This project will allow you to quickly ramp up to a multi-user, collaborative experience, leveraging AR Cloud's power features. The project can work over local area network (LAN), enabling virtually no latency for your shared experience.
For technical support, please reach out to us at firstname.lastname@example.org.
📄️ GCP Deployment
Enterprise deployment to Google Cloud Platform (GCP)
📄️ AWS Deployment
Enterprise deployment to Amazon Web Services (AWS)
📄️ Azure Deployment
Enterprise deployment to Azure
📄️ Custom Deployment
Enterprise deployment to a custom server
📄️ VM Image Deployment
Basic deployment using a pre-configured virtual machine
A breakdown of required licenses to operate AR Cloud
📄️ Upgrade AR Cloud
Process for updating AR Cloud version after initial installation
📄️ Customization and Security
Customize and secure your AR Cloud installation