Organizer Guide: Events

Create and manage GPU events for your students or participants using the Hub.

Creating an event

Log in to the Hub at razorbridge.eu/hub and navigate to Events > Create Event.

Fill in the event details:

• Name — a descriptive title (e.g., “ML Workshop — Spring 2026”)
• Start / End dates — when blades should be provisioned and torn down
• GPU type — select from the dropdown (pricing shown per hour)
• Max participants — the participant cap for this event
• Environment — choose a preset (PyTorch, TensorFlow, JAX) or specify a custom Docker image

Sharing the join code

Every event gets a unique join code (e.g., CUDA-2026). Students use this code to register via the CLI:

rb event join CUDA-2026

Share the code however works best for your class:

• Put it on the first slide of your presentation
• Post it in your course's Moodle/Canvas/Teams channel
• Write it on the whiteboard

Pre-registering students

If you prefer not to share a join code, you can pre-register students:

1. Go to your event detail page in the Hub.
2. Click “Import Participants” and upload a CSV file.
3. The CSV should have one column: email (one student email per row).

Pre-registered students see the event automatically when they log in — no join code needed.

# participants.csv
email
[email protected]
[email protected]
[email protected]

Monitoring participants

The event detail page shows a live participant table with:

• Blade status — provisioning, running, idle, stopped
• Last SSH login — when the student last connected
• Idle duration — time since last SSH activity

Use this to identify students who might need help:

• A student whose blade has been idle for 30+ minutes might be stuck
• A student who never connected might have trouble with the CLI setup

Extending an event

If your session runs over, you can extend the event while it's running:

1. Go to the event detail page.
2. Click “Extend”.
3. Choose an extension: 30 minutes, 1 hour, or 2 hours.

The cost delta is charged to your credits immediately. Students receive an updated teardown time — they don't need to do anything.

Cost estimation

The cost estimate when creating an event is calculated as:

cost = hourly_rate × duration_hours × participants

For example: L40S GPU (€1,44/hr) × 3 hours × 40 students = €172,80.

Actual cost may differ if:

• You extend the event (adds to cost)
• Fewer students than the cap actually join (reduces cost — you only pay for provisioned blades)