Powered by Sneeze, the first open-source metaverse browser engine under the Metaverse Standards Forum, Artemis introduces metaverse browsing.

COLUMBUS, Ohio: $AI #AI--RP1® today launches Artemis™, the world’s first native metaverse browser. Artemis is available for download at rp1.com/artemis.

For three and a half decades, the World Wide Web and web browsers have connected people to pages. Web browsers removed the friction of accessing information on the internet, created interoperability across every device, and gave the world an open ecosystem to build on. Spatial computing has been waiting for the same thing: an open engine, open standards, and a browser that lets anyone access spatial experiences from any device without a separate install for each one. Artemis is the first browser built to do that, powered by Sneeze, an open-source engine that can be embedded into existing web browsers, built directly into devices, or used to power a new class of standalone metaverse browser.

Spatial computing is already taking hold in factories, airports, cities, and virtual environments. Physical AI, robotics, and autonomous systems all need to operate across shared physical and digital spaces. Digital twins are being deployed across industries, from manufacturing and logistics to aerospace to consumer products. Major technology companies, including Snap and Meta, are already bringing AR glasses to market, with more expected to follow in the years ahead. What all of these technologies share is a need for metaverse infrastructure, which the World Wide Web wasn't designed to support.

What is metaverse browsing

Instead of browsing pages, you browse places: physical environments enriched with spatially located services and content, or virtual environments and experiences that exist entirely in digital space.

A spatial fabric is the evolution of a website. On the web, you build a website, host it on your own server, and any browser can reach it. A spatial fabric works the same way: you build it and host it on your own infrastructure, whether it's anchored to the real world or exists entirely in virtual space. A metaverse browser connects to it in one of two ways: automatically, based on real-world proximity, the way AR glasses connect to the spatial fabric of the building you are standing in, or directly by URL, the way a browser on VR, desktop, or mobile reaches a website today. You are no longer building inside a platform that owns your assets and data. You own the fabric. You control it. No platform sits between you and end users or consumers.

Services are the live capabilities that attach to a spatial fabric: AI assistants, safety overlays, navigation tools, equipment monitors, training guides. Each service can come from a different, independent operator, and many can composite into the same scene simultaneously, the same way a web page can embed widgets, players, or ads from multiple sources at once. Every service runs in its own isolated, secure sandbox. The security model of the metaverse is built to be even stronger than the web's.

Here is what metaverse browsing looks like in practice.

A factory worker wearing AR glasses running a metaverse browser walks onto the floor. The browser connects to the factory's spatial fabric automatically. Equipment dashboards, safety overlays, and maintenance guides appear in context, each from an independent operator, without installing anything. The worker moves to the next building. New content loads. Old content unloads. The browser handles it.

An airport deploys its own spatial fabric on its own infrastructure. On the ground, crew wearing AR glasses connect automatically as they move through the terminal. From home, a remote operations manager joins the same spatial fabric directly by URL through a VR headset, with real-time co-presence: spatially positioned avatars, directional voice, and shared context across every device type.

These scenarios illustrate where the entire industry is heading. Artemis is the first browser purpose-built for spatial computing to achieve this milestone.

What Artemis delivers today

This initial release gives enterprises and independent developers early access to the Sneeze engine running in a native metaverse browser. Sneeze and Artemis are being developed in parallel: as the engine evolves, the browser evolves with it.

With Artemis today, developers can:

• Create a limited spatial fabric and host it on their own infrastructure
• Navigate to any spatial fabric directly via URL, with no per-app installs
• Experience content from multiple independent operators loading concurrently into a single scene, each running in its own secure sandbox

Additional capabilities, including embedded spatial services, are in active development. A broader showcase of the browser’s capabilities is planned for the Augmented Enterprise Summit in October 2026. Documentation and standards are available now at omb.wiki.

Why a new kind of browser

Every web browser runs on a web browser engine. Blink powers Chrome. WebKit powers Safari. Gecko powers Firefox. Those engines were designed for 2D documents from a single origin at a time. They were not designed for proximity-based content, multi-origin 3D scenes, or real-time spatial composition.

Before today, 3D content was typically composed using individual game engines, each proprietary and incompatible with the others. Like the web, spatial computing needs an interoperable solution where the browser handles the rendering, so publishers can focus exclusively on creating content rather than delivery and display.

Sneeze, developed by the Open Metaverse Browser Initiative (OMBI) under the Metaverse Standards Forum, is that browser engine. Purpose-built for spatial computing and released in June 2026 under the Apache 2.0 license, Sneeze is being architected to handle multi-origin 3D scene composition, proximity-based content loading, real-time co-presence, and cross-device rendering. The engine builds on established open standards from Khronos Group (ANARI, OpenXR, SPIR-V, glTF), W3C (WebAssembly, Decentralized Identifiers), and OGC (GeoPose). Sneeze can be embedded into existing web browsers, built directly into devices, or power standalone metaverse browsers like Artemis.

