On-premise deployment overview
The three deployment modes and what changes in each.
Most Meetbook workspaces run on the standard managed cloud service. For organizations with stricter data-residency, security, or compliance requirements, Meetbook also supports deployment modes that keep data within the customer's own environment.
The three modes
- Standard cloud — the default. Meetbook's managed infrastructure, no setup required beyond signing up.
- Dedicated/hosted — your workspace runs on isolated infrastructure rather than shared multi-tenant cloud, while Meetbook still manages the deployment.
- Fully on-premise / self-hosted — the entire stack runs inside your own infrastructure (your cloud account or data center), with your organization controlling data residency completely.
What changes on-premise
- Data never leaves your own environment — see Where is my meeting data stored? for the standard-cloud equivalent.
- Sign-up is typically invitation-only rather than open self-serve, since deployments are provisioned per customer.
- Some usage-based billing concepts (seats, AI credits, recording minutes) may work differently depending on the licensing model agreed for the deployment.
- Image signing and stricter update controls apply — see Image signing and invitation-only signup.
Getting started
On-premise deployment is set up in coordination with Meetbook, not a self-serve toggle — contact support or your account representative to scope a deployment for your organization.