Our always-on solution with Daily.co TV now supports larger live streams. We can configure your portal so 8 locations, each with Ethernet, can stream to each other all day. Or you can support fewer always-on locations, but with more drop-in users. This is our TV solution, by the way. If you don't need a TV, it's easy to set up a secure always-on portal on your website, app or team dashboard. See the software always-on blog post.
For teams with remotes or distributed locations, an always-on portal is a video call that’s left open for remotes and other office TVs. It’s a virtual office or water cooler, no matter where everyone physically is.
When a portal streams live video all day, you’re using a lot of data over time. That’s why the number of colleagues who join matters. The key is how you use the portal, and your connection type.
We’ve reworked our architecture, to allow more efficient always-on streaming when possible. Below we explain how Ethernet versus Wifi affects your portal setup, and how our new architecture gives you more options.
The goal of our always-on customers is to strengthen their sense of team, whether that's helping remotes feel like they're in the room, or linking offices to build a sense of the company.
Always-on with Daily.co TV does more than the typical portal. There’s no typing or clicking. Just plug in your TV (or any 1080p screen). The TV automatically joins the shared stream. You can link TVs and remotes into the portal, too.
Typically, teams tend to use portals for a constant stream, drop-in, or a hybrid of the two. In a constant stream, participants are in the portal several hours each day, and often all day. In other use cases, remotes join the portal for a limited amount of time. For example:
In each of these portals, a participant sends and receives their video and audio to and from the other call participants, through the Internet.
Our lead developer Kwindla wrote a blog post describing how video calls work. Kwin’s post is written for non technical readers. It’s about a 5 minutes read, if you’d like to read his walkthrough yourself.
For each call, we either route all your video and audio peer-to-peer, or through one of our Internet servers in the cloud.
Services like Google Drive and Dropbox have made the cloud model familiar. In a video call that uses the cloud, your devices talk to a central server. You send your media to the server, and the server sends you other guests’ streams. The server is the hub for the call, efficiently routing media to all the spokes (aka, participants).
Peer-to-peer, aka p2p, is what it sounds like. Instead of going through the cloud, you talk directly to the other guests. (Kwin’s p2p post describes how that’s possible.)
If your TV is in your Nashville office, and it wants to talk to a TV in your New York office, peer-to-peer is efficient. You talk directly, Nashville to New York. You don’t have to go through a server that might be in, say, Seattle.
But as Kwin describes, as a video call gets larger, peer-to-peer can bog down. If you have 15 people in a call, it’s more efficient to ping one server, than to ping 15 separate devices.
A complicating factor to all this? Cost. Using the cloud is usually more expensive. (You spend resources either on setting up servers or leasing servers from companies like Amazon or Google.)
One final note: privacy. All our Daily.co video calls adhere to strict encryption and privacy standards. We’ve built this into all our designs. Peer-to-peer calls are encrypted end-to-end. Cloud calls are encrypted to and from our servers.
To be most effective, Daily.co video calls use a hybrid approach. By default, a meeting with 4 or fewer participants is peer-to-peer. When a fifth person joins, the call switches to the cloud.
This lets us offer the speed and privacy of p2p on basic calls, while using the cloud to make larger calls possible.
Our default always-on is built on top of this architecture, and it works well for smaller portals. Peer-to-peer is an excellent, efficient way to handle a constant stream between a few locations. However, that previously meant larger constant streams weren’t tenable, since they'd constantly stream over the cloud, which is cost-prohibitive.
This reality actually worked well for what our customers needed. Our initial customer demand was for smaller constant streams. A few locations worked fine for many of those teams to start; several wanted to test with a couple locations.
To launch our always-on, we focused on the need at hand, and released always-on with a 4-participant constant stream limit.
One of the neat things about always-on is customers really like how radically simple it is. It’s laser focused on fixing a pain point customers identified. We quickly started fielding requests for larger portals, and we're glad to now support them!
In our backend, we change your meeting link so it’s always peer-to-peer. That’s cost-effective, but requires Ethernet.
In an eight-location peer-to-peer call, each location is sending and receiving 7 video streams all the time. (One video stream to and from each of the other participants.) We manage how much bandwidth each stream uses, so we can adjust video and audio resolution based on your Internet connections.
This strategy works great for Ethernet, because on a wired Ethernet network, every device has its own cable for sending and receiving audio and video data packets.
On Wifi networks, though, everyone connected to the Wifi network has to share the radio spectrum. Local Wifi networks always have some amount of packet loss, when multiple devices try to transmit at the same time. Normally, this is fine. For things like web pages, email, or Youtube video, the missing data packets can be resent.
But for live video calls, there isn’t time to resend packets. Each dropped data packet causes a little bit of visible or audible quality loss in the call. When a Daily.co device is trying to send and receive 14 video streams (seven sending, and seven receiving), that’s a lot of data packets. And almost all Wifi networks will see increased packet loss in this situation.
In our backend, we can customize how your portal works depending on your network configuration and your expected meeting size. For eight-location, always-on configurations, when your devices open the portal, your meeting link is customized to stay peer-to-peer. It doesn’t switch to the cloud.
To reiterate, for now, you don’t want anyone on Wifi joining a larger p2p portal. Negotiating lots of p2p video on Wifi will bog down their device — and potentially cause the portal to crash.
Having said that, this is our current setup. Please stay tuned. We’ve got some key updates in the coming months ahead for always-on.
New custom option: 8 constant streams, on Ethernet
Contact us to turn this on. We customize your portal to allow up to 8 participants streaming all the time.
Default option: smaller constant streams, that allow remote Wifi and drop-in
If you have a portal where only 4 or fewer are constantly streaming, your portal is small enough you can go ahead with a few options:
We try to do things based on common sense — in this case, usually the drop-in exception isn’t a problem, so we allow it. If we see issues, we’ll contact you to change the setup. So far it’s worked, and we’re glad we can be flexible.
Many thanks to our always-on customers who’ve waited for this update! We appreciate it, and have really enjoyed hearing about the portal locations across the world.
Earlier, we mentioned we’re continuing our architecture work. If you’re interested in a larger portal for your team, please stay tuned.
Let us know what we can clarify! We’re proud our always-on is really useful to our customers — we’re eager to continue getting feedback. Cheers, and here’s to better remote team work.