Self-hosted installs and MDM - xpander.ai

Omni Desktop connects to whichever xpander its address points at. With a self-hosted install, members enter your install’s address on first run, for example chat.acme.com, and everything else follows from it.

Hybrid and Air-gapped

	What happens
Sign-in	Members sign in on your install’s own web page, with your install’s sign-in (including single sign-on). No extra redirect address needs to be registered anywhere.
Download and updates	Your install carries the app builds and serves the download page at `https://<your install>/desktop/` and the app’s updates from the same address. Neither members’ computers nor your install need the internet for them, so this works the same on an Air-gapped install.
Agents and files	Agents run on your install. The app connects out to your install only; nothing listens on the laptop.
Policy and devices	Set on your install’s Platform, the same Devices and Desktop policy pages.

Members’ Macs must reach your install’s address over HTTPS, for example on your network or VPN.

Point every Mac at your xpander with MDM

Set the address for every Mac with a configuration profile from your MDM (Jamf, Kandji, Intune or another):

Field	Value
Payload domain (preference domain)	`ai.xpander.desktop`
Key	`ServerUrl`
Value	Your xpander’s address, for example `https://chat.acme.com`

<dict>
  <key>ServerUrl</key>
  <string>https://chat.acme.com</string>
</dict>

With the profile installed, the app opens on that address, shows Set by your organization, and members cannot change it.

Welcome to Omni screen with the xpander URL field locked to xpander.acme.internal and the note Set by your organization — The first run on a Mac whose address is set by MDM. Shown with sample data.