DEV.co
Open-Source CMS · xibosignage

xibo

Xibo is an open-source digital signage platform featuring a web-based content management system and display players for Windows, Linux, and commercial options for Android, LG webOS, and Samsung Tizen. It has been actively developed since 2009 and is distributed under AGPL-3.0, making it free to use but with specific copyleft obligations.

Source: GitHub — github.com/xibosignage/xibo
719
GitHub stars
180
Forks
Unknown
Primary language
AGPL-3.0
License (OSI-approved)

Key facts

Objective fields from the source. Values we can't verify are shown as “Unknown” rather than guessed.

FieldValue
Repositoryxibosignage/xibo
Ownerxibosignage
Primary languageUnknown
LicenseAGPL-3.0 — OSI-approved
Stars719
Forks180
Open issues122
Latest releaseUnknown
Last updated2026-05-27
Sourcehttps://github.com/xibosignage/xibo

What xibo is

Xibo is a distributed digital signage system comprising a PHP-based CMS, native players for multiple platforms (Windows/.NET, Linux), and a message relay component (XMR) for real-time player communication. The architecture supports multi-screen networks with centralized content scheduling and management via a web interface.

Quickstart

Get the xibo source

Clone the repository and explore it locally.

terminalbash
git clone https://github.com/xibosignage/xibo.gitcd xibo# follow the project's README for install & configuration

Need it deployed, integrated, or customized instead? DEV.co ships production installs.

Best use cases

Multi-location retail or enterprise digital signage networks

Deploy synchronized content across hundreds of screens in stores, offices, or venues with centralized scheduling and content management via the web CMS.

Cost-sensitive organizations needing full control

Organizations with internal infrastructure and development capacity can self-host the entire stack without per-screen licensing fees, reducing long-term operational costs.

Custom integrations and branded player experiences

Development teams can fork and customize the open-source players and CMS to integrate with proprietary systems, APIs, or brand-specific requirements.

Implementation considerations

  • Multi-repository architecture: CMS, players, Docker containers, and optional components (XMR, Interactive Control) are split across separate repositories; integration effort scales with deployment scope.
  • Database and infrastructure requirements: Self-hosting requires PHP environment, database (not specified), and web server; Docker containers available but require container orchestration knowledge.
  • Player deployment and licensing: Windows and Linux players are open source; commercial players (Android, LG webOS, Samsung Tizen) have separate licensing; clarify player strategy before procurement.
  • AGPL-3.0 copyleft obligations: Any modifications to the source code must be made available under AGPL-3.0 or disclosed; legal review recommended for derivative works.
  • Community vs. vendor support: Community forums available at community.xibo.org.uk; critical production deployments may warrant Xibo Ltd's commercial support contract.

When to avoid it — and what to weigh

  • Need immediate commercial support and SLA guarantees — While Xibo Ltd offers commercial support, the open-source project itself has no guaranteed SLA or dedicated vendor support unless you purchase their hosting/support packages.
  • Require proprietary software with no source code inspection — AGPL-3.0 requires that any modifications must be contributed back or the modified code disclosed; organizations unable to comply with copyleft obligations should avoid.
  • Seeking a plug-and-play SaaS offering with zero administration — Self-hosting Xibo requires database, web server, and player management; Xibo Ltd's hosted CMS is available but involves vendor dependency.
  • Need native iOS player support — No iOS player mentioned in the repository list; only Windows, Linux, and commercial Android/LG/Samsung players are available.

License & commercial use

Xibo is licensed under AGPL-3.0 (GNU Affero General Public License v3.0), a copyleft open-source license. This means the software is free to use, modify, and distribute, but any modifications or derivative works must be made available under the same license (or disclosed if run as a service). The license is OSI-approved.

Commercial use of unmodified Xibo is permitted under AGPL-3.0. However, if you modify the source code or integrate it into a proprietary service, you must disclose those modifications under AGPL-3.0 or the same license. Xibo Ltd offers separate commercial hosting, support, and commercial player licenses (Android, LG, Samsung) for additional revenue; verify licensing terms for derivative works and deployment models with legal counsel.

DEV.co evaluation signals

Editorial assessment — not user reviews. Directional, with an explicit confidence level.

SignalAssessment
MaintenanceActive
DocumentationAdequate
License clarityClear
Deployment complexityModerate
DEV.co fitGood
Assessment confidenceHigh
Security considerations

AGPL-3.0 source code is publicly auditable, reducing hidden vulnerabilities. However, self-hosted deployments require secure configuration of the PHP CMS, database, message relay (XMR), and player communication channels. No formal security audit, responsible disclosure policy, or CVE history provided in data; conduct threat modeling for internet-facing deployments and apply standard PHP security hardening. Commercial support may include security patches and advisory.

Alternatives to consider

Brightsign Network

Proprietary, cloud-managed digital signage platform with built-in media players; lower operational overhead but vendor lock-in and per-screen licensing.

Signagelive

SaaS-first digital signage with web CMS and multi-platform player support; avoids self-hosting complexity but relies on vendor infrastructure and subscription model.

OpenSignage (if available) or homegrown custom solution

Alternative open-source options (limited) or in-house development for highly specialized requirements; full control but higher development and maintenance costs.

Software development agency

Build on xibo with DEV.co software developers

Xibo offers a free, auditable, open-source alternative for organizations ready to self-host or engage commercial support. Assess AGPL-3.0 licensing implications and infrastructure requirements before committing.

Talk to DEV.co

Related open-source tools

Surfaced by semantic similarity across the DEV.co open-source index.

Related on DEV.co

Explore the category and the services that help you build with it.

xibo FAQ

Can I use Xibo commercially without paying Xibo Ltd?
Yes, the unmodified open-source CMS and Windows/Linux players are free under AGPL-3.0. However, modifications trigger copyleft obligations, and commercial players (Android, LG, Samsung) are sold separately. Verify derivative work licensing with legal counsel.
What are the hardware requirements for players?
Windows player requires Windows OS/.NET runtime; Linux player requires Linux. Android, LG webOS, and Samsung Tizen players are commercial offerings. Exact minimum specs not provided in data; consult official documentation.
Is Xibo suitable for a single-screen deployment?
Yes; README explicitly mentions 'single screen' use cases. However, the overhead of self-hosting the CMS may be disproportionate; evaluate commercial hosting or alternatives for small deployments.
How does real-time content update work?
Xibo Message Relay (XMR) component enables real-time player communication; it is a separate open-source repository. Deployment depends on your network architecture and required latency.

Work with a software development agency

From first prototype to production, DEV.co delivers software development services around tools like xibo. Our software development agency staffs experienced software developers and web developers for custom software development, web development, integrations, and ongoing support across open-source cms and beyond.

Evaluate Xibo for Your Digital Signage Needs

Xibo offers a free, auditable, open-source alternative for organizations ready to self-host or engage commercial support. Assess AGPL-3.0 licensing implications and infrastructure requirements before committing.