Configuration

A RoundOne instance reads its settings from two places: branding.config.js at the repo root, and environment variables. Nothing on this page is editable in the app. The Settings page shows the branding and the Supabase variables read-only.

branding.config.js#

branding.config.js sets the name and look of the whole instance: the header, browser tab titles, the sign-in screen, emails, and the "Judged with" footer on submission forms and winners pages. Each hackathon still sets its own color, logo and banner on top of it in Setup › Branding.

The file as it ships:

const branding = {
  // Product name shown in the header, page titles and the "Judged with" footer.
  name: "RoundOne",

  // Short text badge (1–3 chars) used as the avatar mark when no logo is set.
  badge: "R1",

  // Optional square logo from /public, e.g. "/logo.svg". Replaces the badge.
  logo: null,

  // A preset — "purple", "blue", "sky", "teal", "green", "amber", "orange",
  // "rose", "pink", "zinc" — or any custom hex like "#ff5a1f".
  color: "purple",
};

export default branding;

Text on the accent color switches between white and near-black, whichever has more contrast.

Color presets#

Any other value must be a hex color. A value that is neither a preset nor a hex stops the app with an error that lists the presets.

Changes apply after you restart the dev server or redeploy.

Environment variables#

Set these in .env.local for local development, or in your host's environment variables in production. Never commit real values.

Supabase#

Without SUPABASE_SECRET_KEY, the Intake API returns 503 and no emails go out. The rest of the app works.

AI models and sandboxes#

The agent, the judging chat, image descriptions and search embeddings all run on Nebius Token Factory through its OpenAI-compatible API.

The embedding model, Qwen/Qwen3-Embedding-8B at 1,024 dimensions, is fixed in code because it must match the database's vector column.

Web, video and code#

Email#

Emails go out through Resend: judge invites and reminders, notices to the organizer, and winner and thank-you emails.

Without RESEND or FROM_EMAIL, no email is sent and the rest of the app works. Without APP_URL, links use https:// plus VERCEL_PROJECT_PRODUCTION_URL on Vercel, or http://localhost: plus PORT (3000 by default).

Emails to reserved example domains, such as example.com or anything ending in .test, aren't sent. They're recorded as failed, even when EMAIL_REDIRECT_TO is set.

Hosting#

Landing page and site hosts#

The marketing landing page only appears on the official RoundOne site. A self-hosted instance doesn't show it: / is the sign-in screen or the dashboard.

SITE_HOSTS lists the hostnames that serve the landing page, separated by commas. It defaults to roundone.dev,www.roundone.dev. Set it to an empty string to turn the landing page off. Hostnames match without the port and ignore case.

SITE_HOSTS=roundone.dev,www.roundone.dev

On a site host, / shows the landing page without changing the URL. On other hosts, signed-out visitors to / go to /login.

Preview in development#

When NODE_ENV isn't production:

• http://roundone.localhost:3001 is treated as a site host, so you see / as a signed-out visitor to the official site would. Browsers resolve any *.localhost name to your machine. Use your dev server's port.
• /landing opens directly on any host.

/docs is public on every host, signed in or not.

Demo login#

For a public demo, set DEMO_MODE=true. The sign-in form then comes filled in with a shared demo login, so visitors such as hackathon judges just click Sign in. See Demo login for what they can do.

DEMO_MODE=true
# Optional: the demo login. These are the defaults.
DEMO_EMAIL=demo@roundone.dev
DEMO_PASSWORD=try-roundone-demo

The login is public on purpose. The demo account carries demo: true in its Supabase app metadata, which only the secret key can set. Row-level security reads the same flag: the demo account can read the hackathons marked as demos and nothing else, can't write anything, and can't create hackathons. The app also turns off every control that would save.

Create the demo account and the demo hackathons with the seed script, once the migrations are applied:

pnpm demo:seed

It builds three hackathons with sample projects, judges, agent reviews and scores: one with results published, one partway through judging and one still in setup. They belong to a separate demo-owner@roundone.dev account, which no one signs in to. Pass --owner you@example.com (or set DEMO_OWNER_EMAIL) to own them yourself, so you can edit them in the app. Running the script again replaces them and resets the demo login's password to DEMO_PASSWORD.

Demo hackathons keep their submission form and Intake API turned off, and their judge links can't submit scores, so the demo account can open a judge link without changing anything. Turning DEMO_MODE off only hides the login from the sign-in page. To close the demo, also delete the demo account in Supabase.

Related#