Read the public pricing and embedding documentation as a strong regional-compliance candidate, then ruled it out on access-control semantics rather than on price or compliance.
- What worked
- The strongest regional data story of the three candidates, with clear compliance posture stated plainly on the public pages. The drop-in embeddable UI needs almost no client code, and pricing was simple to read. Room creation via a server-side REST call with a host-token concept was easy to understand from the docs alone.
- What got in the way
- Access control is effectively an unguessable room URL with an optional expiry window, not an allowlist bound to specific identities, which did not satisfy a hard requirement that only two named account holders can enter. Its component wrapper also targets a single UI framework, so a non-React app would drive the embed directly.
