Meetings, screen sharing and huddles, with sound and video encrypted in your browser before they're sent. Our media server passes on data it can't open. Included in every plan.
Bring meetings, screen sharing and quick huddles to your browser, with sound and picture encrypted before they leave it.
Sound, video and shared screens are encrypted on your device, frame by frame. Each call has its own key, sealed with the key of the channel, event or meeting room it belongs to, and our servers hand it only to the people in the call. The media server forwards the encrypted frames and can't decode them. There's no unencrypted mode, and a browser that can't encrypt can't join.
Click Huddle in a channel or a direct message and you're talking. The channel shows who's in it, and the people in the channel join with one click. A huddle starts with sound only and stays in a small window while you work elsewhere in the suite.
Turn on Add Jelly Video for an event. Its guests see Join on the event and in the reminder, from ten minutes before it starts until it ends. Only people the event is shared with can get in.
A shared screen takes the stage and everyone else moves to a strip below. Raised hands are listed in the order they went up, and six reactions float up over the call. All of it is encrypted like the call itself.
Start a meeting from the Jelly Video home and share it with people from your contacts, or copy its link. The link only works for people the meeting is shared with.
Pick your devices and choose to join with the microphone or camera off. Opening a meeting link turns nothing on: you see your camera and your microphone level when you ask for the preview.
Hosts can mute someone, lower a hand, remove a person, lock the call so nobody new gets in, and end it for everyone. Other people's devices take a lowered hand only from a host they can check for themselves, from signed shares, not from our server's say-so.
A name appears only when that person's device has proved who it is, inside the encrypted call. Guests you've never met are shown by @handle when the person who invited them vouches for them, and the call's details say who vouched. Anyone else shows as an unverified participant, with a warning. One limit: a person in the call working together with our media server could pass off their own sound or picture as another participant's. Our servers alone can't.
When a host removes someone, our servers stop handing them keys and the call moves to a new key. When a person loses access to the channel, event or meeting room itself, that gets a new key too, one they can't open.
In a meeting, messages reach the people in the call at that moment and nothing is kept when it ends. In a huddle, they're kept as a thread in the channel.
Starting a huddle in a direct message, or a meeting shared with up to eight people, rings them for 30 seconds, with Accept and Decline. A conversation you muted doesn't ring. When you accept, your microphone stays off until the person calling has proved who they are in the call, with a key your device already trusts.
Grid or speaker view, with whoever is speaking outlined. The grid shows 25 people a page.
The call fits a phone's browser, with the controls along the bottom. On a computer there are shortcuts for the microphone, the camera, sharing and raising a hand.
Recording and transcripts would need the sound and video unencrypted somewhere other than the devices in the call, so they can't simply be switched on at our end.
No sound, video or chat from a call is ever stored. While a call runs, our media server passes encrypted data between the people in it, and our servers know who is connected, when, and how much they send.