Platform hub - 2026
Chebyrnet unifies music, video, and voice into a coherent platform family - thoughtfully designed for creators, teams, and audiences who refuse to compromise on quality.
Platforms
Music
In developmentA dedicated music service taking shape around a catalogue, personal library, listening history, playlists, search, and a personalised discovery wave.
Video
PlannedA planned, purpose-built home for video inside the Chebyrnet family. Its product surface and delivery stack will evolve independently from the other services.
Voice
PlannedA planned communication service for the Chebyrnet ecosystem. Voice has its own product direction while remaining connected through one identity and one hub.
| Feature | Music | Video | Voice |
|---|---|---|---|
| Repository state | In development | Foundation reserved | Foundation reserved |
| Primary medium | Audio | Video | Voice |
| Identity | Chebyrnet ID | Chebyrnet ID | Chebyrnet ID |
| Public address | music.chebyrnet.ru | video.chebyrnet.ru | voice.chebyrnet.ru |
| Delivery model | Independent service | Independent service | Independent service |
| Product status reflects the current repository structure; public availability follows each service deployment. | |||
About Chebyrnet
Chebyrnet is structured as a constellation of purpose-built products rather than a single monolith. The services share a common entrance while keeping their product responsibilities explicit.
Music stays focused on sound, Video on moving image, and Voice on conversation. They can share identity and platform foundations without losing their own purpose.
Chebyrnet ID is the common entry point. Each product can rely on one authentication service instead of rebuilding account flows.
Music, Video, and Voice keep their own product scope, interface, infrastructure, and release cycle.
This hub keeps every public destination discoverable without coupling the page to a backend or service registry.
A service can grow around the needs of its medium while shared platform concerns remain shared.
Service metadata lives in one typed configuration, so another destination can be introduced without rebuilding the page structure.
Navigation, themes, and interaction run entirely in the browser. The page remains statically renderable and simple to deploy.
Roadmap
The hub distinguishes what exists today, what is being built, and which product directions are still planned.
The shared authentication and account surface for the Chebyrnet ecosystem.
The current product build covers the catalogue, library, listening history, discovery, and the music delivery stack.
A dedicated video product direction with its own service boundary and a reserved public destination.
A dedicated communication product direction connected to the same identity and platform hub.
Available
In development
Planned
Planned next
Philosophy
Each platform can own its infrastructure and release cycle. Shared identity connects the ecosystem without turning every product into one monolith.
A music product should feel native to listening; a video product to watching; a voice product to conversation. The medium shapes the tool.
A growing service family should still be easy to understand. The hub provides one durable map to every public destination.
A service can evolve, deploy, and scale on its own schedule without forcing unrelated products to move with it.
Shared concerns stay shared, product concerns stay local, and the connection between them remains visible in the architecture.
New destinations can join the catalogue through typed content and reusable components rather than another one-off homepage rewrite.
"One ecosystem does not have to mean one monolith. Build a clear entrance, then let every product become itself."
- Chebyrnet platform principle
FAQ
A short guide to the hub, shared identity, and the current service catalogue.
Get started
Create or manage your account through Chebyrnet ID. Product links become active here as their public routes are released.