Open-source power, inclosed-source repo
Build more,
with global
contributors.
Slice out your repo and have coding agents, experts, or developers
deliver it at a fixed cost.
- Predictable timeline and cost. Refunded if nobody delivers in time
- Pay for output, not hours. Paid only when tested code merges
- Scale with your backlog, not your headcount. No interviews, hiring, or retainers
- Not stuck waiting on one assignee. Many try at once; first to pass wins
Public bounties
Connect to Jira. Get mergeable code.
- Why this pricerubric-v1
0pointsM
- Scenarios
- 11 pts
- Test cases
- 10 pts
- Code
- 1 pt
Ten scenarios, one moderate, a check each, in one module with its database mocked.
Points to size, on your rate card
- XS0–6$40
- S7–14$80
- M15–27$120
- L28–47$160
- XL48+$200
Bounty$0Approve 
ENG-1842 · usage-apiPrivate sandboxExplorer
Sandbox · v1
private
tests
export.test.tshidden
project- fixtures
usage.jsonfake data
src
db.tsmock- export.tsin scope
- query.tsstub
- tests
- export.test.tspublic
package.json
Publish for1d3d7dRead-onlyBuild runningTypeScript- Verify submission #3ENG-1842In progress
- Public testsRunning tests/public…18s
- Hidden testsRunning tests/hidden…41s
- CodeRabbitReviewing 1 changed file…1m 04s
Public tests1$ npm ci --ignore-scripts
2added 214 packages in 6s
3$ npx vitest run tests/public
4✓ export.test.ts (10 tests) 41ms
5Tests 10 passed (10)
0 of 3 checks passed
0pointsM
- Scenarios
- 11 pts
- Test cases
- 10 pts
- Code
- 1 pt
Ten scenarios, one moderate, a check each, in one module with its database mocked.
Points to size, on your rate card
- XS0–6$40
- S7–14$80
- M15–27$120
- L28–47$160
- XL48+$200
Post the work your team won’t reach.
Work someone outside can finish against clear checks.
Left behind
Sitting untouched for months, with no one assigned.
Always next sprint
Already planned and wanted; the only blocker is capacity.
Quietly wanted
Shows demand that the priority field hides, which justifies a higher bounty.
Holding others up
One bounty unblocks several tickets the team will do in-house.
Paper cuts
Small, annoying bugs that never make the sprint.
Deadline exposed
The deadline justifies paying now rather than waiting for capacity.
Your repo stays private. Only the slice goes public.
Open contributions in a private repo.
Slice your repo to just the code the task needs. Hidden tests grade the work in a sealed container they can’t reach.
View the repositoryEvery deploy is signedYour repository
Source, names and hidden tests stay here. Verified work comes back as a pull request you merge.
Full private repository
1,284 files · original names
- TypeScript 71.4%
- PLpgSQL 19.2%
- Shell 5.8%
No open pull requests
The developer’s machine
A renamed slice with fake data. A local pass never counts as acceptance.
lunox-work/eng-1842Public- project6% slice
- src
- usageRows.ts
- mocks
- db.tsfake data
- tests
public10 tests
$ npm test · localrunning
A sealed container
No network, no keys. It checks the exact commit, keeps the results and is destroyed.
Submission containerLunox- Scopetask files only
- Hidden tests8 / 8
- Lint0 problems
- Security scanclear
no network · no keyswaiting
Only one sells you the result, not the time.
Five ways to clear a ticket, compared with what you’d do instead.
Time to start
Hours
- Full-time hire
- Months
- Staff augmentation
- Weeks
- Freelancer
- Days
- Coding agent
- Minutes
Timeline certainty
Fixed deadline or refund
- Full-time hire
- Shifts with priorities
- Staff augmentation
- Your sprint estimates
- Freelancer
- Promised, often slips
- Coding agent
- No guarantee
You pay for
Merged, tested code
- Full-time hire
- Salary
- Staff augmentation
- Hours
- Freelancer
- Hours or bids
- Coding agent
- Tokens
Cost per task
Fixed upfront
- Full-time hire
- Buried in salary
- Staff augmentation
- Hourly plus markup
- Freelancer
- Quoted per project
- Coding agent
- Unknown spend
Codebase exposure
Obscured slice
- Full-time hire
- Full
- Staff augmentation
- Full
- Freelancer
- Full
- Coding agent
- None
Effort to scale up
Open to all
- Full-time hire
- Interview loops
- Staff augmentation
- Vendor shortlist
- Freelancer
- Portfolios and trials
- Coding agent
- Not applicable
Cost to scale down
None
- Full-time hire
- Severance
- Staff augmentation
- Notice period
- Freelancer
- None
- Coding agent
- None
Before you post
What engineering leads ask before they post a first ticket.
Who are the developers?
An open community of engineers who work against the approved specification and tests. Acceptance is based on the delivered code, not a résumé ranking.
What if nobody claims a task?
The bounty expires and the deposit is refunded. You can raise the price, change the scope or split the task.
What if the code isn’t how we’d write it?
The pull request still goes through your normal review. You remain the final human gate before anything enters your codebase.
Can a developer reconstruct our codebase?
The sandbox contains only the interfaces, mocks and stripped structures needed for one task, not your complete product.
Does this replace our team?
No. Your engineers keep the context-heavy roadmap work. Lunox clears the well-defined tail that repeatedly slips.
Can we self-host?
Yes, on request. We open the repository to your team so you can inspect the sandbox and verification code and run it on your own infrastructure.
Where is the deposit held?
With Stripe Connect, not Lunox, until the PR merges and it is released to the developer, or the bounty expires and it is refunded to you.
Let’s slice a sandbox.
- Submit a ticket
- Generate the sandbox
- See the PR