Free workspaces for every team at your event. Every team builds in the same environment, and every submission arrives with a summary a judge can read in a minute.
Paste your event link. Teams start free workspaces. Submissions arrive already summarised.
Set it up once and everyone works in the same place, from any laptop.
Three people, three agents, one repo. Each person explains the project to their own agent, the work drifts apart, and the last two hours go to merging instead of the demo. A longer event does not fix it. It just moves the wall.
One person creates the drive. Everyone else joins from a browser and starts building. No environment to reproduce, no hour lost to installs.
Everyone sees the same session, the same files and the same terminal. Prompts queue with a name on each one, so nobody explains the project twice.
There is one copy of the work. When two people push at the same thing, the overlap layer settles it on the spot instead of at 4pm.
The app runs in the drive with a browser on it. Judges open the link. Nobody plugs in a laptop.
Ada wires the redirect, Ben catches the empty-cart bug, Chi is next in the queue. One session, three people, no handoff.
src/cart/Checkout.tsx +64 −3One link. No account. Fine on a phone.
two-cities.coshell.appnpx convex deploy at 15:42, from Ben’s terminalFirst prompt, first commit, last commit, against your kickoff. Earlier history on the repo is shown rather than hidden.
Your checks, resolved against the drive. A link that answers. A repo that is public. npx convex deploy at 15:42.
Prompts per person and the sessions they were in. A record, not a score.
Their own summary, written at submission. Design, video and pitch get counted here.
Every prompt carries a name and a time.
Two minutes at the deadline, mostly filled in already.
Name, one line, deployed link. The repo comes from the drive.
Worked out from what the team actually used, and theirs to change.
A line each, in their own words.
All of them by default. Private ones stay private.
Video link, deck, anything else you asked for.
Frozen at the deadline. What a judge opens at seven is what existed at six.
Timestamps, prompts, commits and commands from the drive, counted. A model then writes the summary and works out which tracks the team used, from the prompts and commit messages.
Paste your Luma or Partiful link. We read the page and the description, and ask only for what is missing.
In your Discord, on the kickoff slide. A room on one wifi network all get in.
One person creates the drive, pastes the link in the group chat, and everyone is working before the first talk ends.
No account, nothing to install. They score on the page or in whatever you already use.
An optional prize you can add to your event: a name, a one-page rubric, the judge brief and a submission question. Teams opt in. Judges score from the same summary they already have.
Yes. Every team on your event code gets a drive for the event, with no card. It is also free to self-host.
Yes. Nothing in the summary needs more than one person, and no check marks a solo entry down.
That is most teams. Prompt counts are a record, not a score, and every team writes its own line on who did what. The video, the deck and the pitch get counted there.
No. One person connects GitHub when the team sets up, and everyone pushes from the drive after that. Teammates do not need GitHub accounts, and commits still carry the name of whoever wrote them.
Nobody, until you submit. The summary is built from prompts, commits and commands rather than your source, and you choose which sessions go in. The judge link is revocable, and a self-hosted drive keeps all of it on your own machine.
Each submission seals at the deadline and opens as a summary: when the work started against kickoff, whether the repo had earlier history, which requirements resolved, and who worked where. The sessions sit underneath it.
Yes, and prompts queue with the name of whoever sent them. Teams that prefer separate sessions on one drive can do that instead.
No. A drive opens in a browser. Teams who want a terminal can attach from the CLI.
It is in your repository, where it was all along. Keeping the drive is a separate decision.
Yes. A self-hosted drive connects out rather than listening, so venue wifi needs no inbound ports.
Tell us about your event and we will set you up with a code, a page and the prize kit.