Press Release
MultiSet AI has released v1.14.0, the most significant update to the MultiSet Visual Positioning System since the platform's general availability. The release ships three major capability shifts at once: Map Versioning, which decouples the spatial content layer from the underlying scan; on-device localization on Android matched by full hint API parity across every on-device VPS SDK; and performance upgrades to mesh density and query latency that affect every customer running MultiSet in production.
The headline of v1.14.0 is Map Versioning, the first VPS-native primitive that treats production spatial maps as living, upgradeable infrastructure rather than one-shot captures. Operators can refresh their facility maps over time, with the same or different scanning hardware, without re-authoring any anchors, navigation paths, or AR work instructions built against the original.
Operators capture the space again, with the same hardware or different, and activate the refreshed scan. Every device pointing at the original version of that map keeps working without code changes. Content authored against the original stays exactly where it was placed.
Map Versioning runs on the same VPS pipeline that powers MultiSet localization, not on traditional scan-merging techniques like Iterative Closest Point. That makes it robust under the cases where ICP fails: scans months apart, different hardware (iPhone LiDAR, Matterport, Leica, NavVis, Faro, XGRIDS), different sensor densities, different lighting, rearranged furniture.
Read the full Map Versioning launch post for the architectural detail, and see the Map Versioning docs and REST API reference for integration specifics.
v1.14.0 brings on-device localization to Android, matching the API surface MultiSet already ships on iOS. Alongside it, the release lands full hint API parity across all on-device VPS SDKs. The hint filtering behavior developers already use against cloud maps now runs identically on-device, regardless of platform. On-device object tracking is included.
The same MultiSet client SDK call returns a 6-DoF pose whether the resolve happens on-device or in the cloud. A single flag controls the deployment mode. This collapses what has historically been two integration paths into one.
On-device deployment matters in three classes of environment: regulated workflows where frames cannot leave the device (defense, healthcare, certain industrial sites), no-network environments (warehouse RF dead zones, offshore platforms, basement floors), and privacy-first wearable deployments. The frame stays on the device, and no network round-trip is required.
Robotics integrations also benefit. The on-device path is what makes MultiSet a credible cold-start and drift-correction layer for ROS 2 stacks running on AMRs without persistent cloud connectivity.
Beyond the two headline capabilities, v1.14.0 ships performance improvements that affect every customer running MultiSet in production.
The cloud localization path is materially faster end-to-end. Devices localize more quickly, and high-traffic deployments serve more queries per RPS unit of provisioned infrastructure. Reconstructed meshes from MultiSet maps now carry significantly more geometric detail, giving downstream consumers, BIM workflows, digital twin pipelines, and simulation environments a higher-fidelity spatial substrate to work against.
These improvements ship without API changes. Existing integrations pick them up automatically on upgrade.
All v1.14.0 capabilities continue to span the platforms MultiSet supports: Unity, native iOS and Android, WebXR, Meta Quest, and ROS 2. Map Versioning is fully scan-agnostic, consistent with the rest of the MultiSet ingestion pipeline. Versions in the same group can mix iPhone LiDAR captures with Matterport MatterPak, Leica RTC360, NavVis, Faro, XGRIDS, and the MultiSet Mapper iOS app, without the content layer ever moving.
v1.14.0 is the foundation for what MultiSet is bringing to AWE Long Beach, June 15 to 18, 2026. Additional capabilities tied to this release will be demonstrated live at the show. Customers running v1.14.0 in production already have the substrate those demonstrations are built on.
v1.14.0 is live now across MultiSet's public cloud deployment and rolling out to private-cloud, self-hosted, and on-device customers on each environment's standard cadence. New maps created today benefit from the denser mesh reconstruction automatically. Existing maps continue to work without changes. Map Versioning is opt-in per map.
The developer portal, REST API docs, and MultiSet Mapper iOS app are all updated for the release.
To see Map Versioning, on-device Android localization, or a full v1.14.0 walkthrough running against your environment, book a 30-minute call.
