A private request portal for keeping Plex/media requests out of random chat threads.
Status: Live / private workflow helper
Live site: request.cyganlabs.com
Plex Requests is part of the CyganLabs media setup: a small, login-gated front door where approved users can ask for media without turning text messages, memory, and “I think someone mentioned this once” into a second database.
This is not a public signup page, a streaming service, or an invitation to request access. It is documentation for a private bit of infrastructure that solves a very real, very boring problem: requests need one sane place to land.
What it is
Plex Requests is a private request front end for the media workflow behind CyganLabs. The public endpoint currently sends visitors to a login page, which is the correct behavior. The useful part is not the login screen; it is the boundary around the workflow.
Approved users get a clearer way to submit requests. The person maintaining the stack gets something better than scattered messages, duplicate guessing, and archaeological digs through old conversations. Infrastructure should not require digging through old conversations.
Why it exists
Self-hosted media systems usually look complicated at the server layer, but the messy failure often happens at the human layer. The storage can be fine. Plex can be fine. The automation can be fine. Then the request process quietly becomes the weakest part of the workflow.
This project exists to make that edge cleaner. A request portal gives the workflow a single intake point, reduces repeat asks, and keeps “what should get added next?” from living entirely in someone’s inbox, phone, or someone’s memory.
What it does
- Provides a login-gated request portal for approved media users.
- Keeps request intake separate from random texts and chat threads.
- Makes the request workflow easier to review, prioritize, and maintain.
- Connects the request layer to the broader Plex/self-hosted media stack.
- Documents the project without exposing private users, private requests, or server details.
What it deliberately does not do
Plex Requests does not provide public media access. It does not accept open registration. It is not a support desk, a SaaS product, or an instant “give me movies” button. The live service is intentionally private.
That boundary matters. Some tools are better when they stay small, quiet, and attached to a specific workflow. Not every useful project needs to act like a startup landing page.
How it fits the stack
The request portal sits next to the Plex side of the homelab, not in place of it. Plex handles playback. The media stack handles storage, organization, bandwidth, and the usual “why is this transcoding?” detective work. Plex Requests handles the intake problem: what people are asking for and where those requests should live.
If you are here because Plex looks blurry, buffers, or behaves differently on every device because consumer tech behaves inconsistently, start with the Plex Help & Guides page instead. This project page is about the request workflow, not playback troubleshooting.
Current status
Plex Requests is live at request.cyganlabs.com as a private workflow helper. Public visitors should expect a login gate. That is not broken; that is the point.
There is no public repo linked here right now, and there is no screenshot because the public view is just a login gate. The interesting part is the operating pattern: keep the media request process structured without exposing private access or private request history.