Stranger Builds

Build week · Submissions close Sun 8 Nov

How it works

Official Rules

Updated 4 November 2026

The short version

  1. Build something new, started after the opening (Friday 30 October, 23:00 UTC). Bring your users, not your product.
  2. Teams of 1 or 2. Solo is judged the same.
  3. Pick a track: Real users (people use what you build) or Hard problems (push new tools somewhere new).
  4. Open up to 2 challenges. Complete one to open another.
  5. Play Trick or Feedback: give feedback to 1 builder, get feedback from 1. Then change one thing because of it.
  6. Every project follows one path: Pick an idea → Ship it → Get feedback → Improve it → Submit.
  7. Ship it in public and submit before Sunday 8 November, 23:59 Argentina time (Monday 9 November, 02:59 UTC). Keep your link working until results on Thursday 19 November.

1 The one rule: build something new

Build something new this week. Bring your users, not your product.

You can bring tools, libraries, templates, AI coding agents, ideas and your audience. You can't bring a product you already had.

What counts as new

  • You started it after the opening: Friday 30 October 2026, 23:00 UTC (Saturday 31 October, 10:00 in Melbourne). One instant for everyone, wherever you are.
  • It has its own link: its own app, repo or agent address.
  • A new agent for a product you already have counts if it has its own entry point and its users start from zero.
  • Polishing, rebranding or adding a feature to an old product does not count.
  • Forks don't count. Starting from a template does.

How we check it

  • GitHub projects: a new repo created after the opening, not a fork.
  • Base44 projects: your app ID, a dated screenshot of the app's Version history showing its first version after the opening, and one screenshot of the editor showing the app ID and your account. Copying or remixing an app that already exists (someone else's, or your own from before the opening) does not count, even if the copy is new.
  • The system checks this when you create your project and when you submit. Finalists get a deeper look: commit history, timestamps and, for Base44, the app's origin.
  • If something doesn't add up, we ask you before we decide.

2 Who can take part

  • You are 18 or older and an adult where you live.
  • You registered for Stranger Builds on Luma (San Francisco, Melbourne, Bangalore or online), signed the pact at strangerbuilds.com and activated your account with the Duck on ASI:One.
  • One account per person. Your account is yours: don't share it or make a second one.
  • You can take part from anywhere, except where the law forbids it or where we can't lawfully pay a prize (Terms, section 3).
  • Who can't win: NERDCONF staff and crew running the event, and their households. Judges can't compete in anything they judge.
  • Sponsor employees can take part, but can't win their own company's prize.
  • To receive a prize you may have to prove your identity, age and that you can legally receive it.

3 Teams

  • 1 or 2 people. Solo is allowed and judged the same as a team.
  • You can be on up to 2 projects at the same time.
  • You can change your team any time before submissions close: Sunday 8 November, 23:59 Argentina time (Monday 9 November, 02:59 UTC).
  • If someone leaves, the project stays with the person who remains.
  • One submission per project. List everyone who actually built it, and nobody who didn't.
  • Agree inside your team how you split a prize. We pay one adult team member per prize and don't settle disputes between members.

4 Two tracks: pick by why you came

Real users is for you if you want real people to use what you build. GitHub is optional (required for the Fetch.ai challenge).

Hard problems is for you if you want to push the newest tools somewhere they've never been. A public GitHub repo is required.

Both tracks follow the same path: Pick an idea → Ship it → Get feedback → Improve it → Submit.

  • Pick an idea: what you'll build and for whom.
  • Ship it: a public link that works without you: anyone can open it, logged out (Hard problems: a public GitHub repo), with your public proof of launch (section 9).
  • Get feedback: Real users: feedback from 1 builder outside your team, through Trick or Feedback: their written note. No minimum score. Hard problems: a judge looks at your work against the challenge's technical goal (section 5).
  • Improve it: Real users: at least one change you made because of that feedback ("they told me X, I changed Y"). Hard problems: reach the challenge's technical goal, confirmed by a judge.
  • Submit: before the close (sections 10 and 11).

Each step and each completed challenge grows your project's house in the Duck World.

5 Challenges, and what "completed" means

