Run the whole event on one platform, not five stitched together

Registration, teams, prepared workspaces, automated scoring, judging and a live leaderboard — built around coding events rather than bent out of generic event-management software. Participants write code in minute two, not after an hour of environment support.

Sign-ups that take thirty seconds

Each event gets a public landing page of its own with magic-link registration, so a participant is in with an email address and nothing else. Teams form on the platform, and each team gets a workspace the moment it exists.

A public landing page per event
Magic-link registration, anonymous-first
OAuth sign-in as an option, not a requirement
Team formation with a workspace per team
Several parallel tracks from one event
Sponsor branding and prize tiers on the page

Every team starts ready to code

Teams do not spend the first two hours installing things. Their Code Lab is pre-baked with the toolchain the event actually needs, identical for everyone, so the leaderboard measures ideas rather than who had the right laptop.

Code Labs pre-baked with the event toolchain
The same environment for every team
An editor and a terminal in the cloud, opened from any browser
Databases and services attached where the brief needs them
Nothing for a participant to install to get started — and no limit on what they install after that
A terminal on the container, so a team can pip- or npm-install whatever their idea needs
Mentors and staff can drop into a team workspace

Heavy compute, on somebody else’s budget if you like

Events that need GPUs or large models can dispatch that work to your own cloud credits or a sponsor’s, with the spend attributed to whoever agreed to pay it. Per-team caps mean the budget holds without anybody policing it in a spreadsheet.

Dispatch heavy compute to your own or a sponsor’s cloud credits
Sponsor-funded credit allocation with clean attribution
Per-team cost caps that stop rather than warn
Spend visible live, per team and per track
A one-off Day Pass for a single event, or a recurring tier

Automated and human scoring, in one ranking

Submissions are endpoints, and they are verified against hidden test payloads the moment they land — so a submission that does not run cannot win on presentation. Judges score rubrics alongside, and the leaderboard combines both.

Endpoint submissions verified against hidden tests
Judges score against rubrics you define
Automated and judge scores combined into one ranking
A live leaderboard throughout the event
Per-track ranking as well as overall
The scoring rules visible to participants up front

What is left when the weekend ends

The workspaces are real environments, not scratch space that evaporates on Sunday night. A winning project can keep running on a URL, and a participant who wants to carry on has something to carry on with.

Projects keep running on a real URL after the event
Participants keep the code they wrote
Results and scoring exportable for the write-up
Sponsors get attribution against what their credits ran
The event configuration is reusable for the next one

The three weeks before, in order

Set the event up — Landing page, tracks, prize tiers, sponsors, and the toolchain every team should start with.
They register and form teams — Magic link, a team, and a prepared workspace — no environment support desk required.
Submit, score, rank — Hidden tests verify what was built; judges score the rest; the leaderboard is live throughout.

Questions organisers ask

Do participants need accounts?

Only an email address. Registration is magic-link and anonymous-first; OAuth sign-in is available if you would rather have it.

Can a sponsor pay for the compute?

Yes. Compute can be dispatched to a sponsor’s cloud credits with the spend attributed to them, and per-team caps keep it inside what was agreed.

How is cheating or a broken submission handled?

Submissions are verified against hidden test payloads rather than taken on trust, so a project that does not actually run scores as one that does not actually run.

Do we have to buy a subscription for one weekend?

No. A one-off Day Pass covers a single event; the recurring tiers are for organisations that run several a year.

An event is a lot of software to assemble in a fortnight. This is the assembly, done once, so the work you do is the programme rather than the plumbing.

Tell us about your event

Dates, how many participants, what the brief needs installed, whether a sponsor is funding the compute. We will tell you what it takes to run it here, and say so plainly if your event is not a fit.