More ways in than a pull request.

Most of NebuCoders happens on GitHub and in Discord. These three doors do not. They are for members who want to put the skill somewhere it lands on someone else — a non-profit's mission, a competition floor, or a classroom that has never had one of us in it.

Honest status, since this page is mostly about the future: the only one of these running today is competing, and the only evidence for it is MuseBot AI at WRO 2026. The other two doors are designed and not yet open. We would rather publish them and be held to them than announce them the week they happen.
Not live yet

Volunteer with NGOs and INGOs

Non-profits have missions and not enough hands. This community has people who can build things and want the work to matter. The door exists to connect those two without either side having to go looking.

  1. We build the campaign with the organisation

    An NGO or INGO brings a mission that needs hands or software. We scope it with them into something a volunteer team can actually finish — a defined outcome, not an open-ended ask.

  2. It opens to members

    The campaign is posted to the community. Anyone in the org can put their name forward.

  3. Screening

    Volunteers are screened before they are placed. Non-profits are trusting us with their name and often with vulnerable people — sending whoever raises a hand first is not good enough for that.

  4. The team does the work

    A person or a team takes the mission through to completion, with the organisation as the one who decides when it is done.

  5. Two certificates

    On completion, the volunteer receives a certificate from the partner organisation and one from NebuCoders. Two names on the record, because two organisations actually vouched for the work.

Where this stands

No campaign has run and no partner is signed, so no certificate has been issued by anyone. What exists is the design above. If you run an NGO or INGO and have a mission that would suit a screened volunteer team — or you are a member who wants to help stand this up — get in touch. Standing up a program is one of the fastest ways to end up leading something here.

Running

Compete for NebuCoders

Competitions are the one place where the work gets judged by people who owe you nothing. That is uncomfortable and it is exactly why it is worth doing.

We post what is coming up

STEM competitions worth entering — hackathons, olympiads, robotics championships, CTFs — collected in one place instead of found by accident three days after the deadline.

Teams compete under the org

Members form a team and enter representing NebuCoders. Titles come back to the community, and the build is documented publicly the way every other project here is.

Mentoring, both directions

A team going to a competition gets mentored by people here. In return, members who have already been through one mentor the next generation. That exchange is the whole deal — it is what keeps the knowledge in the community instead of leaving with the person who earned it.

Our own hackathons

We want to run our own events with real prizes — cash, or tool and service subscriptions that are worth something to a developer who is just starting. Not scheduled yet, and we would rather say so than announce a date we cannot hold.

The one that is real so far

MuseBot AI — 2nd place at the WRO Bangladesh National Final 2026.

Three members, one robot, a silver medal in Senior Future Innovators, and the Asia-Pacific Open Championship in Hyderabad next. Everything about how it was built is published, including what did not work.

Read the build
Not live yet

Teach beyond the internet

Digital literacy is distributed about as evenly as everything else is, which is to say badly. You cannot fix that from a Discord server.

Who this is for

Children and adults in remote areas and camps — people for whom the barrier to digital literacy is not motivation, it is that no one has ever come and shown them. Everything else NebuCoders does quietly assumes a laptop and a connection. This door does not.

How it works

Members travel to a location and teach in person. Sessions are built around what is actually useful to that group rather than a fixed syllabus, and around the hardware that is actually in the room.

What we need before this runs

A partner organisation with existing access and trust in the area, a safeguarding process for working with children, travel funding, and members who can commit to more than one visit. A single drop-in session teaches almost nothing. None of that is in place yet.

Why it is on this page anyway

Because writing it down is how it gets built. If you have run something like this before, or you work with an organisation that has the access we do not, you are the person who makes this real.

Two of these need someone to build them

NebuCoders is run by its members, which means a program exists when a member decides it should. If one of these doors is the reason you are still reading, it is probably yours.