Azure Spatial Anchors (ASA) Alternative & Migration Hub - Fast, private, scan‑agnostic migration to MultiSet VPS

Move to a future‑proof, enterprise VPS with sub‑10 cm precision, on‑prem  options, and cross‑platform SDKs (Unity, iOS, Android, WebXR, Quest).

Why Replace ASA with MultiSet

Accuracy & stability: Median sub‑10 cm alignment indoors/outdoors; low drift in dynamic environments.
Privacy & control: Self‑host on‑prem, private cloud, or use our cloud; full data ownership.
Scan‑agnostic mapping: Bring E57, Matterport, NavVis, Leica LiDAR, CAD/BIM, or scan with our iOS app.
Cross‑platform: Unity/AR Foundation, native iOS (ARKit), Android (ARCore), WebXR (Three.js/Babylon), Meta Quest (OpenXR via Unity).
Scale: Multi‑floor, campus‑scale mapping with seamless map‑to‑map transitions.
Fast time‑to‑value: Developer‑friendly SDKs, sample scenes, and a guided migration checklist.

ASA → MultiSet
migration at a glance

Replace ASA SDK calls with MultiSet SDK calls and swap anchor creation/localization to map‑based visual localization.
What stays: Your app logic, UI, content pipeline, and most AR Foundation components.
Choose a map source
Import existing scans (E57/Matterport/NavVis/Leica) or scan with MultiSet iOS.
Create a Map Set
Import existing scans (E57/Matterport/NavVis/Leica) or scan with MultiSet iOS.
Initialize SDK
Unity/iOS/Android/WebXR; configure endpoint (cloud or on‑prem) and auth.
Replace anchor calls
Swap ASA anchor APIs for MultiSet anchors or map‑relative content.
Test localization
Swap ASA anchor APIs for MultiSet anchors or map‑relative content.
Ship
Add FAQ schema, deep links, and monitoring (GSC + in‑app telemetry)
Pilot Project
CAPABILITY
ASA (RETIRED)
MULTISET VPS
Indoor precision
Variable
Sub‑10 cm typical in mapped spaces
Data ownership
Microsoft
You own; export anytime
Scan inputs
Limited
E57, Matterport, NavVis, Leica, LiDAR, CAD/BIM, iOS scan
Platforms
Unity, iOS, Android, HoloLens
Unity, iOS, Android, WebXR, Quest (+ROS)
Multi‑map navigation
Limited
Built‑in map stitching & seamless transitions
Status
Retired
Actively developed, enterprise support
Cloud anchors
Azure‑hosted only
Cloud, private cloud, or on‑prem

Key Advantages of Choosing MultiSet as Your Azure Spatial Anchors Alternative

Scan-Agnostic
Mapping
Use LiDAR, 3D scanner or iOS Pro devices - MultiSet ingests them all. Bring your Matterport, Leica, NavVis, Polycam. Want to migrate from ASA datasets? Start fresh with MultiSet's Mapper app.
Private, On-Prem &
On-Device Deployments
Security teams love our flexible options: public cloud, private cloud, edge server, or fully on-device. Perfect for compliance-driven industries replacing MS Azure hosting.
Lower Total Cost of
Ownership
Modern micro-services and pay-as-you-scale pricing cut the ASA engine replacement cost by up to 50%.
Future-Ready
Roadmap
Object Anchors take you beyond a simple Azure Spatial Anchors replacement while preserving today’s maps and APIs.

From Scan to Share in Three Simple Steps

Capture
Capture with any modality - iOS Pro, Matterport, Leica, NavVis, Faro, XGrid, Polycam and more
Map & Localize
Sub-10 cm accuracy, robust to dynamic conditions
Publish & Scale
One-tap share links, private QR codes, Unity/WebXR SDKs
Frequently asked questions
What is the best Azure Spatial Anchors replacement for Unity and AR Foundation apps?

MultiSet VPS is the enterprise replacement for Azure Spatial Anchors for teams that need persistent spatial experiences in Unity, iOS, Android, WebXR, and Quest. Azure Spatial Anchors retired on November 20, 2024, and MultiSet replaces cloud-anchor workflows with map-based visual localization, scan-agnostic inputs, and cloud, private cloud, or on-prem deployment options.

Azure Spatial Anchors vs. MultiSet: what changes for persistent indoor AR?

The core shift is from cloud anchor IDs to map-based visual localization. With MultiSet, the map or MapSet becomes the persistent spatial reference, giving you sub-10 cm positioning in mapped spaces, broader scan-input support, built-in map stitching, and stronger deployment control for enterprise environments.

How do I migrate from Azure Spatial Anchors to MultiSet without rewriting my whole app?

Keep your application structure and replace the anchoring layer. The migration path is straightforward: choose or import a map source, create a MapSet, initialize the MultiSet SDK, replace ASA anchor calls with MultiSet localization and map-relative content, then validate localization in your target environment.

Do I need to recreate all my Azure Spatial Anchors when moving to MultiSet?

Yes. Azure Spatial Anchors do not carry over as existing anchor IDs. In MultiSet, persistent AR is rebuilt on top of a new map, MapSet, or tracked object, depending on whether the experience is space-based or object-based.

Is there an on-prem or offline alternative to Azure Spatial Anchors?

Yes. MultiSet supports cloud, private cloud, and on-prem deployments, and also offers on-device localization for applications that need offline capability or stricter privacy controls. That makes MultiSet a strong fit for compliance-driven, security-sensitive, and low-connectivity enterprise deployments.

What replaces Azure Spatial Anchors for object-based AR experiences?

Use MultiSet Object Tracking. If your original ASA experience was attached to a specific machine, asset, statue, or piece of equipment, upload a photorealistic GLB model and turn that object into a trackable anchor. The MultiSet SDK then recognizes and tracks the real-world object so AR content stays locked in place.