Hi everyone!
I’d like to introduce Bluvy Tube, a video discovery and publishing platform built on the AT Protocol ecosystem.
The idea behind Bluvy Tube is fairly simple: what if we could build a complete video platform without having to own the videos, control user identities, or keep creators’ data locked inside our own infrastructure?
That’s what we’re exploring with Bluvy Tube.
What is Bluvy Tube?
Bluvy Tube is designed to provide a complete video experience on top of the Bluesky network and AT Protocol.
You can:
-
Discover and watch videos published across the network.
-
Search for videos, creators and channels.
-
Follow creators and explore their content.
-
Publish videos directly from Bluvy Tube using your Bluesky account.
-
Create and manage your own channel.
-
Organize videos into playlists.
-
Share videos through external websites and applications.
The goal isn’t to build another centralized competitor to YouTube. It’s to explore what a video platform can become when it relies on an open protocol and interoperable data.
No video hosting infrastructure of our own
One of the most important architectural decisions behind Bluvy Tube is that we don’t host the original video files on our own servers.
When someone publishes a video through Tube, the file is sent to the video infrastructure used by Bluesky and the AT Protocol ecosystem.
Bluvy Tube focuses instead on indexing, search, discovery, recommendations, moderation and the viewing experience.
This also means that videos published through other compatible AT Protocol clients can appear on Bluvy Tube, provided they are public and meet our indexing criteria.
We want creators to retain control over their content rather than making them dependent on another proprietary storage platform.
Metadata belongs to creators
A video post alone doesn’t provide everything expected from a modern video platform: custom titles, descriptions, chapters, subtitles, translations and categories.
To address this, we developed an AT Protocol Lexicon:
tube.bluvy.video.metadata
It allows enriched video metadata to be synchronized directly to the creator’s PDS.
This means that information such as titles, descriptions, chapters and subtitles isn’t locked inside Bluvy Tube’s database. Other applications in the ecosystem can potentially read and reuse the same data.
We believe this is one of the most interesting opportunities offered by AT Protocol: applications can build different experiences around shared, portable data.
Features for viewers and creators
Bluvy Tube has evolved considerably over the past few months.
Some of the features currently available include:
For viewers
-
Video search with language, category and format filters.
-
A personalized discovery experience.
-
An optional immersive vertical feed.
-
A mini-player, keyboard shortcuts and sleep timer.
-
Translated titles, descriptions and subtitles.
-
Public and unlisted playlists.
-
Video clips that link back to the original video.
For creators
-
A customizable channel with a banner, description, links, trailer and featured video.
-
Video editing directly in the browser before publishing.
-
Custom thumbnails.
-
Translations, subtitles and chapters.
-
Detailed analytics, including traffic sources and CSV exports.
-
Comment moderation tools.
-
Scheduled publishing and reusable upload templates.
-
Live streaming integration with Stream.place.
Creators can also embed individual videos, playlists and entire channels on external websites. Each channel also provides an Atom feed, so people can follow creators through their preferred feed reader without needing a Bluvy Tube account.
Please note that video publishing currently follows Bluesky’s limits: 10 minutes and 300 MB per video.
Moderation is part of the architecture
Building a video discovery platform on an open network comes with its own challenges.
The AT Protocol firehose provides access to a huge amount of activity, but an open network doesn’t automatically determine what is appropriate for every application.
That’s why moderation and filtering are important parts of our indexing pipeline. We want Bluvy Tube to remain accessible to a broad audience while respecting content labels, moderation signals and the platform’s own rules.
We explored some of these challenges in more detail in our article about how we built Bluvy Tube.
A little about the technology
For those interested in the implementation, our current architecture looks roughly like this:
AT Protocol → Jetstream v2 → Node.js indexer → Internal API → Symfony 7 → MariaDB
The Node.js indexer processes events from Jetstream, identifies video publications and forwards relevant data to our Symfony backend.
The backend handles indexing, moderation, discovery, metadata management and the public API.
The frontend brings everything together into a video platform designed for everyday use.
What’s next?
Bluvy Tube is an ongoing project, and we’re still exploring what a video platform built around AT Protocol can offer.
We’re particularly interested in improving video discovery, creator tools and interoperability with other applications in the ecosystem.
I’d love to hear your thoughts:
-
What do you think a video platform built on AT Protocol should offer?
-
What features are currently missing from the video experience on Bluesky?
-
Would you like to see other applications reuse the video metadata stored on creators’ PDSs?
-
What would make you choose an AT Protocol-based video platform over a traditional centralized service?
Feedback, questions and technical discussions are very welcome!
Try Bluvy Tube: https://tube.bluvy.app
More about the project:
Thanks for reading!