Each challenge has its own brief. A brief can add to these rules for its own challenge; where a brief and these rules disagree, these rules win unless the brief says which rule it changes.

  • Base Combinator · Find the money (Real users, Base44): your Base44 app is shipped, gets its feedback and is improved (section 4: feedback from 1 builder outside your team, and one change made because of it).
  • Get your agent hired (Real users, Fetch.ai: Agentverse and ASI:One): your agent is live on Agentverse, findable in ASI:One, and gets its feedback and is improved (section 4) with tries made through ASI:One. A GitHub repo is required.
  • Build a self-improving agent (Hard problems, TrueForge by TrueFoundry): the public repo with the agent running on TrueForge, and a later run that improved on run 1 by changing its own skills or instructions, confirmed by a judge.
  • Make coding agents sweat (Hard problems, Shelled AI): the public repo built with the Shelled AI app and an edge-case report (where the agents shone and where they broke), confirmed by a judge.
  • Build anything (Real users, any tech): for a project that fits no sponsor challenge. It is completed like the other Real users challenges (section 4: feedback from 1 builder outside your team, and one change made because of it). It has no prize of its own: its projects count for the Community Cup and don't enter the people's vote.

How completion is recorded. Real users: the system marks it when your proofs pass. Hard problems: you declare it by delivering your repo in the app; a judge confirms or rejects it. Until then it shows as "declared". If it's rejected, you're told why and can fix it before the close.

Completed vs winning. Completed is a fixed bar anyone can reach, and it earns rewards win or not (section 13.4). Winning is a competition among the projects that completed.

6 Up to 2 challenges per project

A project can have up to 2 challenges open at once, from either track. Complete one to open another. You can't enter a challenge by ticking a box: the system checks each challenge's proof.

7 Trick or Feedback: how you get users, and fair play