“When you use a metaverse browser for the first time, you will instantly experience the sensation of browsing, now with spatial, three-dimensional content,” said Dean Abramson, Co-Founder and Chief Architect, RP1. “It's impossible not to immediately recognize all of the benefits that we take for granted when browsing the web. Giving publishers the ability to focus on content, rather than its delivery and display, will drive the next revolution for spatializing nearly every location in the world. Even more so when enhanced with AI tools.”

Why the industry needs this

For enterprises: Enterprises are moving from web infrastructure to spatial infrastructure, and they need the exact same guarantees: own your data, host it on your own servers, and know that no single vendor can discontinue the platform underneath you. On the web, this is a given. In spatial computing, it has not existed until now. The pattern is well established: when walled-garden devices or software platforms are discontinued, every organization that built on them faces a choice between abandoning the work or rebuilding from scratch. That risk is the primary reason enterprises remain in proof-of-concept cycles.

Artemis and Sneeze change that. Because Sneeze is an open source browser engine, enterprises deploy spatial operations on infrastructure they control, and any organization can build a browser on the same foundation. Artemis is the first, and it is designed not to be the last.

For device manufacturers: AR glasses and XR devices are only as valuable as the spatial content available to browse on them, and no device manufacturer has the resources to build all of that content alone. Sneeze solves this with an open ecosystem: any enterprise, developer, creator, or independent operator can build spatial fabrics and services that instantly work on any device running the engine, without the manufacturer building or curating any of it. A proprietary content layer, one that enterprises and creators have no reason to build for, is not a path to scale. An open ecosystem the entire world can build on is.

For developers: Which engine do you build on? Which tools? Which platform? Whether you build for XR, gaming, user-generated content, or virtual world platforms, you have faced the same fragmented landscape: different engines, different tools, no shared standard. Sneeze creates a single open ecosystem built on established standards, the same way the web gave developers one set of standards to build for. What you build today works on Artemis and on any future browser that runs Sneeze. Your work is not locked to one engine, one company, or one platform.

For creators: Creators need to know that the skills they develop and the content they build will last. Open standards guarantee that. A spatial fabric built on Sneeze will work in any compliant metaverse browser for as long as the open-source engine exists, rather than disappearing when a proprietary platform shuts down.

“We set out to build the thing that was missing,” said Sean Mann, Co-Founder and CEO of RP1 and board member of the Metaverse Standards Forum. “The internet existed before the web browser, but the World Wide Web did not exist until someone built a web browser. Spatial experiences, digital twins, AR hardware; they all exist today. What was missing was the browser that ties them together. Artemis is that browser. And because it runs on an open-source engine, it will not be the only one. That is the entire point.”

Industry momentum

Sneeze was introduced at AWE 2026 to strong industry reception. Forbes called it something that “could have a big impact on the future of spatial computing.” GamesBeat wrote that the industry should “get ready for a world without app stores.” VR.org called it “the most encouraging announcement of AWE.”

The academic community is already mobilizing. The Open Metaverse Academic Alliance (OMAA), launched at the University of Rochester, brings universities into the same role they have always played in the evolution of the web: building research, developing talent, and working alongside enterprises to advance new standards.

RP1 is now in active conversations with enterprises and AR glass manufacturers about what comes next. If your organization is thinking about spatial computing, AR glasses, or what the next layer of infrastructure looks like, we want you in those conversations.

Get involved

• Download Artemis: rp1.com/artemis
• Explore the Sneeze source code: github.com/MetaversalCorp/Sneeze
• Read the documentation and standards: omb.wiki
• Join the Metaverse Standards Forum and the OMBI: metaverse-standards.org/open-metaverse-browser-initative
• Book a meeting: rp1.com/meet

About OMBI

The Open Metaverse Browser Initiative (OMBI), created by the Metaverse Standards Forum and RP1, brings together standards organizations, technology companies, developers, and researchers to build the spatial equivalent of the web browser. Open, interoperable, governed under the Metaverse Standards Forum, and owned by no single company.

Official page: metaverse-standards.org/open-metaverse-browser-initative

Documentation: omb.wiki

About RP1

RP1 created the world’s first metaverse browser, pioneering the next evolution of the World Wide Web, from flat pages to shared, spatial experiences accessible on any device. Today, RP1 leads the architecture of Sneeze, the open-source metaverse browser engine, through the Open Metaverse Browser Initiative at the Metaverse Standards Forum. RP1 is also building the world’s first native commercial metaverse browser and spatial infrastructure services that enable any organization to transition from web to spatial on infrastructure they own and control. Our mission is to connect the world through an open metaverse.

Website: rp1.com | OMBI documentation: omb.wiki

Fonte: Business Wire