Publish your videos with PeerTube, the YouTube alternative

There are none at the moment: PeerTube is a tool that we wanted neutral in terms of monetization.

However, the uploader can display a support button under the video. This button displays a frame in which people who upload videos can display text, images, and links freely (link to Patreon, Tipeee, Paypal, Liberapay...).

We did not go any further, as we refuse to tie our code to a particular content funding method, that might not fit all communities and deter others. It's the reason why we encourage developers to use the PeerTube plugin API to create their own monetization system.

The installation guide is here (only in English).

Minimum hardware requirements:

• 1 vCore
• 1.5 GB of RAM
• Enough storage for videos
• 20Mbit/s upload network speed
• Enough bandwidth to broadcast videos

Recommended hardware requirements for a big instance to handle 1,000 concurrent viewers (see our blog post about our viewers stress test):

• 4 vCore
• 4 GB of RAM
• Enough storage for videos
• 1Gbit/s upload network speed
• Enough bandwidth to broadcast videos
• Read the scalability guide if you plan to have many users or viewers

If you plan to do transcoding on the same machine as the PeerTube instance:

• 8 vCore
• 8 GB of RAM

For a more detailed guide about hardware requirements:

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.

You will hugely benefit from at least a second thread though, because of transcoding. Transcoding is very cpu intensive. It serves two purposes on a PeerTube instance: it ensures all videos can be played optimally in the web interface, and it generates different resolutions for the same video.

Transcoding can also be offloaded to other machines using remote runners.

1.5 GB of RAM should be plenty for a basic PeerTube instance, which usually takes at most 500 MB in RAM. The only reason you might want more would be if you colocate your Redis or PostgreSQL services on a non-SSD system.

There are two important angles to storage: disk space usage and sustained read speed. To make a rough estimate of your disk space usage requirements, you want to know the answer to three questions:

• What is the total size of the videos you wish to stream?
• Do you want to enable transcoding? If so, do you want to provide multiple resolutions per video? Try this out with a few videos and you will get an idea of how much extra space is required per video and estimate a multiplication factor for future space allocation.
• Which sharing mechanisms do you want to enable? Just web video, or also HLS with P2P? If you want both, this will double your storage needs.

If you want to store many videos on your PeerTube instance, you may want to store videos externally using Object Storage.

In terms of read speed, you want to make sure that you can saturate your network uplink serving PeerTube videos. This should not be a problem with SSD disks, whereas traditional HDD should be accounted for: typical sustained read rates for a well tuned system with a 7200rpm hard disk should hover around 120 MB/s or 960 Mbit/s. The latter should be enough for a typical 1 Gbit/s network uplink.

A rough estimate of a traditional server's video streaming network capacity is usually quite straightforward. You simply divide your server's available bandwidth by the average bandwidth per stream, and you have an upper bound.

Take a server for example with a 1 Gbit/s uplink for example pushing out 1080p60 streams at 5 Mbit/s per stream. That means the absolute theoretical upper capacity bound is 200 simultaneous viewers if your server's disk i/o can keep up. Expect a bit less in practice.

But what if you need to serve more users? That's where PeerTube's federation feature shines. If other PeerTube instances following yours, chances are they have decided to mirror part of your instance! The feature is called "server redundancy" and caches your most popular videos to help serve additional viewers. While viewers themselves contribute a little additional bandwidth while watching the video in their browsers (mostly during surges), mirroring servers have a much greater uplink and will help your instance with sustained higher concurrent streaming.