Infrastructure

Venue hub & sync

Optional venue hub: a Pi on club Wi‑Fi serves venue.yourdomain with local DNS. Staff keep POS/door/kitchen online offline. When internet returns, bidirectional sync mirrors sales, members, catalog, tables and more with the cloud.

What you can do

Concrete capabilities from the live Hubumo build — not a generic feature list.

One hostname: venue.* on LAN → Pi, public DNS → cloud
Offline-first: night continues without internet
Bidirectional sync: hub ↔ cloud when WAN is up
Full business DB mirror — not just sales
Catch-up snapshot after time away from hub Wi‑Fi
Let’s Encrypt certs synced from cloud to Pi

In depth

Why a hub

Clubs lose sales when the public internet blips. The hub keeps the same apps on the LAN. Cloud remains the backup and remote access path.

Identity

Every business write mirrors both ways — products, members, tickets, tables, kitchen, cash days — so hub and cloud stay identical.

How it works — step by step

1
Cloud first
Install the club VPS on your domain.
2
Pi hub
Run the Pi installer with venue.* + sync secret.
3
DNS
Venue Wi‑Fi DHCP DNS → Pi; public A → cloud.
4
Certs
Sync Let’s Encrypt from cloud onto the Pi.

Screens & flows

UI previews of the real surfaces — till, door, manager, displays — so you can see options and steps before opening the app.

Try Venue hub & sync in the venue

Explore more modules