Native In-Client Experience — Without Bots or Proxy Users
NextPlane OpenHub delivers a native Teams and Google Workspace experience for chat, group chat, channels/spaces, file sharing, and supported voice/video scenarios—directly inside each platform’s client.
Unlike proxy-based approaches, this is achieved without bots, vendor-controlled users, or end-user setup.
Single-Tenant Architecture with Customer-Owned Deployment
OpenHub is deployed as a dedicated, single-tenant service and can run in the customer’s own GCP project. This architecture keeps customer data under customer control, supports strict data residency requirements, and avoids the shared-tenant risk model used by SaaS interop platforms like Mio.
Customer-Owned Identity — No Synthetic Users or Impersonation
Mio relies on Mio-managed guest users and persistent impersonation rights to simulate native collaboration, effectively extending the enterprise trust perimeter to an external SaaS provider.
NextPlane takes the opposite approach. OpenHub does not introduce synthetic or vendor-controlled users and does not require cross-tenant impersonation.
All users and guest accounts are created and governed by the customer using their existing identity, security, and compliance policies in Microsoft Teams and Google Workspace. OpenHub connects only these customer-sanctioned identities, operating entirely within existing governance boundaries.
By avoiding synthetic identities and impersonation, NextPlane significantly reduces friction across security, legal, and compliance—and helps POCs progress cleanly to production.
Minimal, Scoped Permissions Aligned with Enterprise IAM
OpenHub requests only the domain-wide delegations and application-level permissions required for interoperability, using tightly scoped and auditable access aligned with Google and Microsoft best practices.
There are no hidden identity insertions, no unmanaged guest sprawl, and no permanent elevated privileges.
Native Administration via Teams and Google Workspace Consoles
NextPlane does not provide or require a separate OpenHub admin console. All configuration and ongoing management are performed directly within the existing Microsoft Teams and Google Workspace admin consoles.
Unlike Mio, OpenHub does not require customers to operate or maintain a list of users and platforms, eliminating additional administrative layers, operational overhead, and risk.
Usage-Based Licensing Without Guest or Proxy User Costs
NextPlane uses a pay-for-what-you-use licensing model based on monthly active unique users. There is no need to assign licenses to individual users or manage guest licensing SKUs—reducing both costs and administrative burden.
Faster, Lower-Risk Deployment
Because OpenHub avoids synthetic identities or proxy tenants (for external interoperability) and expanded impersonation rights, deployment is measured in weeks rather than months.
This significantly reduces security review cycles, legal scrutiny, and compliance delays that often stall Mio deployments before production.
Expanding Interoperability Roadmap
NextPlane continues to expand interoperability capabilities, including external federation and enhanced Teams ↔ Google calling, available through early-adopter programs—without changing the underlying security or identity model.
