ARYA is SpinetiX's cloud content management system for digital signage. It provides browser-based remote management of SpinetiX players — content publishing, campaign scheduling, fleet monitoring, and team collaboration. Players connect to Arya via HTTPS with certificate-based authentication. This guide covers the enrollment process from player to cloud.
When to Use This Guide
- Multi-site deployments where players are in different buildings, cities, or countries
- Managed service providers operating signage fleets for multiple clients
- Teams that need multiple people managing content from different locations
- Remote-first organizations that can't walk to every player on the local network
How to Connect a Player to ARYA
Step 1: Create an Arya Account
Sign up at spinetix.com/arya. Choose a subscription plan based on player count. Arya provides a web dashboard where you'll manage all enrolled players.
Step 2: Access the Player's Web Interface
Connect to your SpinetiX player at http://<player-IP> on the same network.
Navigate to the Configuration → Cloud Management section. This is where enrollment happens.
Step 3: Enter the Enrollment Code
Arya generates a unique enrollment code for your account. Enter this code in the player's web interface. The player establishes a secure HTTPS connection to Arya's cloud servers, exchanging TLS certificates for mutual authentication.
Step 4: Verify Connection
In the Arya dashboard, the player appears with a green status indicator. You can now see its current content, firmware version, network status, and screenshot preview. The player checks in with Arya at regular intervals, maintaining a persistent management channel.
Step 5: Assign Content and Groups
Tag your player with labels (location, department, floor, client). Upload content through Arya's browser interface and assign it to individual players or groups. Content pushes automatically — no manual publishing needed.
Key Parameters
| Parameter | Value | Why It Matters |
|---|---|---|
| Protocol | HTTPS with mutual TLS | Encrypted, authenticated communication |
| Authentication | Certificate-based | No passwords exposed on the network |
| Access Control | Role-based (admin, editor, viewer) | Multi-user team collaboration |
| Fleet Grouping | Tags, locations, departments | Manage thousands of players efficiently |
| Offline Behavior | Local content cache | Screens keep playing when cloud is unreachable |
| Platform | Browser-based (any device) | No software installation required |
Common Mistakes
- Blocking outbound HTTPS on the firewall. The player needs outbound port 443 to reach Arya cloud. Many enterprise firewalls block all outbound traffic by default — add a rule for player-to-Arya communication.
- Not verifying enrollment completion. Always confirm the player shows green status in the Arya dashboard. A pending enrollment means the player is still running its previous local content.
- Ignoring proxy requirements. If your network routes through a web proxy, configure the proxy settings on the player before enrollment. Without this, the player can't reach Arya's cloud endpoints.
- Using Arya for air-gapped networks. Arya requires internet. For isolated networks (military, critical infrastructure), use Elementi with local network publishing instead.