Skip to content
Starfield Labs

Help desk

Submission guidelines

How to fill in and submit your hackathon project on Starfield Labs. Each event can set its own submission form. If the event page says something different from this page, the event page wins.

Contents

Where you submit

Submit from your team page before the deadline. Any member of your team can submit. Your project opens from your event hub, and your changes save as you go.

What to submit

A complete submission usually includes:

  • Project title: clear and descriptive, up to 80 characters.
  • Short description: a one-paragraph summary, up to 280 characters.
  • Long description: the problem, your solution and how it works, at least 100 words.
  • Tracks and technologies: the event tracks you’re entering and every tool, model and API you used.
  • Video: a demo or pitch of up to 5 minutes, uploaded as MP4 or WebM, up to 300 MB. A link can’t replace the upload.
  • Slides: a PDF deck, up to 50 MB, when the event’s submission form asks for one.
  • Code: a public GitHub repository. If you have several repos, link them from the main README.
  • Live demo: a working URL and the platform it runs on (for example Vercel, Replit or Streamlit).
  • Cover image: optional, 16:9.

The steps

The project screen has six steps: Team, Project, Presentation, Video, Links, and Review. You can open any step at any time, and a step with nothing for your event to ask is left out.

  • Team shows your team's name and members.
  • Project holds the title and the description, the tracks your project enters when the event has more than one, and its technologies and cover image when the event's form asks for them.
  • Presentation holds your slides, when the event's form asks for them.
  • Video holds your video upload, then a YouTube link when the form shows one.
  • Links holds your code’s repository and your live demo’s URL, when the event's form asks for them.
  • Review lists anything required that is still missing, then Submit.

Submit before the deadline

Submissions close at the time on the event page. A countdown on each event page shows exactly how much time you have left. After you submit, your team can keep editing, or return the project to draft, until submissions close. If a technical problem stops you from submitting, contact the organizers before the deadline. Only they can extend it for your team.

Incomplete submissions may be scored lower or excluded from judging.

How projects are judged

Unless the event page says otherwise, judges score each project from 1 to 5 on four criteria:

  • Application of technology: how well you used AI and the event’s tools.
  • Originality: how new and creative your idea is.
  • Business value: whether it solves a real problem for real users.
  • Presentation: how clearly your video, slides and demo explain the project.

Criteria set by an event

Events and sponsor tracks can use their own criteria, weights or scales. These are always listed on the event page. The hackathon rules have the rest.

Tips

  • Start with the problem your project solves, then show how it solves it.
  • Show your project working in your video, not only slides about it.
  • Check that your repository and demo open for someone who isn't signed in to your accounts, since judges can review only what they can open.
  • Submit early, and keep improving your project until submissions close.