title: Out-of-the-Box vs Self-Hosted | Iristick.Teams Deployment Options description: Compare Iristick.Teams deployment options: cloud-hosted OOTB for fast setup or self-hosted for enterprise-grade data control in your own Azure environment.
Out-of-the-Box vs. Self-Hosted
Iristick.Teams can be deployed in two ways: a fast cloud-based setup hosted by Iristick, or a secure self-hosted setup within your own Microsoft Azure environment.
Why an Azure Communication Services resource is involved at all
Iristick.Teams is a third-party app, so it must use Microsoft's Azure Communication Services to join Teams meetings — the official Teams client uses internal Microsoft endpoints not available to third parties. The ACS resource is a key issuer, not a data pipe. It mints short-lived tokens and provides a routing endpoint. Call audio and video flow peer-to-peer through Microsoft-operated relays, never through the ACS resource owner's infrastructure. The single architectural difference between OOTB and self-hosted is who owns that ACS resource and the token-broker backend: Iristick (OOTB) or you (self-hosted). Full detail: Why an ACS resource is required.
Out-of-the-Box (OOTB)
The fastest way to get started with Iristick.Teams.
Key Benefits
- Hosted and maintained by Iristick
- Minimal Azure configuration required (IT Admin Setup Guide)
- Ready-to-use after one-time admin setup: install the app, activate glasses, and sign in
- Always running the latest version via Google Play updates
Requirements
- Microsoft 365 Business account with Teams access
- One-time Azure admin setup (IT Admin Setup Guide)
- Iristick.Teams app installed on an Android smartphone
- Activated Iristick smart glasses (licensed with 1LMST)
Best For
- Quick rollouts
- Small or medium-sized teams
- Organizations without strict IT policies
Connection Flow
Self-Hosted
Designed for companies with strict data policies or IT-managed infrastructure.
Key Benefits
- Complete control over infrastructure and permissions
- ACS, token broker, and metadata backend all run in your Azure subscription instead of Iristick's
- No user information or call summaries stored on Iristick infrastructure
- App deployed via your MDM (Mobile Device Management) system
Call media is the same in both deployments
Call audio and video always flow directly between the device and Microsoft's Azure Communication Services — never through Iristick servers, in either OOTB or self-hosted. The self-hosted choice is about removing Iristick-controlled infrastructure from the path, not about protecting call content.
What You Need
- Microsoft Azure subscription
- Azure tenant ID and Communication Services resource
- App registration within your Azure Active Directory
- MDM system to distribute the Iristick.Teams app
- Installation license (1SHIMST) and maintenance license (4SHIMSTMU)
What We Provide
- App binaries and Azure integration package
- Step-by-step installation guide
- 8 hours of setup support
- Ongoing updates through the maintenance license
Best For
- Enterprise environments
- IT departments requiring full control over authentication and data
- Regulated industries or sensitive use cases
Connection Flow
Not Sure Which One Fits?
| Feature | Out-of-the-Box | Self-Hosted |
|---|---|---|
| Setup time | Instant | Requires IT configuration |
| Hosting | Managed by Iristick | Managed by your IT team |
| Updates | Automatic via Play Store | Delivered via license |
| Metadata location | Iristick backend | Your Azure tenant |
| ACS resource | Iristick subscription | Your subscription |
| Call media (audio/video) | Microsoft ACS — not Iristick | Microsoft ACS — not Iristick |
| Custom Azure setup | Not needed | Required |
| Best for | Fast onboarding | Controlled, secure rollout |
Still unsure? Reach out to us and we’ll help you pick the best option for your use case.