Upstream fix · paid on merge
The issue that blocks you, merged upstream. You pay after the merge.
We take the open-source issue that blocks your team to a merged pull request: reproduction, a fix with tests in the project’s style, and the review rounds. $500 or $1,000, quoted before work and invoiced after the maintainer merges. Declined, or not merged within 45 days of opening the PR: no charge.
Opens an email to hello@cybernative.ai. Send the public issue link and what it blocks for you. We never need access to your systems or code.
Check our public record- Fixed price, quoted before work
- Invoiced after the merge
- No access to your systems or code
- 01You send the public issue link$0
- 02We quote a fixed price$0
- 03We reproduce, fix, test and open the PR The 45-day window starts$0
- 04Review rounds with the maintainer You install from our PR branch meanwhile$0
Maintainer merges
$500 or $1,000
Invoiced; due within 14 days
Declined, or not merged in 45 days
$0
No charge
Public record · check it on GitHub
Two public records you can open right now.
This is a new service. These are our two public examples of the work, on the projects’ own GitHub pages. Neither was a paid job.
-
openaddresses/openaddresses · PR #9999
Migrate five Socrata sources from SODA1 rows.csv to SODA3 query.csv
Merged by the maintainer, 10 Oct 2026
Our pull request. Five address sources were moving off a download API their publisher is retiring; the PR moves them to its replacement and states the project’s own test results before and after the change.
-
obsidianmd/obsidian-importer · issue #666
[Notion] Skipped notes still using requests?
Fixed in 3.1.13 with our test, adapted
We reproduced the bug as a failing test in the project’s test style and posted it on the issue. The maintainer’s fix adds it as linked-source.test.ts, “adapted from the issue comment”, and our test passes unchanged on 3.1.13.
We can’t promise that a maintainer will merge, and we make no claim about how long a merge takes. That risk is why you pay only after one.
Price · one fixed quote per issue
Two prices, quoted before we start.
We read the issue and the project, then quote one of these in writing. Nothing is due before the merge.
- Scoped
Fix or compatibility change
$500after merge
A scoped fix: a bug, a regression, or code that breaks against a new version of something it depends on.
- Larger
Feature or migration
$1,000after merge
A feature, or a migration to a new API or format, that we estimate at more than one engineering day.
Every job includes
- A reproduction of the issue.
- The fix, with tests written in the project’s own style.
- The review rounds with the maintainer, until the PR is merged or declined.
- AI-assistance disclosure in the PR wherever the project requires it.
- An install pin to our PR branch, so your team can use the fix until it is released.
Payment
- Invoiced after the maintainer merges; payable within 14 days.
- No charge if the maintainer declines the PR, or it is not merged within 45 days of opening it.
- No payment up front, and no card details on this site.
- Your written quote sets the terms for this job. Our site Terms cover two earlier $49 services, now closed to new work.
Fit · before you write
All we need is a public link.
The work happens in public, on the project’s own repository. Your systems and your code stay with you.
We need
- The link to the public issue.
- Your description: what it blocks for you, and what you do today instead.
We don’t
- Need access to your systems or code, ever.
- Guarantee that the maintainer will merge.
- Take security-vulnerability work.
- Take projects whose maintainers sell this development themselves.
Start with the issue link
Send the issue that blocks you.
Reply to our email, or write to us with the public issue link and what it blocks for you. We reply with a fixed quote, or tell you why we can’t take it.
Email us the issue linkOpens an email to hello@cybernative.ai. Links only: please don’t send private code, credentials or customer data.