ChangeLab Cloud
The control plane for live ChangeLab sessions. Upload a release, promote it when it is ready, and launch the sessions your facilitators run.
A session uses the variant and release it was created with.
One console per client. Releases arrive from Creator, a production slot decides what new sessions run, and every live session is one row with one state.
Releases
Everything a session needs travels as one file. Creator exports a .clpkg, Cloud stores it as a numbered version, and what lands is never edited afterwards.
Exports a sealed release package that Cloud takes in.
Organisations, projects, variants, release slots, members, domains, usage.
Shared infrastructure serving every live session at once.
Teams, answers and results, in a store of that session's own.
Sealed at upload
Games, media, plugin code and checksums are all in the package. Nothing is fetched from anywhere while an event is running.
Two slots per project
Preview is where a release is tried. Production is what the next session launches from. Promoting moves one to the other.
Uploads keep their version
Promoting production to v13 leaves v12 in the list, still pinned to every session that ran on it.
Sessions
A session is one run of a release with one group. It takes the release and the variant it was created with, and it keeps them.
Pinned at creation
A session locks to the release it launched with. A promotion afterwards cannot reach it, so an urgent fix means launching a replacement rather than editing what is live.
Promotion looks forward
Moving the production slot decides what the next session gets. Nothing scheduled, running or finished moves with it, which is what makes promoting safe on the morning of an event.
Separate stores
Each session writes to a store of its own. There is no shared pool that has to be filtered correctly, so one session cannot read another's even by accident.
Sessions share the machines and nothing else. The servers are one deployment; the store is not.
Entry
Two project settings decide how somebody gets into a session: the entry mode it uses, and the address it runs on.
Entry mode
- Open
- Anyone holding the code. Cloud asks for nothing and stores nothing identifying about them.
- Accounts
- A work email on a domain you allow, plus the shared passcode.
- Enterprise SSO
- The client's own identity provider decides who gets in.
Session address
- Shared
- play.changelab.dev, and a six-character code short enough to read out to a room.
- Delegated
- A domain the client points at us. One wildcard mints an address per session, and the certificates are handled.
A participant meets one screen, and the entry mode decides what happens after it.
Portal
Each organisation has a page of its own: their mark, their colour, their address, and no vendor branding anywhere on it. Somebody opens the link, sees what is running, and joins.
- Nothing is public by default. Three separate decisions put a cohort on it: an address on the organisation, an experience cleared to be named, and that cohort published. The console’s Portal page states the outcome of all three in one place.
- It never replaces the code. The portal saves a participant from typing anything. The join code and the session link keep working whether or not a cohort is listed on it.