Start your first ticket

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

Start with one ticketSee how it works
  • 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

Connect to Jira

and get mergeable code

  1. 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

    1. XS0–6$40
    2. S7–14$80
    3. M15–27$120
    4. L28–47$160
    5. XL48+$200
    Bounty$0Approve
  2. ENG-1842 · usage-apiPrivate sandbox

    Explorer

    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 for1d3d7d
    Read-onlyBuild runningTypeScript
  3. Verify submission #3ENG-1842In progress
    1. Public tests18s
    2. Hidden tests41s
    3. CodeRabbit1m 04s
    0 of 3 checks passed

What makes a good bounty?

Work your team won't reach soon, but 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.

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 repository

Your repository

Source, names and hidden tests stay here. Verified work comes back as a pull request you merge.

acme/usage-apiPrivate
CodePull requestsActions
main

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
  1. Scopetask files only
  2. Hidden tests8 / 8
  3. Lint0 problems
  4. Security scanclear

no network · no keyswaiting

Compared with what you’d do instead

Five ways to clear a ticket. Only one sells you the result, not the time.

  • 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

Questions worth asking

What engineering leads ask before they post a first ticket.

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.

Let’s slice a sandbox

  1. Submit a ticket
  2. Generate the sandbox
  3. See the PR
Start with one ticketTalk to an engineer