Better collaboration for developers.
Discover people, start a project, build with a team, and turn what you actually shipped into a portfolio worth showing.
Discover
Find the right people first
Search by skill, availability, and interest to find developers who are looking for the same kind of project you are — then browse open projects that already need what you can build.
Ava Kapoor
Backend · Spring Boot
Leo Marchetti
Frontend · Next.js
Projects
Turn an idea into a team
Post a project with the roles you need, and let developers apply with context on what they'd bring. Every project has a home for its details, its open roles, and the people already on it.
Campus Marketplace
A peer-to-peer marketplace for student sellers.
Teams
Build with the right people
Every project has a team behind it: clear roles, membership you can see at a glance, and invitations that bring the right person in at the right time.
Campus Marketplace team
- AKOwner
- LMMaintainer
- RSMember
- TJMember
Workspace
From idea to execution
Once a team forms, the work needs a home. Every project gets a workspace: a board to track tasks, an activity feed to follow what changed, and a chat to talk it through — all in one place.
Todo
In progress
Review
Activity
- Ava opened a pull request
- Leo moved a task to Review
- 3 new messages in #general
Tasks
Ownership you can see
Work moves through clear stages, so everyone knows what's next, who owns it, and what's actually done — not just claimed. The stages shown here are illustrative of the general flow.
Messages
Two kinds of conversation
Direct messages are for one developer talking to another. Workspace chat lives inside a project, so the conversation stays attached to the work it's about.
Direct message · Leo Marchetti
Campus Marketplace · workspace chat
One connected ecosystem, not five separate tools
People, teams, projects, tasks, and chat all reference each other directly, so context never gets lost between them.
Contributions
From real work to real reputation
01
You do real work
A task, a pull request, a review — the things that actually move a project forward.
02
It's recorded as a contribution
Tied to the project and the team it happened in, not a self-reported line on a résumé.
03
It builds your developer reputation
Over time, a track record of what you've shipped and with whom.
04
It shows up in your portfolio
Ready to share with the next team, the next project, or a recruiter.
Portfolio
Your work should speak for you
Every project, skill, and contribution builds one developer profile — a timeline of what you've actually built, not a list of claims.
Coming soon: one developer identity
Sign in to other tools you build with, using the same Saanjha profile.
Ava Kapoor
Backend developer
6
Projects
42
Contributions
3
Teams
How it works
01
Create your profile
Your skills, interests, and what you want to build next.
02
Discover people and projects
Search for developers or browse projects looking for your skills.
03
Build together
Form a team, open a workspace, and get to work.
04
Showcase your contributions
What you shipped becomes part of your developer portfolio.
Security
Built with the fundamentals in place
Your own account
Sign in is tied to your credentials alone — no shared logins, no ambiguity about who did what.
Permission checks on every action
Team roles and project visibility are enforced on the backend, not just hidden in the interface.
Secure sessions
Sessions are managed carefully and expire, so access doesn't outlive the moment you granted it.