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>
Control the PeerTube player embed using the <a target="_blank" rel="noopener noreferrer" href="https://docs.joinpeertube.org/api/embed-player">embed API</a>
Create public <a target="_blank" rel="noopener noreferrer" href="https://docs.joinpeertube.org/use/library#playlist">playlists</a> assigned to your channel to organize your content or remote videos
Develop plugins and themes using the <a target="_blank" rel="noopener noreferrer" href="https://docs.joinpeertube.org/contribute/plugins">getting started guide</a>
Discover our recommendations selected among the <strong>%{ videos } videos</strong> and the <strong>%{ platforms } platforms</strong> of the PeerTube network
Enable <a target="_blank" rel="noopener noreferrer" href="https://docs.joinpeertube.org/admin/configuration#live-streaming">live streaming</a> for your instance
Enable or disable signup, <a target="_blank" rel="noopener noreferrer" href="https://docs.joinpeertube.org/admin/managing-users#registration-approval">approve manually new users</a> or set upload limits
Except for video transcoding, a PeerTube instance is not CPU bound. Neither Nginx, PeerTube itself, PostgreSQL nor Redis require a lot of computing power. If it were only for those, one could easily get by with just one thread/vCPU.