InkPlay system overview

Before you start

• Read What is InkPlay if the team is new to the product.
• Identify the counter machine or staff workstation that will run the Controller.
• Identify the PCs and display screens that will join the branch.

Controller and Local Node

The Controller is the staff-facing app. The Local Node is the branch runtime behind it. Together they should be treated as the branch operating center.

• Use the Controller for staff actions such as sessions, PCs, players, reports, staff, setup, and devices.
• Keep the Local Node machine powered and reachable on the branch network.
• Train staff to treat Controller warnings as branch health signals.

Agent PCs

The Agent runs on player PCs. It shows the player-facing shell, reports device state, receives branch commands, and keeps the PC aligned with the active session.

• Install Agent on every player PC that should be managed by InkPlay.
• Use clear PC names that match physical station labels.
• Confirm Agent PCs appear online before relying on them for customer sessions.

Mobile, displays, and cloud services

Mobile and displays improve the customer experience. Cloud services support owner accounts, subscriptions, release visibility, backups, and platform-level features.

• Use mobile for player identity, QR login, requests, and activity.
• Use TV or console displays for customer-facing status and promotion surfaces.
• Use cloud-supported areas for owner visibility, subscriptions, updates, and long-term records.

Verify it worked

• Staff can explain which machine runs Controller and which machines run Agent.
• The owner understands that branch-critical work should continue locally when possible.
• Mobile and TV features are described as companion surfaces, not staff control replacements.

Troubleshooting

Related product pages

• Controller
• Mobile app
• TV display

See also

• What is InkPlay?
• Understand local-first branch operations
• Pair TV displays