Enterprise deployment models for digital signage determine where your content management runs, how players connect, and how you pay. SpinetiX offers three models — full cloud (Arya), full on-premises (Elementi), and hybrid — all using the same hardware. The deployment model is a business decision, not a technical limitation. Your CFO's procurement preference and your CISO's security requirements determine the right choice.
When Deployment Model Matters
- Budget planning — Capex vs Opex affects which fiscal year absorbs the cost
- Data residency — some jurisdictions and organizations mandate data stays within the country or building
- IT capacity — on-premises requires internal server management; cloud offloads this
- Security classification — classified environments need air-gapped, on-premises deployments
Three Deployment Models
Model 1: Full Cloud (SpinetiX Arya)
SaaS deployment: content creation, scheduling, and fleet management in a browser. No server to manage. Automatic updates. ISO 27001 certified, GDPR compliant, BSI C5 attested. Players connect outbound on port 443. Best for: multi-site organizations that want fast deployment and no server management.
Model 2: Full On-Premises (SpinetiX Elementi)
Everything inside your network. Elementi runs as a Windows desktop application on your server. Players connect to the local Elementi instance. Zero data leaves the building. Air-gap capable — no internet connection needed anywhere. Best for: government, defense, banking, and environments with strict data residency requirements.
Model 3: Hybrid
Content creation and advanced editing in Elementi (on-premises). Remote fleet management and monitoring via Arya Cloud. Gives content teams powerful desktop tools while allowing IT to monitor and update players remotely. Best for: organizations with complex content needs and distributed screen locations.
Key Parameters
| Factor | Arya Cloud | Elementi On-Prem | Hybrid |
|---|---|---|---|
| Pricing | Opex (subscription) | Capex (perpetual) | Combined |
| Server management | SpinetiX handles | Your IT team | Split |
| Air-gap | No | Yes | Partial |
| Internet required | Yes (outbound 443) | No | For management only |
| Data residency | Cloud region (EU/US) | 100% your building | Content local, mgmt cloud |
| Auto-updates (CMS) | Yes | Manual | Split |
| Content editor | Browser-based | Desktop application | Desktop (more powerful) |
| Multi-site | Native, multi-timezone | VPN required | Cloud-managed remote sites |
Common Mistakes in Deployment Model Selection
- Choosing cloud because "everyone does." Cloud is excellent — unless your data must stay on-premises by law or policy. Ask your legal and compliance teams before signing a cloud contract.
- Choosing on-premises to avoid subscription costs. On-premises saves subscription fees but adds server management, backup, and update responsibility. Make sure your IT team is staffed for it.
- Not considering migration paths. Requirements change. A cloud-first startup may need on-premises after a government contract. SpinetiX hardware works with both models — no hardware replacement needed. Plan for flexibility.
- Ignoring the hybrid option. Many organizations benefit from on-premises content creation (Elementi's powerful editor) plus cloud fleet management (Arya's remote monitoring). Don't force an either/or decision. Platform overview →