Airbridge

Airbridge creates virtual DLNA/UPnP renderers that forward audio to AirPlay speakers and Chromecast devices, allowing media servers such as Music Assistant to…

  • Media Applications
  • Media Servers
  • Tools & Utilities
Airbridge creates virtual DLNA/UPnP renderers that forward audio to AirPlay speakers and Chromecast devices, allowing media servers such as Music Assistant to stream to AirPlay-only or Chromecast-only hardware. It receives DLNA audio over HTTP and forwards it to AirPlay zones via the libRAOP library or to Chromecast devices via CASTV2. Designed for setups where specific AirPlay implementations have compatibility issues, it works around them by presenting standard DLNA renderers. Includes automatic multicast DNS (mDNS) device discovery, a web admin interface, and volume control.

Platform availability

Available on 1 of 10 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

51/100 Fair

Maintained
44last commit 288 days ago
Popular
2212 GitHub stars
Easy to install
351 install platform, install notes, Docker image
Light to run
85512 MB minimum RAM
Security check
94no serious findings, 1 minor, CI, tests

Availability: platform listings confirmed today, links checked 24 days ago

GitHub stars
12
Open issues
5
Last commit
2026-02-06
Latest release
v0.2.2
License
MIT
Activity
stale

Checked 8 days ago - source: GitHub (kenyonj/airbridge)

Resources & Compatibility

Minimum requirements: 512 MB RAM, 50 MB disk.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Set your app name and web token Put your Airbridge app name and web token into the web SDK (the Airbridge code you add to your app) before starting it. If these are missing or wrong, the SDK can't connect to your project and your user events won't be tracked. source
  • Add Expo plugin credentials For Expo apps, add the airbridge-expo-sdk plugin to your app.json (Expo's main app settings file) with your appName and appToken. Without those values, the SDK has no Airbridge account to report to. source
  • Use the current referrer method Use fetchGoogleInstallReferrerDetails to read Google Play install referrer information. The older getGoogleInstallReferrerDetails is deprecated, so relying on it can lead to outdated or broken attribution details. source
  • Network Mode Use host network mode for mDNS device discovery and SSDP announcements. source

Fetched 47 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Why does Airbridge need Docker host networking?

It requires host network mode for mDNS device discovery and SSDP announcements.

Which port does Airbridge use for the DLNA server and web admin?

The HTTP port defaults to 8200. The web admin is available at the /admin path.

What should I mount and back up for a self-hosted Airbridge?

Docker should mount a data volume at /data. The SQLite database location can also be set with the -db flag and defaults to ./airbridge.db.

Can Airbridge receive Chromecast streams from client apps?

No, Chromecast receiver support for casting from apps to Airbridge is blocked by Google device authentication requirements.

What extra component is required when building Airbridge from source?

You must place a prebuilt cliraop binary for your platform in the bin directory. Then run make build.

Answers sourced from github.com

Community

Collected 48 days ago - public community threads