For developers done with working solo

Stop developing alone.
Pin your project.
Build a real team.

Side projects die solo. Corkbored is where you find the people who actually build with you — your team, maybe your cofounders — and where everyone who ships shares in what it becomes.

psst — the cards move. it's a corkboard.

github.com/mira/ledgerline

Open-source budgeting for freelancers

TypeScriptPostgreslaunched

Needs: mobile dev · ~5 hrs/wk

github.com/dev-sara/trailcache

Offline maps for backcountry hikers

RustReact Nativebuilding

Needs: Rust dev · backend

github.com/jq-dev/promptpit

Self-hosted eval harness for LLM apps

Pythonprototype

Needs: frontend · design eng

Your repo herereal commits required — no ideas guys

For builders between things

Find your team. Ship your thing.

// the team feeling, again

Million-dollar ideas sit abandoned because one person ran out of steam. Find builders who actually want to be there — people who chose your project, not just anyone with a GitHub account.

// the builders pledge

Everyone who joins agrees to treat each other with honesty and integrity. No ego, no politics, no spam PRs — just builders working together on something they believe in.

// share what you make

If it takes off, everyone who built it is already on the record — code, tasks, decisions, all of it. The spoils go to the people who earned them.

From repo to team

How it works

  1. Pin a project

    Link a real GitHub repo with real commits. Verified automatically — no vaporware on the board.

  2. Say who you need

    Collaborators, not employees: "React dev, great with tailwind!" Set the expectation up front.

  3. Choose your team

    Devs apply with a short pitch and their actual GitHub history. You decide who gets in.

  4. Build & share the upside

    Accepted members get repo access. If the project takes off, the contribution record is already there.

After the match

More than matchmaking — a place the team actually works.

Every project gets a shared workspace: a task board, async discussion threads, an announcements feed, and a live activity stream synced from GitHub.

And here's the part that matters later: tasks finished, threads decided, commits merged — it all lands on the contribution record. Design and docs count, not just code. When the project wins, nobody argues about who built it.

ApplicationsTasksDiscussionAnnouncementsActivity

To do

Results dashboard wireframeunassigned
Rubric scoring edge cases@jq-dev

Doing

CSV export for eval runs@ana-builds

Done

SQLite migration@jq-dev
Diff view fix@jq-dev

done + assigned = logged as a contribution

House rules

Pinned to the board

  • No ideas guys. Code first, then collaborators.
  • No drive-by PRs. Apply, get accepted, contribute.
  • Builders share the spoils. Contribution is on the record.

The board opens soon.