Xibo CMS
Manage lobby announcements and event displays
Review status: Research backlog. Research candidate with incomplete checks; not a vetted recommendation.
Official Website · Source Code
oss-osi-approved planned guideOverview
Xibo CMS manages content shown by connected digital-signage players. A coworking team could schedule lobby welcome messages, event promotion and member announcements. The CMS license does not make every player free; player-platform terms and hardware support must be checked separately. Automatic room-booking synchronization is not verified here.
At a glance
| Field | Value |
|---|---|
| Categories | digital-signage |
| Deployment | self-hosted, managed-saas |
| License class | oss-osi-approved (AGPL-3.0-or-later) |
| Cost model | hardware-plus-software |
| Implementation difficulty | hard |
| Maintenance burden | high |
| Maturity | unknown |
| Freshness status | partially-verified (2026-10-23) |
| Completeness | partial |
| Confidence | medium |
| Directory tier | research-backlog |
Cost reality
Self-hosting requires CMS infrastructure, display hardware and administration. Windows/Linux open-source players have no software license cost, while Android/webOS/Tizen players require commercial licenses; paid major upgrades may apply. Cloud plans are paid.
Plans, provider terms and prices change; check official sources before making a budget or deployment decision.
Tasks reduced or augmented
Software does not replace community or ops staff. It may reduce or augment:
- Schedule approved announcements across configured lobby displays
- Reduce manual replacement of event slides on individual screens
Human oversight still needed
- Approve public content, image permissions and announcement expiry
- Check display hardware, network access and player-specific licensing
Manual process this can replace
Structured task-fit review has not been completed for this tool. Treat the free-text examples above as evaluation prompts, not replacement claims.
Data held
-
media files and announcements
-
administrator accounts
-
display inventory and schedules
-
player connection logs
-
Personal data: yes
-
Payment data: no / not primary
Collect only data needed for the pilot and confirm access, deletion and export behavior before operational adoption.
Risks
| Area | Notes |
|---|---|
| Vendor lock-in | Export, migration and restore behavior have not been tested; retain a practical manual fallback before depending on the tool. |
| Security | Separate signage players from sensitive member and office networks. Restrict CMS administration and uploaded content, apply CMS/player updates and avoid showing private booking or member data. |
| Compliance | Obtain permission before publishing member names, photographs or event attendee information on public screens. |
| Licensing | This record covers the AGPL CMS. Official open-source information covers Windows and Linux players. Android, LG webOS and Samsung Tizen players use separate commercial perpetual licenses; do not infer ChromeOS licensing or compatibility from the CMS license. |
| Operational | Test the exact hardware/player/CMS combination. Do not assume Linux, Windows, Android and TV-platform players have identical features or support; ChromeOS terms remain outside this review. |
Coworking fit
Roles: community-manager, marketing, technical-operator
Workflows: community-programming, event-lifecycle
Problems: improve-member-experience, multi-location-consistency
Smallest useful experiment
Use one spare supported display and player to show a staff-approved event slide and welcome message for a week, checking schedules, reboot recovery and the actual player license.
Links
- Homepage
- Repository
- Documentation
- Official website
- Source repository
- Official documentation
- Pricing and edition terms
Implementation guide
No implementation guide is published yet.
Verification
- Status:
partially-verified - Completeness:
partial - Confidence:
medium - Tier:
research-backlog - Last reviewed:
2026-10-23 - Sources:
Bounded official-source metadata review only. Features and edition boundaries were read; installation, task-fit evaluation, operator outcomes, integrations, security and recovery were not tested. Retained in Research Backlog; not a recommendation.