vyla-entertainment/documentation
2
0
Fork 0
mirror of https://gitlab.com/vyla-entertainment/documentation.git synced 2026-11-15 06:57:21 -05:00
Code Issues Packages Projects Releases Wiki Activity

updated story

Browse Source
This commit is contained in:
alwaysmesmerizingyou
2026-11-14 15:30:28 -08:00
parent 167ddf47fa
commit b9b596d14f
1 changed files with 7 additions and 12 deletions
Download Patch File Download Diff File Expand all files Collapse all files

19
misc/project/story.md
View File

@@ -1,20 +1,15 @@
# Our story
<p class="page-description">Why Vyla exists, what we care about, and how you can help.</p>
<p class="page-description">The story behind Vyla, from a small web project to a self-hosted ecosystem.</p>
Vyla started as a small web project with a simple goal: a cleaner, more private way to discover and watch movies and shows without relying on a single company or centralized service. It has since grown into apps for desktop, Android and Android TV, plus the tools that power them.
Vyla started from a web project that initially intended to create a clean environment where one could stream movies and TV shows free from all the unnecessary elements. Originally, it was developed mainly as a frontend which embedded other players. With time, I got involved in the process of developing the infrastructure.
Vyla is software, not a streaming service. We do not host or provide any media.
Another core component of Vyla is Vyla API, which dealt with searching streams from various providers, verifying their availability, and playing them. Later on, it evolved into being able to cope with many kinds of streams and deal with possible issues related to their quality and reliability.
## What we care about
With constant changing and breakage of providers, I had to develop Vyla SDK. The purpose of it was to isolate the source implementations from the rest of Vyla so that they could be independently managed and used in other projects. I made each source into provider modules which had the same interface. Vyla SDK remains updated as sources change.
- **Control.** You decide how much of Vyla you use and where it runs.
- **Privacy.** Vyla stays local and self-hostable, with no unnecessary centralized dependencies.
- **Community.** Vyla is built in the open by the people who use it.
Among the main challenges associated with the development of Vyla was hosting. Initially, I did self-hosting of the frontend, API, player, Nginx, PM2, and other infrastructure on a VPS. Managing them was a struggle with constant downtime, provider issues, Cloudflare problems, and, lastly, DMCA complaints.
## Where to go next
However, after receiving a DMCA strike and experiencing problems due to frequent reports in Cloudflare, I figured out that it wouldn't be efficient to self-host the streaming infrastructure. Therefore, the choice was made to focus more on the SDK and the applications rather than using a remote backend.
- Pick an app: [Vyla Home](/products/home), [Vyla Go](/products/go) or [Vyla TV](/products/tv).
- Build with Vyla: start with the [SDK quickstart](/sdk/vyla-sdk/quickstart) or the [Stream API](/stream-api/overview).
- Help fix sources: read the [contributing guide](/sdk/vyla-sdk/contributing).
- See who made this possible on the [credits page](/misc/project/credit).
Thanks for reading ❤️