Consequently, PeerTube development and/or management of websites associated with the PeerTube project (<a target="_blank" rel="noopener noreferrer" href="https://joinpeertube.org">joinpeertube.org</a>, <a target="_blank" rel="noopener noreferrer" href="https://instances.joinpeertube.org">instances.joinpeertube.org</a>, <a target="_blank" rel="noopener noreferrer" href="https://search.joinpeertube.org/">search.joinpeertube.org</a>, etc.) may not please everyone (in particular because of different ideas, ideologies of cultures).
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.
Organize videos in public or private <a target="_blank" rel="noopener noreferrer" href="https://docs.joinpeertube.org/use/library#video-history">playlists</a>
Develop plugins and themes using the <a target="_blank" rel="noopener noreferrer" href="https://docs.joinpeertube.org/contribute/plugins">getting started guide</a>