Builders here are each other's first users. Trick or Feedback runs in the app from the opening until the close.

  • Trick or Feedback assigns you a project. You don't pick. One try per person per project; never your own team's.
  • Spend at least 2 minutes really using it. Leave a written note (what blew your mind, what frustrated you, what you'd change) and a 1–5 "would you use it?". Every note earns you candy in the Duck World.
  • On the Fetch.ai challenge, tries happen through ASI:One.
  • Only tries from other participants, assigned by Trick or Feedback, count toward Get feedback (section 4). People from outside the event are your users: they reach your project through its Try it page (app.strangerbuilds.com/try/your-project), use it and can vote for it. On the Fetch.ai challenge, they reach your agent through its ASI:One link.
  • Flagged: swap rings, tries under 2 minutes, empty or copy-paste notes, several accounts from one person. A flagged try doesn't count until a person looks at it. Faking or trading tries can disqualify your project.

9 Ship it: launch in public

Shipping includes one public proof of launch, linked in your submission:

  1. a launch post on X, ideally with a launch video; or
  2. a demo video (public or unlisted, up to 2 minutes); or
  3. a pitch video (up to 2 minutes).

10 What to submit

One submission per project, in the app, before the close: name, team, who it's for and what it does; the public link (and the public repo if your track or challenge needs one); the proof it's new (section 1); the challenges completed or declared, with their proofs; your proof of launch (section 9); your recap ("they told me X, I changed Y"); what existed before and what you used, with licences; test access shared privately if judges need a login. Never put passwords, keys or anyone's personal data in public fields. Use English (other languages with English subtitles).

11 Deadline and key dates

  • Fri 30 Oct, 23:00 UTC: the opening. The pact and the Duck World open; new work counts from here.
  • Sat 31 Oct: in person in San Francisco (Frontier Tower), Melbourne (Stone & Chalk) and Bangalore, 10:00–18:00 local.
  • Until the close: teams and communities stay open; you can change yours any time before submissions close.
  • Fri 6 to Sun 15 Nov: the people's vote.
  • Sun 8 Nov, 23:59 ART (Mon 9 Nov, 02:59 UTC): submissions close.
  • 10–15 Nov: judging.
  • Thu 19 Nov: results, all together.

The last version you submit before the close is the one we judge. A draft or a message is not a submission. After the close: no new features. If something breaks and you can't submit, tell us before the close at hey@nerdconf.com with a screenshot and the time. Any extension is announced to everyone and applies to everyone in the same situation.

12 Judging

People pick the winners. The system only helps them look.

Best of the day (San Francisco, Melbourne, Bangalore)

  • Everyone can submit until the close. Submitting means uploading your evidence in the app (section 10). A project competes for its city's Best of the day if it submits before that city's cut: the announced demo time plus 10 minutes, 16:10 local time on Saturday 31 October, with a sponsor proof declared and not rejected (section 8), and at least one team member at that venue. A project's city is the event its builders came from (their registration).
  • After the 16:10 cut, the venue's judges look at the submitted projects in the app, and the judges see the same live ranking. The top 5 finalists pitch, and each city's jury picks the best project or projects and announces them there the same day (17:30 local in San Francisco and Melbourne).

Challenge prizes: judged after the close, among the projects that completed. For each challenge the judges shortlist the top projects (at least 2 judge reviews each) and NERDCONF picks the winners from the shortlist. The system suggests where to look first (extra points for real users and for changes made from feedback); it uses no score formula. Real use outside the event (the people's vote, usage you can show) is part of what judges see.

Fair judging: judges disclose conflicts and step aside; sponsors can't pick a winner outside this process; judges look only at what you submitted; ties are decided by NERDCONF after hearing the judges; decisions are final; winners are provisional until the proof checks pass, and if one fails the next eligible project wins.

13 Prizes

USD 10K in prizes and credits. The amount of each prize is shown inside the app.

13.1 The prizes

  • Best of the day: San Francisco, Melbourne and Bangalore (section 12).
  • Base Combinator · Find the money (Base44): 1st and 2nd.
  • Get your agent hired (Fetch.ai).
  • Build a self-improving agent (TrueForge by TrueFoundry): best build and runner-up.
  • Make coding agents sweat (Shelled AI).
  • The people's vote (Fetch.ai): the most votes in the Duck on ASI:One (13.3).
  • Community Cup: 1st, 2nd and 3rd, for the three communities whose members submitted the most projects, one prize per community (section 14).
  • A one-year GitHub Copilot Max subscription: for one builder, drawn at random on 19 November among all members of the projects that win a paid prize (Terms 12.5). Every member has one equal chance. It is the only prize decided by chance.

13.2 How prizes combine

A project can win one challenge prize. On top of it, it can win Best of the day and the people's vote. A Community Cup prize goes only to a project with no other paid prize. The Copilot Max subscription goes to a person. Every paid prize needs a sponsor's tech (section 8). A prize may stay unawarded.

13.3 The people's vote

Anyone can vote, through each team's own ASI:One link, Fri 6 to Sun 15 Nov. Only projects that completed a sponsor challenge, not Build anything (Hard problems: declared; if a judge rejects it, its votes don't count). One vote per ASI:One account. Fake accounts, bought votes and swaps are disqualified.

13.4 Completing a challenge, win or not

Your house grows in the Duck World, a place on the sponsor's demo list, and a written note from a judge.

13.5 Getting a prize

Paid per project to one adult team member (Copilot Max to its winner). Winners get an email from hey@nerdconf.com and have 10 days to reply. Prizes are paid within 30 days of the announcement once verified (Best of the day by 30 November). Prizes are before taxes and fees, can't be transferred, and credits are not money. Full terms: Terms and Conditions, section 12.

14 Communities and the Community Cup

Your community is the one you build with. Pick it in app.strangerbuilds.com/profile → "Your community". You can change it as many times as you like until submissions close. No community picked, no count.

The Community Cup, in six rules:

  1. The community whose members submit the most projects by Sunday 8 November, 23:59 Argentina time, wins. Submitted means "Submit" pressed in the app. Build anything projects count too.
  2. Prizes: USD 750, 450 and 300 for the top three communities. Each goes to the team behind that community's best project, as the judges rank it. If that project already won another paid prize, it goes to the community's next best project. It is paid to one adult member of that project, like every other prize (13.5), never to the community or its organisers.
  3. Pick your community in your profile. You can change it until the close. No community picked, no count.
  4. One project counts once, for the community of the person who submitted it.
  5. Ties go to the community with more projects live at a public link.
  6. Standings are posted in Slack on Thursday and Saturday. The winners are announced with all the other prizes.

Offering anything for a community pick, or creating empty projects to count, disqualifies them.

15 Disqualification

A project or person can lose prizes or be removed for: an old product passed off as new; fake, traded or swapped tries; fake votes; more than one account; proof that doesn't match; someone else's work without permission; influencing a judge, sponsor or crew outside the process; breaking the code of conduct or the law. We tell you why and you can answer once before we decide.

16 Conduct

Roast the app, never the person. No harassment, hate or threats; no malware, phishing or testing systems you don't own; don't expose anyone's data or secrets; don't fake results; follow each venue's rules and the crew. Report problems to hey@nerdconf.com. Full code of conduct: strangerbuilds.com/conduct.

17 What is public

Public inside the event: your duck, project page and house, step on the path, challenges, public link and repo. Public on the web: winners. Never public: your email and the level you picked at sign-up. Sponsors see your name only if you switch it on. You own what you build (Terms, sections 6, 8 and 13).

18 Questions and changes

Ask hey@nerdconf.com or the Duck. These rules are in the Duck's MCP; if the MCP and this page disagree, this page wins. Any change that matters goes out through the app and email; judging criteria never change after the close in a way that hurts submitted projects.

Terms and Conditions · Code of Conduct · Back to Stranger Builds