> For the complete documentation index, see [llms.txt](https://unity.zoeimmersive.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://unity.zoeimmersive.com/bridge-xr/start-here/architecture-and-requirements.md).

# Architecture & Requirements

Bridge XR combines hosted services, playback surfaces, and a Unity workflow.

### Core components

#### Authentication

Bridge XR can connect to your institution's existing SSO provider.

#### Backend services

The backend runs in your cloud environment and handles platform logic, data, and experience delivery.

#### Storage and database

You need:

* object storage for uploaded experience bundles
* a PostgreSQL database for platform data

#### Web Dashboard

The web dashboard is the browser-based management surface.

It is hosted on your infrastructure and includes the **web player** for Unity web exports.

#### Bridge XR App

The app is the installed client used to play experiences on Meta Quest headsets.

This is the headset-based player in the Bridge XR platform.

#### Unity authoring stack

Developers need:

* Unity
* **Zoe for Unity**
* the **Bridge XR integration package**

This stack is used to build, prepare, and upload experiences.

Developers can export for different playback targets, including the web.

### What your team needs to plan

* a URL for the web dashboard
* a cloud environment for frontend and backend hosting
* object storage
* a PostgreSQL database
* an SSO setup
* a distribution method for the Bridge XR app
* a plan for which experiences run in the browser and which run on Meta Quest

### Typical ownership

* **IT / platform owners**: infrastructure, SSO, app rollout
* **Administrators**: workspace setup and member access
* **Developers**: Unity workflow and uploads

### Infrastructure diagram

<figure><img src="/files/yb4FyUdcWLzicPeqOaFZ" alt="Bridge XR infrastructure diagram"><figcaption><p>Bridge XR infrastructure diagram</p></figcaption></figure>