Getting started
Welcome to Forke
Forke is the micro-task marketplace where developers earn real money by shipping real code — no fake projects, no bidding wars, just bite-sized work with instant UPI payouts.
Overview
Think of it as Fiverr × GitHub × an RPG. Founders post small, scoped tasks with a fixed budget and a time estimate. Developers claim a task that matches their level, ship the work as a pull request, and get paid the moment it's approved. Every completed task becomes verified, timestamped proof of work on your public profile. The whole thing is Git-native: work flows through real branches and pull requests, never ZIP files or pasted code.
Why Forke exists
Building fake CRUD apps impresses no one, and traditional freelancing means proposal-bidding wars and week-long timelines for a ₹300 bug fix. Forke removes both frictions: developers get a structured, low-friction way to say “I have two hours — give me a real task, pay me”, and founders get a trusted, fast, scoped micro-task economy instead of a full freelance platform. Read the longer story on What is Forke.
Two sides of the marketplace
These docs are written for both audiences. Jump to the side that fits you:
- For developers — claim tasks, ship code, level up, cash out.
- For founders — post scoped tasks, fund escrow, review a plain-English verdict.
The core loop
Three principles
Everything on Forke rests on three architectural rules:
- Never ZIP uploads. Every submission lives in a pull request. No exceptions.
- Forke is the middle layer. Developers never touch owner repos directly — Forke mirrors, branches, and merges.
- AI assists, humans decide. AI generates the verdict card; founders make the final call.
Where to go next
- New to the model? Read Core concepts.
- Ready to earn? Start with Browsing the bounty feed.
- Curious how work is judged? See the review pipeline.
- Want the level breakdown? See the Levels page.