Independent radio. Entirely yours.
Your music. Your schedule. Your sound.
Freo is a self-hosted internet radio platform. Build your library, shape the week, take the decks, and discover what connects with your listeners.
Made for music people. Built to broadcast. Start with the setup guide →
A station with your signature
The best stations have a point of view. Freo gives you the space to find yours—and the tools to bring it to life.
One connected workspace takes you from a carefully chosen library to a full week of programming, a hands-on DJ session, and a player your listeners can make part of their day.
01 / Music & playlists
From the album you know by heart to tomorrow's discovery. Bring your music together, give it some order, and put it to work.
Browse artists, albums and songs. Import MP3 files or whole folders. Shape your library with artwork, colored tags, categories, notes and song flags.
Build a Straight playlist or let Random work through a fresh cycle. Add songs, albums, artists or categories; drag to reorder, then bring your playlist into the schedule.
A more consistent sound. Background analysis measures BPM, loudness and true peak. Non-destructive playback gain helps match song levels while keeping your originals intact.
Inside the music workspace ↗02 / Your station, in time
A carefully planned week. A repeatable daily format. One great playlist on repeat. Choose the way you want to program.
Place programs on dates and times. Repeat daily, weekly or monthly. Adjust a single occurrence or a whole series.
Compose a full 24-hour format. Assign weekdays, selected dates, or a pattern that rolls from day to day.
Choose a Show, playlist, artist, album, category or song. Let it repeat continuously.
REUSABLE SHOWS
Build a Show from 15 minutes to 24 hours. Drag in sources, resize sections, combine artists and insert a song for a particular moment. Saved revisions keep future edits deliberate.
A DAILY FORMAT
Save a 24-hour Block and give every part of the day its own character. A configured default playlist fills the gaps; Events add IDs, announcements and other timed moments.
Scroll across to explore
| Mode | Your starting point | Made for |
|---|---|---|
| Calendar | Day, Week, Month or Agenda | Shows and music tied to dates, times and recurring series |
| Blocks | A reusable 24-hour composition | Weekday formats, selected dates and rolling daily patterns |
| Simple | One Show or music source | Continuous playback with an explicit change when you're ready |
Shows are reusable compositions, not a fourth mode. Events work across all three. Scheduling follows station-local time; normal program boundaries let the current song finish.
03 / Take the air
Let the schedule run, take control of two decks, or bring your voice into the mix. The booth keeps your station's sound close at hand.
Load a song without interrupting Auto. Choose a fade from 0 to 10 seconds and Take Air. Pause, resume, repeat once or fade out. Return to your scheduled sound when your session is done.
Keep an eye on the active program, current song and next selection. Monitor your stream and skip through a worker-controlled fade.
Test a browser microphone or USB mixer input off air. Set your gain, go live, then fade back to the interrupted feed.
YOUR STATION'S SIGNATURE
Fire an ID, sweeper or promo. Play over the music with ducking, or take over and resume the interrupted audio afterward. The same cart wall stays with you in Auto, DJ and Live Mic.
04 / Your sound, in numbers
Go beyond a listener counter. Explore your audience, music, feedback, resources and broadcast reliability, across one channel or the whole installation.
Follow current, average and peak connections, listener-hours and approximate geography. Keep stream listeners separate from player-page visitors.
See confirmed song and artist plays, likes, dislikes and approval. Compare periods and take the data with you as CSV.
Track stream transfer, storage, mount availability, low audio levels and broadcast outcomes. Missing observations stay visible as gaps.
Analytics uses a local geographic database and locally served maps. Raw listener addresses and user agents are not stored in analytics.
Understand the numbers ↗05 / On the other side of the speakers
Your station deserves a listening experience with as much personality as its music.
Give it a cover, artwork and your own colors. Share announcements and socials. Publish the schedule, make room for sponsors, and hear back through song votes and private comments.
The details make the station
From your first import to the commercial log. Explore the tools that make Freo a complete station workspace.
Scroll across to explore
| Capability | What Freo includes | In practice |
|---|---|---|
| A connected catalog | Artist, album and song views; metadata, artwork, notes and review flags. | Search, filter and organize in one workspace. |
| Import & analysis | MP3 file, batch and folder uploads; progress, duplicate checks, BPM, waveform, loudness and peak analysis. | Background processing keeps preparation out of the broadcast path. |
| Categories & tags | Multiple categories, colored tags, bulk assignment and membership Undo. | Each channel keeps its own organization. |
| Playlists | Straight order or non-repeating Random cycles; bulk additions, reordering and scheduling. | Category, artist and album additions copy the current songs. |
| Preview & level matching | Private audition, seeking, original/normalized listening and station loudness targets. | Playback gain preserves original audio files. |
Scroll across to explore
| Capability | What Freo includes | In practice |
|---|---|---|
| Calendar, Blocks & Simple | Three scheduling modes, reusable Shows, recurring placements and saved revisions. | A configured, playable default playlist fills gaps. |
| Rotations & clocks | Explicit category rotations, repeating clock slots, previews and track/artist separation. | Advanced rotation rules are distinct from visual-scheduler shuffle cycles. |
| Timed events | Songs, IDs, announcements and sequences; one-time, weekly and hourly series. | Hard, soft and non-interrupting policies; timing windows and outcomes. |
| Event sequences & stopsets | Ordered music/imaging snapshots, item failure policies and execution history. | Separate from the scheduler’s 24-hour Blocks. |
| Traffic planning | Advertisers, campaigns, creatives, dayparts, daily logs, makegoods and CSV as-run reports. | Advanced commercial planning; billing and invoicing are not included. |
Scroll across to explore
| Capability | What Freo includes | In practice |
|---|---|---|
| Two-deck control | Load, Take Air, pause, resume, repeat once, clear and fade out. | Choose a 0–10 second transition; prepare while Auto plays. |
| Monitoring | Persistent Master Monitor, listening volume, private preview and program/monitor meters. | Program levels come from the worker; monitor levels measure browser audio. |
| Carts & imaging | Eight hot carts, four station-ID slots, imaging groups, sweepers, promos and jingles. | Play over with ducking, or take over and resume. One cart at a time. |
| Live Mic | Off-air input testing, software gain, mute, fades and disconnect fallback. | Optional WebRTC gateway; browser mic or OS-recognized stereo USB input. |
Scroll across to explore
| Capability | What Freo includes | In practice |
|---|---|---|
| Audience & geography | Current, average and peak connections, listener-hours, approximate map and period comparisons. | Connections are sampled; they do not identify unique people. |
| Music & engagement | Confirmed song/artist plays, likes, dislikes, approval and moderated private comments. | Queue entries and private previews do not count as plays. |
| Resources & reliability | Stream transfer, storage, mount availability, low program levels and broadcast outcomes. | Coverage gaps remain visible. Stream bytes exclude website/proxy overhead. |
| Branded listening | Covers, artwork, palettes, announcements, socials, sponsor slots and mobile controls. | Day/Night and reduced-motion preferences. |
| Public schedules | Published Day, Week and Month listings, automatic schedules and custom overrides. | Listener-facing listings are separate from engine control. |
| Reports you can use | Overall or per-channel statistics, timezone-aware dates, tables and CSV export. | Six views: Overview, Audience, Music, Engagement, Resources, Reliability. |
Scroll across to explore
| Capability | What Freo includes | In practice |
|---|---|---|
| Multiple channels | Separate station engines and streams; shared artists, albums and songs without duplicated audio. | Configured station limits apply. Current admins manage all stations. |
| Identity & domains | Station logos, location, descriptions, stable URL aliases and verified custom domains. | Contacts stay private unless published; operators configure DNS and HTTPS. |
| History & accountability | Confirmed playback starts, admin audit records, health views and durable control intent. | Controls recheck the intended song before changing playback. |
| Copyright review | Permanent public Track IDs, optional ISRC, reporting form and private case management. | Review tools do not establish ownership or music licensing. |
| Installation integration | Permanent station UUIDs, optional registration, aggregate reports, directory metadata and cached entitlements. | The Central reporting service runs separately from station playout. |
Explore the traffic workflow, custom domains and copyright review in detail. Freo is actively developing; see the setup notes for current requirements and release limits.
Your next great hour starts here
Your radio runs on your server. Freo Live is where you register your site, connect your installation and manage its license.
Bring your server and your music. The setup guide walks through the requirements.
Read the setup guide ↗Create your owner account and station profile, verify your email, then connect Freo using your activation code.
Register your site ↗Start with the included allowance. Manage your installation and explore additional channel licensing when you need it.
How licensing works →Your station. Your server.
Freo connects a browser workspace to dedicated broadcast services. Your library, programming and confirmed history live in PostgreSQL; each managed station gets its own Liquidsoap process.
Dedicated ingest and statistics workers support the station. Optional WebRTC microphone audio joins the engine through a separate gateway. The web app records validated commands; the automation worker controls the private playout connection.
Scroll across to explore
| Layer | Technology | What it does |
|---|---|---|
| Workspace | Python · Flask · Gunicorn | Browser management, APIs and authenticated control requests |
| Station data | PostgreSQL | Music, schedules, command intent and confirmed playback history |
| Audio & delivery | Liquidsoap · Icecast · Nginx | Station playback, transitions and public listener streams |
| Media preparation | FFmpeg · ffprobe | Validated imports, metadata and background audio analysis |
| Live microphone | WebRTC / Opus · aiortc | Optional browser microphone and USB audio input gateway |
| Operations | Ubuntu 24.04 · systemd | Separate services, workers, timers and health checks |
Make room for your next idea
Bring the music and the point of view. Explore the setup guide, see how Freo fits your server, and make your next great hour.
Freo is an actively developing project for self-hosted internet radio. The production target is Ubuntu 24.04. A separate fresh-VM installation acceptance test remains outstanding; start with the requirements and current installation notes.
An Ubuntu 24.04 server, your music, and the services described in the setup guide. Plan for storage and stream bandwidth. Production browser access needs HTTPS. Station broadcast start/stop remains a server CLI operation.
Yes. Freo manages separate station engines and stream mounts. Share artists, albums or songs across channels without copying the audio. Station limits depend on installation configuration and any configured entitlements; current admin accounts manage all stations.
Yes, with the optional Live Mic gateway installed and configured. Use a browser microphone or an OS-recognized stereo USB mixer input. HTTPS and working WebRTC connectivity are required; some networks need TURN.
The application, database and audio services run on your server. Local statistics are collected separately from optional Central integration, which supports registration, aggregate reporting, directory metadata and cached entitlements. See the integration guide for details.
The source and documentation are available on GitHub. Consult the repository for current source-code reuse terms. For installation entitlements and additional channel capacity, visit Freo Live licensing. These are separate from the rights needed to broadcast music.
