Innoactive Portal
Cross-platform cloud streaming — XR applications rendered on cloud GPUs and delivered to every headset, browser, and desktop.
Getting started in four steps
Get your Innoactive Portal organization
Request an organization from the Innoactive team. You receive admin credentials, a dedicated subdomain, and an empty workspace to invite users into.
Install the Portal Client on your device
Pick the Portal Client for your hardware — Windows desktop, Meta Quest, HTC Vive, Pico, or Apple Vision Pro — and sign in with your Portal account.
Upload your application to Portal
Package your Unreal Engine, Unity, or NVIDIA Omniverse build and upload it to your Portal organization so it appears in the launcher.
Start a streaming session
Open the client, pick the application, and Portal allocates cloud rendering hardware in the nearest region. Annotations, deep links, and user groups all work out of the box.
Innoactive Portal is the cloud-streaming platform that lets IT roll out spatial workflows the way they'd roll out any other enterprise app. The knowledge base below is organised by the journey teams typically take: get the first user streaming, plug in the engines and scenes you already use, lock down access, deploy at scale, then dial in the network. Skip ahead to the section that matches where you are.
Release notes
35 entries →- Autodesk VRED Core Cloud streaming available on L40S and RTX PRO 6000
Downloads
Client apps and plugins for getting Portal running across your fleet. Client downloads require a Portal login.
Portal Client
Portal Client for PC
Windows desktop client for streaming Portal sessions.
Download →
Meta QuestPortal Client for Meta Quest
Standalone client for Meta Quest headsets.
Download →
HTC VivePortal Client for HTC Vive
Standalone client for HTC Vive Focus 3 / XR Elite.
Download →
PicoPortal Client for Pico
Standalone client for Pico Neo 3 Pro and Pico 4 Enterprise.
Download →
Apple Vision ProPortal Client for Apple Vision Pro
Provisioned through Apple Business Manager — request access for your organization.
Download →
Knowledge base
Set up your organization, invite users, pair headsets, and upload your first application to Innoactive Portal.
Getting started
Set up your Portal organization, invite the first users, upload an application, and pair a headset — the recommended starting path for new admins.
How to add a new user
Invite a user by email from the Control Panel, assign them to one or more user groups, and manage existing accounts when SSO is not enabled.
How to pair your device
Pair a headset to your Portal account with the six-digit code so any Portal app launches straight to the device.
How to upload an application on Portal
Upload an APK for standalone headsets or a ZIP with a Windows executable for streaming, then manage versions from the Portal Control Panel.
Best practices
Minimum network, application, and CloudXR/SteamVR settings every project must meet before going live on Portal — the checklist before opening a support ticket.
Day-to-day session control — personal servers, scheduling, hot machines, deep links, launch arguments, and collaborative streaming.
Start a personal streaming server
One-click personal cloud VM with your VR apps pre-installed and a six-hour session limit — for quick tests and short-notice demos with no admin setup.
Schedule and manage streaming sessions
Plan a Portal streaming session for a specific start and end time, invite multiple participants, and share a single confirmation link with all attendees.
How to prepare a streaming session in advance
Decide between a personal streaming server, a reserved hot machine, and a scheduled session with invites — and pick the right one for the use case.
How to auto-select VR or desktop access mode
Use the --portal-interface-mode launch argument to flip an app between its VR rig and desktop rig automatically based on how the user opens it on Portal.
Reserve a Hot machine with pre-installed applications
Pre-configure a cloud rendering machine for a defined time window and user group — minimal load time for client demos, training, and high-stakes streaming sessions.
How to create and use deep links
Generate URLs that launch a specific app or scene directly inside the Portal client on Quest, Vive, Pico, and Vision Pro.
How to use launch arguments
Pass user, session, device, and custom data to a VR app at launch time using Portal default arguments, executable arguments, or deep-link arguments.
Stream NVIDIA Omniverse Kit applications, author and ship OpenUSD content, and use Innoactive Portal as the launcher for your Omniverse stack.
First sessions, end-user and expert paths, and where Innoactive Portal fits into the Omniverse stack.
Stream Omniverse to XR headsets
Take a streamed Omniverse session from the browser to a Meta Quest, Pico, HTC Vive Focus, or Apple Vision Pro in three steps.
NVIDIA Omniverse
Landing page for Omniverse on Portal — paths for end users, Kit-app developers, and USD authors, with links to streaming, deployment, and data-prep guides.
Your first Omniverse streaming session in Innoactive Portal
Launch USD Composer, Explorer, or Presenter in a browser through Portal in five clicks — the fastest way to confirm Omniverse streaming works for a new user.
Getting Started with Omniverse Streaming for End Users
First steps for non-developers joining streamed Omniverse design reviews on a browser or XR headset — no workstation or local install required.
Leverage on Innoactive Portal as an Omniverse expert user
Entry point for Omniverse experts integrating custom Kit applications with Portal — points to the components overview and the Kit-app deployment guide.
Omniverse components and synergies with Innoactive Portal
How Innoactive Portal slots into the Omniverse stack — Kit applications, OpenUSD content, Nucleus server, and CloudXR streaming all the way to the headset.
Benefits of USD and how it integrates into Omniverse and Nucleus server
Why OpenUSD plus Omniverse plus Nucleus has become the default 3D pipeline for BMW, Siemens, and Zaha Hadid — and how the three pieces fit together.
How to set up collaborative streaming sessions in Omniverse with Live Sync
Generate a Live Sync streaming link straight from USD Composer with the Innoactive Link Share tool, then invite teammates on browsers or headsets.
Bootstrap your own Omniverse Kit application and ship it as a streamable Portal app.
How to create and stream your own Kit app
Bootstrap a custom Omniverse Kit application from kit-app-template, wrap it with the Innoactive extensions, and ship it as a streamable Portal app.
How to visualize USD files stored in a Nucleus server
Stream your own protected USD files from either the Innoactive Nucleus enterprise server or a private Nucleus, with redirected authentication to a local browser.
From CAD/DCC assets to a clean modular OpenUSD project — layers, variants, animations, and data preparation.
Glossary, debugging tools, project structure, and CI/CD examples for OpenUSD on Portal.
How to create your own CI/CD pipeline (Omniverse example)
A working GitHub Actions YAML you can copy into an Omniverse Kit repo to build, package, and upload new versions to Portal on every push.
LIVRPS Debugging with IDE
Fix the yellow V and I composition warnings in OpenUSD by inspecting layers directly in VS Code or Cursor when the Omniverse UI cannot resolve them.
Glossary for OpenUSD workflows section
Reference glossary of every OpenUSD, Omniverse, and digital-twin term used across the Innoactive tutorial series, with examples and difficulty ratings.
Manage users, user groups, single sign-on, and per-application access control across your Portal organization.
Authentication and single sign on (SSO)
Enable email login, Microsoft Entra ID, Google Workspace, OpenID Connect, or SAML for Portal users — and combine providers in the same organization.
User groups and permissions
Group-based access model used in Portal — users inherit permissions from every group they belong to, with platform and per-application permissions managed separately.
How to implement Access Control Plugin for Portal
Add the Innoactive Access Control plugin to a Unity or Unreal build so the app only runs when launched through the Portal Desktop Client by an authorised user.
Access Control Plugin download
Download the Access Control Plugin packages for Unity and Unreal Engine versions 4.23 through 5.x to lock distributed builds to authorised Portal users.
Move users to a user group via API
Worked example using GET, POST, and DELETE on the Portal /groups/<id>/users/ endpoint to move users between groups in bulk from a script.
Roll Innoactive Portal out to a fleet — MDM provisioning, sideloading, enterprise stores, client updates, and event preparation.
How to use Innoactive Portal with MDMs
Pair Portal with Meta Horizon, ArborXR, ManageXR, or Intune so MDMs handle devices and Portal handles users, APK hosting, and PCVR streaming.
How to sideload Innoactive Portal client on standalone devices - Meta Quest sideloading
Sideload the Portal APK on Meta Quest using either a Meta Developer Organization or SideQuest — for evaluation before moving to App Lab or MDM distribution.
Innoactive Portal VR client download from official enterprise stores
Direct store links to install the Portal VR client on Meta Quest, HTC Vive Focus 3, and Pico headsets through their official enterprise distribution channels.
How to subscribe to Portal Clients updates
Three channels — email, RSS feed, and MDM push — to receive new Portal VR and Desktop client releases as soon as they ship.
How to plan and prepare for a successful event or demo
Pre-event checklist for live Portal demos — apps uploaded, permissions granted, region pinned, headsets paired, deep links tested, and a dry run completed.
Firewall configuration, IP ranges, and corporate-network guidance for streaming through Innoactive Portal.
Ports, protocols, IP ranges, and IT-conversation prep for streaming through the Portal cloud rendering fleet.
Firewall configuration and IP / Port whitelisting for Cloud streaming
Corporate firewall rules — UDP and TCP ports, protocols, and directions — required for Wireguard, DCV, WebRTC, and CloudXR traffic on the Portal cloud platform.
IP ranges
AWS and Azure IP ranges for the Portal cloud-rendering fleet — paste into firewall allowlists for enterprise networks.
Proxy IP addresses
The three STUN/TURN server IPs and ports Innoactive operates as relays — always required in firewall allowlists alongside the cloud rendering ranges.
How to overcome network restrictions
Workarounds when a corporate network blocks a streaming session — disable VPN, switch to guest Wi-Fi, or fall back to a 5G mobile hotspot.
How to prepare for a discussion with your IT department
Strategies to shrink the IP allowlist, request Fixed IPs, and reduce UDP exposure so IT teams can approve Portal cloud streaming with confidence.
Common network error messages and glossary
What "latency too high", "bandwidth too low", and "unstable connection" actually mean during a Portal streaming session, and where each issue comes from.
How to optimize your network connection to improve your streaming experience
A three-step routine — wired test, Wi-Fi test, then router tuning — to diagnose and improve a network before blaming the streaming session.
Manual region selection, hardware tiers, fresh-VM bootstrap, and Desktop Client log files.
How to manually select a specific location for cloud rendering
Switch from automatic to manual mode in Cloud Preferences to pin every streaming session to a specific region and cloud provider.
How to manually select more powerful hardware for cloud rendering
Bump an application to a higher performance tier in Control Panel when default cloud rendering hardware cannot keep up with a heavy scene.
How to request a new cloud rendering machine when starting a streaming session
Append forceColdVm=1 to a Portal launch URL to skip the cached VM and start the next streaming session on a fresh cloud rendering machine.
How to find log files of Portal Desktop Client
Open the Portal Desktop Client logs folder in two clicks from the Windows system tray when you need to send diagnostics to support.
API reference, engine plugins, CI/CD pipelines, and compatibility documentation for IT and developers.
REST API authentication, endpoints, and example payloads.
API
Entry point to the Innoactive Portal REST API reference, with a worked example for moving users between groups programmatically.
How to use the Innoactive Portal API
Get oriented in the Portal REST API — OAuth2 and BasicAuth authentication, JSON payloads, and the api.innoactive.io base URL — before scripting integrations.
Innoactive plugins for Unreal Engine — downloads, integration, and Vision Pro local-streaming settings.
Unreal Engine Plugin for Cloud streaming - download
Download Portal Streamer plugin builds for Unreal Engine 5.2, 5.3, and 5.4 so you can upload UE projects to Portal directly from the editor.
Unreal Engine Plugin for Cloud streaming
Drop the Innoactive Portal plugin into an Unreal project to upload and stream builds straight to Portal without leaving the editor.
Unreal Engine settings for Apple Vision Pro local streaming
Project, material, and post-process settings an Unreal 5.5 build needs to render passthrough-correct alpha when streamed locally to Apple Vision Pro.
Build, package, and upload Portal apps automatically with GitHub Actions and semantic-release.
Supported engines and headsets, Portal system requirements, FAQ, and cookies policy.
Supported platforms and exceptions
Which engines, build types, and headsets Portal supports for PCVR, standalone, and 3D desktop apps — and the known edge cases that need a workaround.
Innoactive Portal requirements and specifications
Top-level entry to the Portal compatibility section, pointing to best-practice requirements and the list of supported platforms and known exceptions.
Cookies list
First-party and third-party cookies set by Portal subdomains, including name, validity, and the domains that issue them — useful for privacy reviews.
FAQ
Short answers to the questions Innoactive teams hear most often about Portal — supported engines, MDM differences, standalone vs PCVR, analytics, and branding.