Navigation
Let’s talk Pune, India / Independent developer
Selected work

PairMe

Developer tools / Realtime collaboration
2026

A collaborative coding platform that turns a concrete blocker into a focused pairing session. Find a problem, join a room, and work through it together.

My part
Product engineering / Full-stack development
Built with
Next.js / TypeScript / PostgreSQL / Stream
PairMe's room directory: Pair better. Ship faster. Search for rooms and problems, browse problems, start a room, or help another developer.
Built to work together.

The room directory. A problem is the starting point, not a social feed.

Start with the blocker.

PairMe is built around a useful loop: bring a concrete problem, find someone to work with, pair live, and leave a record of what changed.

Each room carries the problem, stack, and repository context. Developers request access; the owner reviews requests and manages capacity. Collaboration starts with enough context to be useful.

A room has a lifecycle.

Open, requested, matched, live, completed, or cancelled. These states explain what a room allows, rather than reducing collaboration to an online indicator.

Shared Markdown notes, session outcomes, and GitHub issue, PR, and commit links keep the work attached to the conversation. A completed session becomes a read-only record.

OpenRequestedMatchedLiveCompleted

The live session is a boundary.

Stream Video and Chat are loaded when a permitted member opens a live session. The video client connects through a server-backed token provider before joining a call.

Camera and microphone access are optional. A developer can join without either device, keeping permissions from becoming the price of entry.

System overview
BrowserRooms, requests, shared notes
Next.jsApp Router + application APIs
ClerkIdentity + authenticated access
StreamVideo + chat, loaded on demand
PostgreSQLPrisma + persistent room state

Built around the work.

Room discovery, owner-managed requests, live sessions, shared notes, and outcome records form the product. This case study describes the implemented system; usage and business impact measurements have not been supplied.