<a target="_blank" rel="noopener noreferrer" href="https://docs.joinpeertube.org/use/create-upload-video#upload-a-new-version-of-a-video">Upload a new version of the video</a> if your administrator enabled this setting
Enable <a target="_blank" rel="noopener noreferrer" href="https://docs.joinpeertube.org/admin/configuration#live-streaming">live streaming</a> for your instance
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
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
Organize videos in public or private <a target="_blank" rel="noopener noreferrer" href="https://docs.joinpeertube.org/use/library#video-history">playlists</a>
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.