Cloud vs on-premises is the foundational architecture decision for digital signage deployments. Cloud (SaaS) offers ease of management, multi-site reach, and lower initial cost. On-premises offers data sovereignty, no recurring fees, and full network isolation. SpinetiX uniquely supports both models with the same content format: Arya (cloud) and Elementi (on-premises). Hybrid deployments mix both — cloud for remote sites, on-premises for secure facilities.
Architecture Comparison
Cloud Architecture (Arya)
Content and management live in SpinetiX's cloud. Players connect over the internet, pull content from Arya, and report status back. Managers access the web dashboard from any browser. No local servers, no IT infrastructure beyond internet connectivity and the players themselves.
- Content path: Designer → Arya Cloud → Player (pull over HTTPS)
- Management: Web browser, any location
- Infrastructure: Internet connection only
- Updates: Automatic platform updates by SpinetiX
On-Premises Architecture (Elementi)
Content is designed and published from a Windows workstation running Elementi. Content pushes directly to players over the local network. No internet required. All data stays within the physical premises. IT team controls every component.
- Content path: Designer → Elementi → Player (push over HTTP/LAN)
- Management: Elementi desktop application
- Infrastructure: LAN, designer workstation
- Updates: Manual software updates by IT team
Hybrid Architecture
Combine both models in a single organization. Corporate HQ and secure facilities use Elementi (on-premises). Remote offices, retail locations, and partner sites use Arya (cloud). Content format is identical — design once in Elementi, publish to either platform.
Decision Matrix
| Factor | Cloud (Arya) | On-Premises (Elementi) |
|---|---|---|
| Initial cost | Low (subscription) | Higher (license + infra) |
| Recurring cost | Per-player/month | None (optional support) |
| IT overhead | Minimal | Server/network management |
| Data sovereignty | Swiss-hosted cloud | Fully on-premises |
| Multi-site | Native (internet) | Requires VPN/WAN |
| Security | TLS + cloud security | Full network isolation |
| Scalability | Unlimited | LAN bandwidth limited |
| Internet required | Yes | No |
| Government/Military | Rarely acceptable | Required |
| Retail chains | Ideal | Challenging at scale |
Key Parameters
| Parameter | Cloud | On-Premises |
|---|---|---|
| Content format | Same | Same |
| Player hardware | Same SpinetiX players | Same SpinetiX players |
| Offline playback | Yes (local cache) | Yes (local cache) |
| Fleet monitoring | Arya dashboard | Player web interface |
| Migration path | Can migrate to on-prem | Can migrate to cloud |
Common Mistakes
- Choosing cloud for classified environments. Government, military, and critical infrastructure often prohibit cloud connectivity. Don't propose Arya for environments that require air-gapped operation — use Elementi on the isolated network.
- Choosing on-premises for 200 remote retail stores. Managing VPN tunnels and Elementi push to 200 distributed sites is operationally painful. Use Arya — each store's players pull content over their existing internet connection.
- Ignoring the hybrid option. Many organizations have both secure and distributed environments. Don't force one model everywhere — use on-premises for HQ and Arya for field offices.
- Not planning for migration. Requirements change. A startup begins with cloud but acquires a government contract requiring on-premises. SpinetiX's format compatibility makes migration smooth — but plan for it in your initial architecture.