InkPlayLocal APIs and persistence serve Controller and Agent operations inside the venue.
Operations and support
Reliability evidence
Internet loss and branch failure are not the same event.
InkPlay keeps branch operations close to the venue through Controller, Local Node, and Agent. When internet is unavailable but the branch LAN and Local Node remain healthy, local work can continue while cloud visibility may become stale. If LAN or Local Node fails, centralized branch control is affected.
Cloud and cross-branch visibility can become stale while local operation remains available.
Local diagnostics, Agent snapshots, and guarded backup/restore paths exist.
Branch-local operation
Critical venue workflows are served through the local branch path.
InkPlay includes a branch Local Node, local persistence, staff authentication, device/session APIs, command queues, reports, diagnostics, and backup services. Controller and Agent use that local path instead of requiring every branch action to wait for a cloud round trip.
- Sessions, branch staff actions, device communication, and local records are handled through branch services.
- Agent PCs connect to the Local Node over the venue LAN.
- Local diagnostics expose health information before support changes branch setup.
Outage boundary
WAN loss can preserve local work while cloud-dependent visibility degrades.
When the LAN and Local Node remain healthy, local Controller and Agent workflows can remain available. Cloud dashboards, remote owner visibility, cross-branch data, downloads, and internet identity flows can be delayed or unavailable.
- Keep serving only stations that still show healthy local state.
- Expect cloud or remote views to become stale until connectivity returns.
- Avoid deleting devices or rebuilding pricing because of a temporary disconnect.
Hard failure boundary
A failed LAN or Local Node affects centralized branch control.
Local-first still has a dependency: the branch network and Local Node host must remain available for normal branch-wide coordination.
- If many PCs fail together, check power, router, LAN, and Local Node health before troubleshooting every Agent separately.
- If only one PC fails, isolate that Agent, device approval, or Windows/network state.
- After recovery, run a short test session before returning affected PCs to customer use.
Recovery controls
Use health, diagnostics, backups, and guarded restore paths.
InkPlay contains Local Node health endpoints, Agent diagnostic snapshots, setup backup export/restore, and cloud backup services. Restore is intentionally controlled because it can replace branch state.
- Check Local Node health and affected device diagnostics before reinstalling.
- Create and verify backups before major setup, imports, updates, or risky recovery work.
- Cloud backup requires an activated and configured branch; cloud restore is blocked while active sessions exist.
Helpful guides
Continue with the operator manuals.
Common questions
Reliability questions, answered clearly.
Can InkPlay continue operating when the internet is down?
Branch-local Controller and Agent workflows can remain available when the venue LAN and Local Node are healthy. Cloud visibility and internet-dependent features may become stale or unavailable.
What happens if the branch LAN or Local Node is down?
Normal centralized branch control is affected. Staff should check power, network, the Local Node host, and health endpoints before changing devices or reinstalling software.
Are all InkPlay branches automatically backed up?
No blanket guarantee is published. Backup tools exist, but cloud backup requires branch activation, configuration, and successful status checks. Owners should verify the latest backup rather than assume it exists.
Need help with your venue?
Continue the conversation in the support center.
Choose the branch, describe what is affected, and keep every reply together until the issue is resolved.