Studio247 is a multi-tenant platform for media streaming, transcoding, automation, and broadcasting. Organisations, communities, creators, and media networks use it to manage assets, run automated playout, publish live streams, and collaborate—each within an isolated studio workspace with its own configuration, members, and optional custom domains.

This page is an orientation brief. It is not a legal document; see Terms of Use and Privacy Policy for those commitments.

1. Who it is for

Studio247 suits teams that need shared media libraries, scheduled programming, and reliable streaming infrastructure without building everything in-house. A single account can belong to multiple studios; you switch between studios to work in the right tenant context.

2. Accounts and access

You sign in with a verified account to use the operational console. After registration, onboarding helps you get oriented. Studio membership is invitation-based or granted by administrators; roles control who can manage media, configure streams, edit schedules, or view content. Optional two-factor authentication and API tokens are available where enabled for your account.

3. Studios and feature flags

Each studio is a logically isolated tenant: its own files, playlists, streaming settings, and optional product modules. Capabilities such as playlists, programming shows, a knowledge base, forum, organisations, talent applications, streaming, and API access are turned on per studio when it is provisioned. That keeps smaller deployments simple while allowing full broadcast stacks where needed.

4. Media library and transcoding

Upload and organise audio and video in the studio media library. Uploaded assets can be queued for processing by distributed FFmpeg workers: format conversion, loudness normalisation, thumbnails, waveforms, and other variants needed for playback and delivery. Processed outputs are registered back against the source file so playlists and streams use the right renditions.

5. Playlists and collaboration

Playlists group related media with access control, collateral, and optional workflows such as review or pack downloads when those features are enabled. Playlists tie into programming and curated file access so teams can separate productions, clients, or seasons without mixing libraries.

6. Programs, structures, and AutoDJ

Define programs with rule-based blocks for automated rotation. Timeslots on the schedule tell AutoDJ which show or program to play at a given time, so unattended playout stays on programme. Compiled playlists are generated from program rules and linked show or studio file pools. You can preview upcoming playout before it goes to air.

7. Streaming and broadcasting

Where streaming is enabled, Liquidsoap orchestrates live and automated output: harbour inputs, playlist sources, crossfades, metadata, and failover behaviour. Studio operators configure tenant- and endpoint-level Liquidsoap settings in the console. Streams can be exposed through an embeddable web player when that module is active. Traditional broadcast targets (for example Icecast-family mounts) depend on your deployment and endpoint setup.

8. Programming shows

Shows (in the broadcast sense) link playlists to on-air identity: artwork, curated file access, structure-based AutoDJ playlists, and related scheduling. They are distinct from the studio tenant itself—think of them as programmes or series within a studio’s output.

9. Community and talent

Optional studio modules include a knowledge base for help articles, a forum for discussion, and organisations for org-level membership inside a studio. Talent applications provide a public apply flow on a studio’s www domain so DJs, producers, or contributors can submit interest; staff review applications in the console.

10. Discord integration

Link your account to Discord for identity across channels. The Studio247 Discord bot can relay activity and support account linking via a one-time code. Community coordination often continues on Discord alongside the web console—see the invite on the landing page when you want to join the community on Discord.

11. Custom domains and white-label

Studios can attach verified custom domains for console, player, stream, and public www experiences, subject to DNS verification and platform configuration. That supports white-label presentation for networks and brands operating their own front door while running on shared infrastructure.

12. Administration

Platform staff use administrative tools for tenant provisioning, moderation, data correction, and system health. Day-to-day operators work in studio-scoped areas; ordinary listeners and visitors interact with public players, apply pages, and published content as configured.

13. Next steps

Ready to get started: create an account, sign in if you already have credentials, or use contact for questions about access, studios, or integrations.

Login - Register - Platform - Privacy Policy - Terms of Use - Contact

Copyright Company ©