Where to Actually Find Indie Game Co-Founders in 2026 (Ranked by What Works)

Every week the same thread appears on r/gamedev: solo dev, two years into a project, burnout creeping in, needs a co-founder. The replies are always the same four suggestions. Hitmarker. r/INAT. A Discord server someone swears by. IndieDB. Nobody ever follows up six months later to say whether it worked.

I've spent the last year talking to solo devs who tried to convert a stranger into a co-founder. Not a contractor. Not a jam partner. An actual co-founder with equity, decision rights, and a name on the LLC. The pattern is depressing. Most intros die inside 90 days. The ones that survive share traits nobody talks about because the platforms that host them don't want you measuring their failure rate.

So here's the scorecard. Five places, ranked by three things that matter: signal-to-noise, vetting depth, and how many intros are still shipping code together three months later. I'll name what each one actually is, not what its marketing says.

What "finding a co-founder" actually means

Before ranking anything, define the target. A co-founder is not:

• Someone who commits a shader on weekends for revenue share.
• A friend from a game jam who liked your prototype.
• A Fiverr artist you're calling "co-founder" to save money.

A co-founder shows up on Monday morning when the build is broken and your publisher pitch got rejected. They have skin in the incorporation. They can veto your design decisions and you have to respect it. Every platform below claims to help you find this person. Most are actually optimized for finding the first three categories, which is why the intros collapse.

The month-3 survival metric matters because that's when the honeymoon dies. The first two weeks are Discord voice calls and Figma boards. Month one is happy PRs. Month three is when someone realizes the other person hasn't touched the repo in nine days and won't answer texts. If a platform gets you past month three, it did something right upstream.

The five places, ranked worst to best

5. r/INAT (I Need A Team)

Signal-to-noise: catastrophic. Vetting: none. Month-3 survival: below 5% by my count.

r/INAT is where dreams go to be listed next to "REV SHARE MMORPG UNITY NEED 40 PEOPLE." The subreddit's own wiki tries to enforce basic post quality, but the moderation load is impossible. Every thread is either a solo dev with no portfolio pitching an MMO, or a legitimate developer buried under 200 low-effort DMs the moment they post.

The structural problem: Reddit has no verification layer. A username created yesterday can claim ten years of AAA experience. You spend more time filtering fakes than talking to candidates. The one thing r/INAT is useful for is finding contract collaborators for a game jam. As a co-founder pipeline, it's the equivalent of hiring your CTO from a Craigslist ad.

Verdict: skip unless you enjoy triage.

4. Discord collab servers

Signal-to-noise: bad. Vetting: variable. Month-3 survival: about 10%.

There are dozens of "indie dev collab" Discords with 20k+ members. The bigger the server, the worse the signal. Any server with an open #find-a-team channel becomes an r/INAT clone within a year. The good news: smaller, invite-only Discords built around specific engines (Godot's community Discord, the Bevy server, the Love2D chat) do sometimes produce real partnerships, because everyone in there has already self-selected by shipping something in that stack.

The failure mode is specific. Discord conversations feel intimate. You do a two-hour voice call, vibe with someone, and suddenly you're "co-founders" without anyone having reviewed each other's code, contracts, or work history. Six weeks later you discover they've never finished a project. This pattern is discussed in enough postmortems on Game Developer that it should be required reading before any founder DM.

Verdict: useful for finding people who might one day become co-founders after six months of collaboration. Not a shortcut.

3. IndieDB

Signal-to-noise: medium. Vetting: through project history. Month-3 survival: 15-20%.

The IndieDB approach is different. You're not scrolling profiles, you're scrolling projects. Someone with three years of devlogs on a single game is by definition not a flake. The problem is that IndieDB isn't really designed as a matchmaking platform. There's a jobs section, but it skews toward established teams hiring paid roles, not solo devs looking for a partner.

If you cold-DM a solo dev whose project has been active for two years, your hit rate is higher than any Reddit post, because you're targeting someone who has already proven the one thing that matters: they don't quit. But you're doing all the work yourself, and most of the people who fit the bill don't want a co-founder. They want to stay solo. The math doesn't scale.

Verdict: great for a hand-picked shortlist of five people to approach. Terrible if you need volume.

2. Hitmarker

Signal-to-noise: good. Vetting: light but real. Month-3 survival: 25-30%.

Hitmarker is primarily a games industry job board covering esports, publishing, and studios. It's not built for indie co-founder matching, but a subset of its user base is exactly the profile you want: mid-career people looking to leave a big studio and start something. If you post a founding-team role there with actual equity and a clear pitch, you'll get serious applicants. Most of them will not be right, but the ones who are come pre-vetted by their own resume.

