Who you're trusting with your code

Why Unstale exists

Most teams don't skip upgrades because they're lazy. They skip them because nobody can say how long the work will take, what will break, or what it will cost. So the app stays on PHP 8.1 or Django 4.2 until a security audit, a hosting provider or a flaw like PHP2Shell forces the issue.

I started Unstale to take that uncertainty away: a report of what breaks and a fixed price before you pay anything, then a pull request that passes your own tests, or your money back.

How the work is done

The code changes are AI-assisted, and we say so up front. AI makes the work fast enough to sell at a fixed price. It doesn't replace the checks, so every upgrade goes through three of them:

• Your test suite and build. The pull request has to pass them, or you get a full refund.
• A review for what tests can't see. Settings the new version silently ignores, removed internals and changed defaults. In our seven trial upgrades, this review found the most serious problem in five of them.
• Your team's review. Nothing reaches your main branch until you merge it. Reject it within 14 days for any reason and you pay nothing.

Decisions only you can make, such as raising a minimum language version or moving an add-on up a major version, are listed in your free scan report before you pay.

What we can and can't access

Only your repository, through our GitHub account @unstale-bot: read access for the scan, write access to open the pull request. Never production servers, passwords or secrets. Remove our access as soon as you've merged. How we handle your code is set out in our privacy policy.

Work you can check

• Node-RED. Express 5 support, submitted after the maintainers asked for it: pull request #6024, open for review.
• Seven open-source trial upgrades. Django, Laravel and Express apps, with test counts before and after and what review caught: case studies.
• Free upgrade guides. PHP, Laravel, Python and Django, each with a checklist: upgrade guides.