Server Deployment

Guidelines to deploy BridgeXR backend and web frontend on your servers.

Use this page to deploy the Bridge XR backend and web dashboard on your own infrastructure.

What gets deployed

Your deployment includes:

• the backend

• the web dashboard

• the web player for browser-based experiences

• storage and database services used by the platform

The Bridge XR App is separate from this deployment flow. It is distributed to Meta Quest headsets after the platform is live.

Before you start

1. Fill out the onboarding form.

2. Define the dashboard URL, such as bridgexr.yourdomain.com.

3. Share that URL with the Zoe Immersive team as early as possible.

4. Prepare your SSO setup with SSO configuration.

Without the final dashboard URL, your Bridge XR clients and integrations cannot point to the correct server.

Infrastructure requirements

You need:

• S3-compatible object storage or Azure Blob Storage

• a PostgreSQL database

• a Bridge XR backend service

• a Bridge XR frontend service

Suggested starting sizes

• backend: around 10 GB storage, 2 CPU, 2 GB RAM

• object storage: around 50 GB to start

• database: around 20 GB to start

Actual sizing depends on experience size, participant count, and usage frequency.

Deployment steps

1. Download the Bridge XR Web Files from the Zoe for Unity download page. Note: Make sure you are logged in with the correct account; otherwise you won't see those files.

2. Deploy the frontend files to a web server suitable for a single-page app.

3. Run the backend service on your Linux environment.

4. Seed the database with the provided script.

5. Connect SSO with SSO Integration.

6. Validate the platform in a testing environment if available.

7. Promote the deployment to production.

After deployment

Once deployment is complete:

• add members in Manage Organization and Members

• create modules in Create and Manage Modules

• distribute the XR app to Meta Quest headsets.