PeerTube

Key features

• ActivityPub federation Independent instances exchange follows, subscriptions, and video metadata through the ActivityPub protocol, so an account on one instance participates in a larger video network rather than a single company's database.[1][2]

• Per-instance moderation Each instance is built, managed, and moderated by its owner, with registration approval, user management, muting, and reporting tools instead of one global opaque policy.[1][2]

• Peer-to-peer playback Viewers share video segments with each other over WebRTC while watching, which reduces server bandwidth load when a video becomes popular.[1]

• Live streaming and transcoding Instances support publishing live streams alongside uploaded videos, with ffmpeg-based transcoding producing adaptive HLS output.[1][2]

• YouTube and Vimeo channel sync Creators can automatically synchronize a channel from a remote platform such as YouTube or Vimeo, which gives an evidenced migration path off centralized hosting.[1][2]

• Built-in Studio editing The web interface includes a Studio for trimming videos, adding watermarks and intros or outros, uploading replacement versions, and viewing per-video statistics.[1][2]

• Mobile apps with offline viewing Official apps on the App Store, Google Play, and F-Droid cover discovery, watching, publishing from a phone, and downloading videos to watch offline with no premium tier.[1]

• Open APIs and plugin system A documented REST API, player embed API, ActivityPub interface, and plugin and theme framework support third-party clients, custom players, and external authentication through LDAP, OpenID Connect, and SAML plugin examples.[1][2]

Who will love it

• Creators leaving centralized platforms: independent hosting with aligned values, real moderators, and portable subscriptions suits channels that want out of opaque algorithms without losing federation reach.[1][2]

• Groups needing their own governed video space: registration approval, local rules, and federation controls give a community its own culture while staying reachable from the wider network.[1][2]

• Technically comfortable self-hosters: documented Docker and Any-OS paths on familiar TypeScript, PostgreSQL, and Redis components suit operators who already run small services.[1][2]

Who should avoid it

• Creators who depend on mainstream recommendation reach and monetization: the federated network is split across instances and carries no ad-revenue engine, so anyone whose income depends on algorithmic discovery should stay centralized.[1][2]

• Non-technical viewers who want zero setup decisions: choosing an instance and trusting a volunteer-run operator add concepts a centralized signup avoids.[1]

• Teams unwilling to carry operations and moderation load: running an instance means handling reports, upgrades, backups, storage growth, and hosting bills, which only fits teams that accept that responsibility.[1][2]

Alternatives and compatibility