Deployment Modes

HyperToken can run as a local Node process, a browser client, a relay-assisted peer network, or an application with a server-side authority. The state model remains the same: each Engine uses a Chronicle, and networked peers exchange Automerge sync data.

Mode	Use	Boundary
Local CLI	Develop or play an example without a network.	State is in one process unless persisted.
Browser client	Run bundled games such as Watershed.	Browser shims and hosting must support the generated bundle.
Relay-assisted peers	Connect clients through npm run relay or Compose.	The relay forwards traffic and is unauthenticated.
Authoritative service	Use the server classes in network/ when an application needs a trusted room/server process.	Authority and validation are application deployment choices.

Docker builds the image with docker build -t hypertoken:latest .; docker compose up relay runs the Compose relay service on port 3000. The example profile defines Blackjack server/client services separately. Production authentication, TLS termination, persistence policy, resource limits, and monitoring must be supplied by the deployment environment.