Skip to main content
Can Vexa join Zoom through the Zoom SDK or RTMS? Today: No. Zoom joins via the web client in 0.12.x; the native SDK and OBF-token path is not carried. Sponsorable: yes — The SDK and RTMS route, for the meetings the web client cannot reach.
Reach Zoom meetings the browser bot cannot enter.

​
What it does

  • Joins through the Zoom SDK and RTMS rather than the web client.
  • Covers rooms and configurations that refuse a browser guest.
  • Sits alongside the existing web-client route, not instead of it.

​
What exists today

Zoom joins via the web client in 0.12.x. The native SDK and OBF-token path is not carried.

​
What this adds

The SDK and RTMS route, for the meetings the web client cannot reach.

​
How sponsorship works

You fund the item. It moves to the front of the queue. You co-write the acceptance criteria, so “done” means done on your meetings. Your name goes on the release note. Sponsorship buys the order of the queue — never exclusivity, never a private build, and never a date the work has not earned. The fee basis is per item or per stage, agreed in writing before work begins.

​
Two doors

Sponsor this

Fifteen minutes. Bring the constraint you are under.

Watch this

One email when it ships. The mail is already written — send it as it is.

​
Questions

No. Zoom joins via the web client in 0.12.x; the native SDK and OBF-token path is not carried.
The SDK and RTMS route, for the meetings the web client cannot reach.
It ships upstream under Apache-2.0, to everyone, with the sponsor named on the release note.
Ships upstream Apache-2.0 when sponsored.