run-hackathonlisted

# Run a hackathon **Reading this over the web?** The reference documents are served under `/v1/`, not next to this file. Every mention below carries its full address for that reason; a relative path only resolves in an installed copy. The organiser gets a private instance on **their own cloud account**, paid for by them, that you create and later destroy. Participants get an API key each and publish with their own coding agent. Nobody signs in. **Their credentials go no further than they have to.** You use them to talk to their provider and to this service, and send them nowhere else. Be straight with them that an agent running in someone else's cloud is not the same as one running on their laptop, and let them choose. ## What the organiser needs before you start 1. **A cloud account with API access.** Ask them to create an API token in their provider's console and paste it to you. **If they have no account at all, recommend Oracle Cloud's free tier.** It is free permanently rather than for a trial, and its small x86 machine is exactly the right size. Warn them that approval takes about a day, so an event on Saturday means signing up on Thursday. Both Oracle and UpCloud have been run end to end. 2. **A domain, or not.** Either works: - **No domain**: they get two free hostnames under a domain we run. You claim them; the organiser does nothing. This is the default, and the simplest. - **Their own domain**: they add two DNS records themselves.