Digital Signage Content Management System (CMS) Explained

A digital signage CMS (content management system) is the software that controls what plays on every screen from one place. It runs the whole content lifecycle — design templates, connect live data sources, schedule playlists, assign content to individual screens or groups, set user roles, and monitor the fleet. Without one, someone walks to each screen with a USB stick; with one, a single operator runs 10,000 screens from a browser. SpinetiX offers it as a cloud CMS (Arya) and as on-premises authoring (Elementi).

Five jobs, and the rest is packaging. It has to build or import layouts (templates with zones for video, images and data), bind live data sources to those zones, schedule playlists per screen or group, control who can publish what, and report which players are online. Judge any product on those five using your own screens, not a feature matrix. Two limits apply to every platform in this category. The software does not create content, so someone still owns the feeds and the refresh cycle. And a wrong choice costs most when the vendor changes hands, which is why the consolidation of the CMS market belongs on the buying checklist next to features. Whether the platform enforces approval before content goes live is covered in the approval question on this page.

Nothing visible, for a while. On SpinetiX the schedule and the content sit on the player, so screens keep following the last published plan when the CMS or the network drops. What stops is everything that needs the link: you cannot publish a change, push an urgent message or see fleet status until the connection returns, and a zone fed by a live data source keeps its last cached data, which the player holds for up to 24 hours, then shows whatever fallback you built for it. A short outage does not blank the estate, but it freezes your ability to react. If a message must reach the screens during a cloud outage, plan an on-LAN trigger for it before you need it.

Owns the schedule, not the artwork. The role decides what each screen group plays and when, keeps data feeds and templates current, publishes through the CMS and checks that players are online. In a small estate that is one person with full access; in a larger one it is several people, each limited to their own screens, which is what roles and permissions are for. The limit is the one in the approval question: roles record who may publish, they do not make a second person sign off, so a brand-sensitive or regulated estate adds an approval step outside the console or a layer with a real approval queue, such as 123CMS. The CMS does not produce the creative either, so budget for whoever does.

Any display driven by a dedicated media player or a player-grade SoC. A cloud CMS such as SpinetiX Arya does not talk to a plain monitor directly — it manages a player (a SpinetiX HMP400 or iBX-series unit) connected behind the screen, and that player renders the content and reports status back to the cloud. So a commercial display plus a SpinetiX player is cloud-CMS-ready; a consumer TV on its own is not. That is why the CMS is hardware-independent: the same Arya account runs one lobby screen or a 10,000-screen estate.

Yes. The CMS treats an LED wall as one large canvas. A SpinetiX player outputs the full-resolution image to the wall's LED controller (for example a Novastar unit), and the cloud CMS schedules and updates that canvas exactly like any other screen — a single HMP400 can drive a wall well beyond 1080p. You design the layout once, the player re-reads the data, and the CMS pushes changes over the network with no on-site PC in the loop.

Honestly — most signage platforms, SpinetiX included, do not ship a built-in, enforced multi-step approval gate. Arya gives you user roles and permissions so you control who can publish, but it will not, on its own, hold a playlist until a manager signs off. Teams that need strict approve-before-live add it one of two ways: an external approval step that feeds an already-approved data source the screen reads, or a personalised layer (such as Media La Vista's 123CMS) that wraps the fleet with a real approval queue. If a vendor claims full editorial workflow out of the box, ask to see it demonstrated on their own console.

You build playlists and give them a time to play. Scheduling covers date and time ranges, day-parting (breakfast menu until 11:00, lunch after), recurring weekly patterns, per-screen or per-group targeting, priority overrides for urgent messages, and time-zone-aware playback so a campaign fires at the correct local time in every city. On SpinetiX the schedule runs on the player itself, so screens keep following the plan even if the network drops.

Neither is universally better. Cloud (SpinetiX Arya) is faster to deploy, auto-updated, and needs no server management. On-premises (SpinetiX Elementi) keeps all data inside your network — required for government, defence, and organisations with strict data-residency rules. SpinetiX runs both on the same hardware, so the choice is about data governance, not a hardware lock-in.

With most vendors you start over, because layouts are stored in a proprietary binary format. SpinetiX content is built from standard web technologies (HTML5, SVG, JavaScript), which is far more portable, and your data sources stay external and independent of the CMS — so the feeds that drive the screens are never trapped inside one vendor's tool.