InkPlayWiki

What is InkPlay?

Published: 2026-07-12 - Updated: 2026-07-13 - 8 min read - InkPlay Team

A plain explanation of InkPlay as a local-first operating platform for gaming venues, staff, player PCs, mobile identity, and displays.

What does InkPlay actually do for a gaming venue?

Owners and staff can explain the product in operational terms: branch control, player PC control, sessions, billing, players, displays, and reporting.

Before you start

  • Know the basic layout of the venue: counter, player PCs, console areas, and staff roles.
  • Decide whether the venue will start with PC sessions, console sessions, or both.
  • Keep a simple list of the daily work staff currently handle manually.

Platform purpose

InkPlay gives a gaming venue one operating layer for the work that happens before, during, and after play. It connects the staff Controller, Agent PCs, player accounts, displays, billing, and branch reports.

  • Use the Controller as the staff workspace for sessions, devices, players, reports, and branch setup.
  • Use the Agent on each player PC so sessions and player-facing actions are controlled by the branch.
  • Use mobile, displays, and promotions when the venue is ready to improve return visits and customer communication.

What it replaces

InkPlay is meant to reduce scattered tools. A venue should not need separate spreadsheets for players, timers for sessions, manual notes for debts, and disconnected screens for promotions.

  • Replace manual session tracking with controlled start, extend, transfer, and stop actions.
  • Replace disconnected player notes with branch-linked player accounts and history.
  • Replace one-off display screens with branch-owned TV and Agent surfaces.

What InkPlay should not be

InkPlay should not make the branch dependent on a distant cloud service for every live customer action. Live floor work should stay close to the venue and staff.

  • Do not treat the mobile app as a staff control panel.
  • Do not expect cloud visibility to replace the Controller during live operation.
  • Do not bypass staff approval for actions that affect PCs, sessions, money, or customer-facing screens.

Verify it worked

  • Staff can describe the Controller, Agent, mobile app, and TV display as different parts of one venue system.
  • The owner can list which current manual tasks InkPlay is expected to replace first.
  • The first rollout scope is tied to real venue work, not every possible feature at once.

Troubleshooting

Staff think InkPlay is only a timer.

Start with the Controller, Agent PC, player account, and reporting manuals so the operating model is clear.

The team expects the phone app to run the branch.

Use the mobile manuals to explain that mobile is a companion identity surface, while the Controller remains the staff workspace.

See also