RoundOneRoundOne/Docs
Sign inTry the demo
Getting started
  • Introduction
  • Quickstart
  • Key concepts
Hackathon sponsors
  • Sponsors
  • Nebius Token Factory
  • Nebius Sandboxes
  • Tavily
  • NVIDIA Nemotron
  • Devpost
Workspace
  • Your hackathons
  • Create a hackathon
  • Sign in and settings
Setup
  • Schema
  • Criteria
  • Judges
  • Phases
  • Distribution
  • Judge portal
  • Branding
  • General
Judging
  • Projects
  • Project detail
  • Progress
  • Failed inbox
  • Rewards
  • Chat
Results
  • Winners
  • Winner emails
Shared links
  • Judge link
  • Submission form
  • Winners page
Reference
  • Intake API
  • Configuration
  • Deployment
Hackathon sponsors

Sponsors

The Nebius x NVIDIA Global AI Hackathon on Devpost, and what each sponsor's tech does in RoundOne.

RoundOne was built for the Nebius x NVIDIA Global AI Hackathon on Devpost. The hackathon asks every project to run on Nebius Token Factory or Nebius AI Cloud and to use at least one NVIDIA open model. RoundOne uses the sponsors' tools for the work an agent is good at: building repos, reading code, visiting demos and checking claims. Judges keep the calls about the ideas.

Sponsor tech in RoundOne#

SponsorWhat RoundOne usesWhere it does the work
Nebius Token FactoryOne OpenAI-compatible API for every model call, with schema-enforced JSON and embeddingsAgent reviews, double checks, project summaries, Chat, chat search
Nebius SandboxesVM-isolated sandboxes that clone, install, build and test each repoThe Sandbox run mechanism and the agent's runCommand tool
NVIDIA NemotronNemotron 3.5 Lightning, Nemotron 3 Super 120B and Nemotron 3 Ultra 550BThe agent's three model tiers and Chat's Fast and Smart modes
TavilyExtract, crawl and searchThe Web scraper mechanism, the agent's web tools, Chat's index and web lookups
DevpostThe hackathon's home: rules, submissions, judges and prizesProjects come in from a Devpost export through the Intake API

How they fit together#

  1. Devpost collects the submissions. An organizer exports them and sends them to RoundOne through the Intake API.
  2. When judging starts, the agent reviews each project one criterion at a time. Each criterion's mechanisms gather the evidence:
    • Sandbox run clones the repo into a Nebius Sandbox, installs, builds and runs the tests.
    • Web scraper reads the live demo with Tavily.
    • Code scraper searches the repo for the packages and calls the organizer listed, such as the Token Factory API.
  3. An NVIDIA Nemotron model, served through Token Factory, reads the evidence, investigates with tools on the larger tiers, and returns its verdict as strict JSON.
  4. When the agent is unsure, a bigger Nemotron model judges the same evidence again.
  5. Judges score the ideas. In Chat, organizers ask questions across every project, answered by Nemotron over a search index built with Token Factory embeddings and Tavily.

Keys to set#

Each sponsor's tools need one key in your environment. Configuration lists every variable.

VariableSponsorWithout it
NEBIUSNebius Token FactoryNo agent reviews, chat or sandboxes.
NEBIUS_PROJECT_IDNebius SandboxesSandbox runs can't start. The rest of the agent works.
TAVILYTavilyWeb steps are skipped, and the agent notes "TAVILY isn't set".

The NVIDIA models need no key of their own: Token Factory serves them with the NEBIUS key.

Sponsor pages#

Nebius Token FactoryEvery model call, schema-enforced verdicts and chat embeddings.Nebius SandboxesClone, build and test every repo in an isolated VM.NVIDIA NemotronThe models behind the agent's tiers and Chat.TavilyLive demos, web searches and linked pages.DevpostThe hackathon, its rules, and getting its projects into RoundOne.
PreviousKey conceptsNextNebius Token Factory