But some pars of PeerTube can be horizontally scaled to bypass the following limits, as described in our <a target="_blank" rel="noopener noreferrer" href="https://docs.joinpeertube.org/maintain/configuration#scalability">scalability guide</a>:
Communicate with the streamer and other viewers using the <a target="_blank" rel="noopener noreferrer" href="https://livingston.frama.io/peertube-plugin-livechat/">livechat PeerTube plugin</a>
Communicate with your viewers using the <a target="_blank" rel="noopener noreferrer" href="https://livingston.frama.io/peertube-plugin-livechat/">livechat PeerTube plugin</a>
Hiring another developer, developing an official mobile app, promoting the PeerTube ecosystem... These are a few of the things we plan to do in 2024, on top of an exciting v7 roadmap.
Read the <a target="_blank" rel="noopener noreferrer" href="https://docs.joinpeertube.org/maintain/configuration#scalability">scalability guide</a> if you plan to have many users or viewers
Recommended hardware requirements for a big instance to handle 1,000 concurrent viewers (see our <a target="_blank" rel="noopener noreferrer" href="https://joinpeertube.org/news/stress-test-2023">blog post about our viewers stress test</a>):
The feature is called <a href="https://docs.joinpeertube.org/admin/following-instances#instances-redundancy" target="_blank">"server redundancy"</a> and caches your most popular videos to help serve additional viewers.
Transcoding can also be offloaded to other machines using <a target="_blank" rel="noopener noreferrer" href="https://docs.joinpeertube.org/admin/remote-runners">remote runners</a>.