Can I register for a hackathon without a team?

Yes. Devpost, Devfolio, and MLH-run events all let you register solo and form or join a team afterward. Team size caps (usually 1 to 4) are set per event, but registering alone is normal, and every major platform builds tools specifically for this.

How does Devpost's team formation actually work?

Devpost hackathons have a Participants page where registrants can opt in to a 'looking for team' checkbox and write a short blurb about their skills or idea. A 'Team-up request' emails the person directly from your Devpost account, so replying is as easy as replying to that email.

What do MLH and Devfolio hackathons use instead of a participants page?

Discord. MLH-affiliated hackathons typically run a #team-formation channel plus an #introductions channel, opened a few days before the event. Devfolio hackathons run something similar through their own community channels. Check your registration confirmation email or the hackathon's site for the invite link.

What should I actually write in a team-formation post so people respond?

Three things: what you can build, specifically ('React + Node' beats 'full-stack'), what kind of teammate you need, and a one-line idea if you have one. A bare 'looking for a team' gets scrolled past; a post that gives someone a concrete reason to reply gets answered.

How to Find a Hackathon Team When You Don't Have One

Not having a team isn't a reason to skip a hackathon. Every major platform builds tools for exactly this, because most events have more solo registrants than fully-formed teams walking in.

Devpost: use the Participants page

Once registered, check the "looking for a team" box and write a short blurb on your skills or idea. A "Team-up request" emails the recipient directly from your Devpost account, so replying is as easy as replying to that email. Browse the page yourself rather than waiting to be found: if you can code but not design, look specifically for a designer's post.

Devfolio or MLH: check Discord

MLH-affiliated hackathons typically run a #team-formation channel alongside #introductions, opened a few days before the event, sometimes with an organized "team formation mixer" before the clock starts. The invite link is usually in your confirmation email or on the hackathon's site. Devfolio hackathons run something similar through their own community spaces. Same mechanic as Devpost, just in chat instead of a form: post what you can do, scan what others offer, message directly.

What actually gets a reply

"Looking for a team, DM me" gets scrolled past: it's identical to a dozen other posts. Be specific on three things instead:

What you can build, concretely. "React and Node, comfortable with REST APIs and AWS deploys" is something someone can match against their own gap. "Full-stack developer" isn't.
What you need. "Need a designer" or "need someone to own the ML side" tells people whether they fit before they message you.
A rough idea, if you have one. Even one line ("something around campus food waste") gives people a concrete thing to react to.

Confirm team size before you recruit

Caps (usually 1-4) are set per event, not platform-wide, so don't assume one hackathon's rules carry over to the next. Check before you're four people deep into planning and find out the cap is three.

Nobody responding? Go solo

Solo hacking is a legitimate path, not a fallback: more work per person, but no coordination overhead either. If the team-formation channel isn't turning anything up close to the deadline, registering solo and building something smaller but fully yours is a completely reasonable call, and judges don't discount a solo entry for being solo.