How It Works
From brief to working software.
Post a real problem, let developers compete to solve it, and choose the solution you have already seen run.How It Works
Instead of browsing profiles and hoping someone can deliver, you choose from software that already exists, is tailored to your problem, and is proven to work.The evaluation happens before you choose.
Step 01
Fund a contest
Write the brief, set a deadline, and pay the reward into escrow. Start from scratch or from your own repo.Step 02
Developers build
Each developer gets a private repo for their entry and ships versions as they improve it.Step 03
Try every version
Open each version's preview to see the end product in action. Developers can choose to share their code too.Step 04
Pick the winner
Choose the solution that works best. You get its full code, and the reward is paid out to its builder.Step by Step
Two sides of the contest, one standard: what works.
Clients get proven solutions. Developers get judged on what they build. Here is what each side does along the way.01 / For Clients
Launch a contest, choose a result
01
Describe the problemWrite a brief for your project, the same way you would scope it for a hire. Optionally start it from your own repo and branch.
02
Fund the rewardTop up your wallet and pay the reward into escrow. The contest opens once it is funded, and you can guarantee it to attract more developers.
03
Try each versionDevelopers ship versions as they improve their entries, each with a preview of the end product. Some also open their code to you.
04
Pick the winnerWhen the deadline passes, the contest moves to judging. Choose the version that works best: you get its full code and the reward is released to its builder.
02 / For Developers
Build, ship, and get rewarded
01
Find a funded problemBrowse open contests with clear briefs, deadlines, and rewards that are already held in escrow.
02
Enter with your git accountConnect GitHub, GitLab, or Gitea. Entering creates a private repo in your account, seeded from the client's code when there is any.
03
Ship versionsPush to a branch, deploy a preview, and add it as a version with its preview URL. Your code stays private unless you choose to share it.
04
Win and get paidThe best working solution wins, regardless of your title or school. The reward, less the platform fee, goes to your payout account.
Contest Lifecycle
Every contest moves through the same stages.
These are the statuses you will see in your dashboard, from the first draft to the payout.01Write the brief, pick a deadline and reward, and optionally point it at your repo. Free, and not visible to developers yet.
02Ready to publish. Pay the reward from your wallet into escrow to open it.
03Developers enter, push code, and add versions with live previews until the deadline.
04The deadline has passed. Try each version's preview, read any code developers shared, and choose the winner.
05You get the winning code, merged into your repo and saved as a download. The reward is released to its builder.
Contests that aren't guaranteed can be cancelled before completion. Anything already paid goes back to your wallet.
Built on Git
Real repos, real commits.
Entries live in git from the first push, so what you judge is exactly what you get.01
Start from a repo, or from nothingClients can point a contest at a repository and branch. Public repos work from any host; private ones go through the client's connected git account.
02
A private repo per entryEntering creates a private repo in the developer's own account, with the client's branch and history pushed in, or a README for blank contests.
03
Versions pinned to commitsDevelopers add versions from their branches. Each one is pinned to a commit and comes with a preview URL the developer deploys, showing the end product in action.
04
Code shared on the developer's termsSource code is private by default. Developers can open it to the client in the repo viewer, and close it again, at any time.
05
The winning code is yoursWhen the contest completes, you get full access to the winning version. It is merged into your origin repo, if there is one, and saved as an archive you can download any time.
Versions
v3
feat/split-payments
9f3c2a1e7b04
v2
feat/fuzzy-dates
4be81d0c22f9
v1
main
c71e9ab05d3e
What You Evaluate
Everything a resume can't tell you.
The questions you normally answer months after hiring are answered before you choose.01
The end product
Every version comes with a preview URL showing the product in action. Judge it the way your users will, not from a demo call.02
Delivery speed
Deadlines are part of the contest. You see who delivers working software on time, not who promises to.03
Edge-case handling
Try each version's live preview with the scenarios that matter to you and see how it behaves when things do not go to plan.Questions
Common questions, straight answers.
01
What kind of projects work as a contest?
Any project or technical problem you can describe with clear requirements: a feature, a tool, an integration, or a self-contained piece of a larger system. You can also start a contest from your own repo and branch.02
How do I judge the submissions?
Each entry is a set of versions. Every version is pinned to a commit and comes with a preview URL from its developer, so you can try the end product on the contest page. Pick the version that best solves your problem.03
Can I see the source code before choosing?
Only if the developer shares it. Code is private by default, and each developer can open it to you in the repo viewer, or close it again, at any time.04
Do I get the winning code?
Yes. When the contest completes, you get full access to the winning version. It is merged into your origin repo if the contest started from one, and exported as an archive you can download at any time.05
What does a guaranteed contest mean?
Once a guaranteed contest is paid for, it can't be cancelled, so developers know a winner will be paid. Guaranteeing is optional and can't be undone.06
What if no entry is good enough?
If the contest isn't guaranteed, you can cancel it while it is open or being judged, and the escrowed reward goes back to your wallet. A guaranteed contest always ends with a winner.07
What does it cost?
Creating a contest is free. Coderank keeps 10% of the reward and the winning developer gets the rest. Card processing fees for wallet top-ups are shown before you pay.08
How and when do developers get paid?
When the client picks a winner, the reward, less the platform fee, is released to the winner's payout account: a Nigerian bank account, PayPal, Payoneer, or Wise.09
Which currencies are supported?
Rewards are held and paid in Naira. You can view every amount in Naira or US dollars, converted at the daily exchange rate.10
Do I need a git account?
Developers do: entering a contest creates a private repo in your GitHub, GitLab, or Gitea account. Clients only need one to start a contest from a private repo.11