You name the files. You name the price.
A failing test, a migration you keep postponing, a feature behind a flag. Hand one off and read what comes back — on its own branch, checked against the files you named, and merged only if you say so.
A stranger, without the keys.
Handing work to someone you do not know is really a question of what they can see, so that is the part we built first. They never receive a copy of your repository, and never the ability to push to it. What comes back is a change, checked on our side against the files you named — the same change and the same file list always reach the same answer.
- ▹They never get your repository — only what you named — the issue text alone, or the files the job touches. Your call, per posting.
- ▹We check for secrets first — we put the files together on our side and check them before any of them leave. If something looks like a credential, the hand-off stops rather than going out.
- ▹Checked against the files you named — the change comes back through us. Nothing outside the files you named lands, and anything touching your CI setup or lockfiles is refused outright.
- ▹No push access, ever — the developer never gets push access to your repository. What they produce comes back through us, onto a branch of its own, and nothing merges until you accept it.
You choose what they see.
A posting is not an invitation into your codebase. You decide how much of it exists, as far as the developer is concerned, and the files are put together on our side and scanned for secrets before any of it leaves.
- ▹What they see — the issue text alone, or the files you name. Set per posting — a one-line fix does not need your codebase.
- ▹What the job is — a failing test, a feature behind a flag, a migration nobody has time for. Scoped small enough that a diff answers it.
- ▹What lands — their work arrives on its own branch, checked against the files you named, for you to read. Nothing merges until you accept it.
Where this is today.
Handing off a task, matching it to a developer, and returning a checked change all work now. Releasing payment on acceptance is the piece we are building next, so early postings are arranged directly with us. If you have work you would hand off, we want it to be one of the first.