30 days freeThen $65/month per locationNo credit card required Start free trial
ARC owner guides Architecture guide for owners

Cloud vs installed escape room software

The important distinction is not whether staff use a browser. It is where the game engine and hardware control run, and what remains available when an outside service cannot be reached.

Written and reviewed by the ARC product teamLast reviewed August 2026
Decision brief

The meaningful distinction

  • Trace the complete path from a player action to the physical response.
  • Separate room control from account, update, backup, and messaging services.
  • Installed software removes a cloud dependency from room control but makes local power, network, computer, and backup planning important.
  • Remote access and online services can complement an installed system without moving the game engine to the cloud.
On this page
  1. 01What cloud and installed actually mean
  2. 02Follow the live-game operating path
  3. 03Compare the operating tradeoffs
  4. 04Reliability is more than internet availability
  5. 05Control over updates creates responsibility
  6. 06Installed software can still use online services
  7. 07Questions to ask every software provider
01

What cloud and installed actually mean

In a cloud-run system, an outside service makes important live-game decisions or holds live state. With installed software, the computer at the escape room business handles games and devices.

Both approaches can use browser screens. Ask where each command is handled, not what the interface looks like.

02

Follow the live-game operating path

A useful architecture explanation follows one real event from the room and back again.

Player action

A sensor or prop reports a change

The message begins on the room network through a controller, gateway, PLC, or protocol.

Evaluation

The system checks room state and logic

Objectives, variables, timers, and automation conditions determine the next action.

Response

The system controls the experience

Locks, lights, audio, displays, and staff screens receive the resulting command or update.

Record

The operation keeps useful history

Activity, device state, and session results help staff explain and recover the room.

03

Compare the operating tradeoffs

Questions behind the architecture labels
Decision areaCloud-run systemInstalled system
Internet outageOnline features may stop.Live rooms continue locally; online add-ons may stop.
Main computer failureHosted game control may remain available from another device.ARC stops until the computer is repaired or replaced and a backup is restored.
UpdatesProvider may deploy centrally.Owner chooses a maintenance window and manages the update.
Remote accessOften built into the hosted service.Requires a secure path to the on-site system or an optional online service.
Data recoveryProvider controls hosted recovery.Owner needs current local or off-site backups and a tested restore plan.
04

Reliability is more than internet availability

Installed software avoids a live dependency on a remote provider, but it still depends on the ARC computer, local network, gateways, controllers, and power. Good architecture makes those dependencies visible.

Do not confuse offline operation with automatic high availability. ARC does not currently provide automatic failover to a second computer.

Owner checklist
  • Use a UPS for the ARC computer and critical network equipment
  • Keep current backups and know how to restore them
  • Document addresses, credentials, gateways, and license reconnection
  • Test what staff sees when internet or a controller is disconnected
  • Maintain a realistic replacement-computer plan
05

Control over updates creates responsibility

Choosing when to update protects a live schedule from surprise changes. It also means the owner should read release notes, create a backup, use a maintenance window, and test a room afterward.

A predictable update process is more valuable than simply claiming that updates are frequent or automatic.

06

Installed software can still use online services

Keep time-sensitive room control local and use online services where central coordination provides a clear benefit.

Keep local

Time-sensitive operation

Game logic, device commands, timers, audio, displays, and staff control should not wait on a public internet round trip.

Use online deliberately

Business convenience

Account management, software delivery, off-site backups, remote access, and notifications can use online services without owning the live path.

07

Questions to ask every software provider

Owner checklist
  • Where does the game engine run?
  • What exactly stops when the internet is unavailable?
  • What happens when the main computer fails?
  • Who chooses when production software updates?
  • Can I export and restore complete room configuration and media?
  • How is remote access secured, and what remains onsite?
  • Which recovery steps have customers actually tested?
Put it to work

Test the architecture, not just the interface

Run ARC on your network, connect real hardware, disconnect the internet, and practice recovery during the full 30-day trial.