How it works

From a calendar invite to three clouds — and back to nothing.

Book a workshop or a challenge, and its attendee accounts and cloud environments build and clean themselves up on schedule.

Organizer

An organizer picks a date, a size and the clouds, and nothing is billed until it starts.

Automatic · at start

Two hours before the start, the accounts, Harness org and cloud environments build themselves.

Attendees

Each attendee signs in to their own environment and works through the labs.

Automatic · at end

When the timer runs out, every account, project and org is torn down.

Under the hood

A run's lifecycle, build-up to teardown

scheduled
On the calendar, with nothing built until about two hours before the start.
provisioning
A Google Workspace org-unit is created, then one attendee account per seat.
Harness org
every event
A Harness organization is created with one project per attendee.
applying
Terraform builds every requested cloud, one environment each in challenge mode.
Terraform, one state per cloud
Google CloudGKE
Ephemeral project
Billing linked, APIs enabled
GKE cluster
Attendees granted Editor
AWSEKS
Member account
An IAM user each
EKS cluster
PowerUser access
AzureAKS
Resource group
An Entra user each
AKS cluster
Contributor access
A workshop can also request no cloud and share a long-lived sandbox project instead.
ready
environments live
Credentials are ready to hand out and the room is open.
in session
Attendees work in their own environments, and the deadline can be extended a day at a time.
destroying
Everything comes down in reverse: the clouds, then Harness, then the accounts.
destroyed
Nothing is left running or billing.

Any step can end in failed, where the run stops and stays flagged on the calendar to be retried or reaped.

Pick a date, a size and the clouds, and the orchestrator takes it from there.