LibreTime
Open-source radio broadcast and automation platform with scheduling, library management, live broadcasting and playout integration (Icecast, Liquidsoap).

LibreTime is an open-source radio broadcast and automation platform designed to run internet and terrestrial radio stations. It provides web-based scheduling, library management and automated playout, and is maintained by a community that forked and continued development from the AirTime project.
Key Features
- Web-based scheduling and show management with a calendar-driven interface
- Central media library supporting tracks, playlists, smart blocks and podcasts
- Automated playout with live broadcast support and DJ input endpoints
- Integrations with playout and streaming components such as Liquidsoap and Icecast
- Installer and Docker Compose deployment options for single-server or containerized setups
- Backend services using PostgreSQL and message queueing (RabbitMQ) for task coordination
- API and worker processes (Python services) alongside legacy PHP frontend components
- Support for recording, stream outputs, and multi-mount Icecast configuration
Use Cases
- Run an internet radio station with scheduled automation and live DJ shows
- Operate a community or campus FM/AM station with automated playout and logging
- Manage podcast scheduling, recording and on-demand archives from a single interface
Limitations and Considerations
- The codebase contains legacy PHP components alongside newer Python services; some deployments may require managing both runtimes and migration awareness
- Streaming depends on external components (Icecast, Liquidsoap) which must be configured and secured separately (SSL/reverse proxy recommended)
- Full production setups typically require configuring PostgreSQL, RabbitMQ and a reverse proxy; administrators should be comfortable with Linux service management or container orchestration
LibreTime is a mature, community-driven platform for broadcast automation and internet radio. It is suitable for stations that need scheduling, live input and integrated playout, but administrators should plan for the mixed legacy stack and external streaming components when deploying.