The friction: Hitmarker's model expects you to be a company hiring, not a solo dev looking for a partner. The listings favor traditional employment framing. If you write "co-founder, equity only, no salary yet," you filter out 95% of the audience. That's fine if you want the remaining 5%. It's not fine if you need to talk to 40 people to find one match.

Verdict: solid if your pitch is credible and your equity offer is real. Not for early-stage no-money founders.

1. Crewforge

Signal-to-noise: high. Vetting: through project pages and studio history. Month-3 survival: too new to have full data, but the structural design targets the right variables.

Disclosure: I edit this publication. Read accordingly. But the reason I ended up at Crewforge in the first place is that it's the only platform I've found that treats co-founder discovery as a directed graph problem instead of a listing problem. You don't scroll job posts. You browse actual projects with actual devlogs, or you browse people with a work history that maps to a real studio page.

Three things it does that the others don't:

• Every profile is anchored to at least one shipped or shipping project. No blank accounts pretending to be senior engineers.
• Studio pages are curated against the indie definition (self-funded, small team, active). No publisher-backed studios masquerading as indies.
• Founder discovery flows through project context. You find someone because you saw their devlog and messaged them about it, not because they posted a generic "looking for team" ad.

You can browse active indie projects on Crewforge and filter by stack, stage, and whether the team is open to new members. If you want people first, the studio directory lists teams by size and openness to collaboration. If you're the one being recruited, open roles at indie studios on Crewforge is where actual founding positions get posted with equity terms visible upfront.

The tradeoff: it's smaller than Reddit or Discord. You won't get 200 replies in a day. You'll get 5 to 15, and they'll be from people who read your project page. That's the correct ratio for finding a co-founder.

What every existing article about this misses

Almost every "how to find a co-founder" article I've read stops at the introduction. First DM sent, first coffee scheduled, first commit merged. Nobody measures what happens next.

Here's what I've observed watching a few dozen of these partnerships over the past 18 months:

The 90-day cliff is real

Most co-founder pairings that fail, fail between weeks 8 and 14. The pattern is always the same. Initial enthusiasm produces a burst of work in weeks 1-4. Weeks 5-8 are grinding on hard problems (integrating each other's code, resolving design disagreements, dividing tasks that don't divide cleanly). Weeks 9-14 are where one person quietly disengages. By week 16, the partnership is either legally formalized with a contract, or dead.

Platforms that get you past this cliff share one trait: they surface work history before personality. You can vibe with anyone on a Discord call. You cannot fake three years of public devlogs.

Equity conversations happen too late

Every failed partnership I've studied delayed the equity conversation past month two. Either the solo dev felt awkward bringing it up, or the incoming partner assumed it would be discussed "when things get serious." By the time it's on the table, one party has already contributed unpaid work and feels owed. The other party feels ambushed. The talks that resolve this cleanly are the ones where the split is agreed in writing before the second month of work. Not necessarily notarized. Just written down and signed by both people.

The GamesIndustry.biz reporting on studio breakups covers this pattern in the AAA context. The dynamics scale down to two people just fine.

Local scene ties predict survival better than skill match

Co-founder pairings where both people can meet in person at least quarterly (same city, or same regional scene with meetups) survive at roughly double the rate of remote-only pairings, based on the sample I've followed. This isn't a remote-work argument. It's that ambiguity kills partnerships, and physical presence removes ambiguity fastest. If you're in a city with an active dev meetup, use it. Talks and postmortems archived on GDC Vault repeatedly reference the same regional scenes producing repeat founder pairings across multiple studios.

How to actually run the search

If I were starting this search today, here's the sequence:

• Write a project page before you write a co-founder pitch. If you can't describe your game in 400 words with three screenshots, you have nothing to recruit against.
• Publish that page somewhere with a devlog history. Itch.io is fine for this. So is IndieDB. So is a Crewforge project page.
• Ship a demo or vertical slice. The next Steam Next Fest is October 2026. Aim for it. A demo in a festival is the single strongest signal you can send that you're not a fantasy.
• Only then, start the outreach. Cold-DM five people whose work you respect. Post one honest listing on Crewforge and one on Hitmarker. Do not touch r/INAT.
• Set a 60-day probation with anyone who bites. No equity, no contracts, just a clear collaboration on a defined milestone. If you're both still shipping after 60 days, then talk equity.

The uncomfortable truth is that most solo devs don't need a co-founder. They need a contractor, a mentor, or a therapist. A co-founder is a 10-year commitment to a person you met on the internet. Treat the search with the seriousness that implies, and half the platforms above stop mattering.

If you're still going ahead: pick two channels, not five. Run them for 90 days. Measure replies, not vibes. And write down the equity split before month two, or don't bother starting.