venueOS · demonstration

Sign in and look around

Lindsay Curling Club, running on venueOS. The platform is multi-tenant — one deployment, one database, and one tenant that cannot see another tenant’s data because the database refuses, not because the application remembers to filter. Only this tenant is listed here for now.

The office

app.venueos.studio — the address carries ?venue=<tenant> to say which tenant is being signed in to.

Tenant	Industry	Sign in	Password
Lindsay Curling Club	Curling	`admin@lindsaycurling.com`	the club’s own password

Sign in with the password you already use. The import carried every member’s existing credential across unchanged, so nothing had to be reset — which is also why no password is printed in that table.

The member’s side

The same address, signed in as somebody who holds no office role: the console drops the admin shell and shows the member portal instead.

Tenant	Sign in	Password
Lindsay Curling Club	`member@lindsaycurling.com`	that member’s own password

The tenant’s website

lindsaycurling.venueos.studio — the club’s public site as a member or a visitor sees it.

The companion app

One app for every industry the platform serves: it asks the server which tenant this is and builds its tabs, its vocabulary and its colour from the answer. Installers and instructions at downloads.venueos.studio.

Demo club data. This tenant holds demo club data — a copy of Lindsay’s own database, imported to demonstrate a migration rather than to run the club. The club’s live system is untouched and is still the original, and nothing done here reaches it.