Move forward. Preserve what matters.
Portwell turns a vendor API retirement into a reviewed change for your repository, with the evidence your reviewers need: where you are exposed, a focused patch, what was checked, and what still needs a human.
Get a free exposure assessment
Nothing merges or deploys without your approval.
charges.create is retired on 1 January 2030. Use payments.create.↓ Found in your repository at commit b5a0bb0
- PASSED 4 OF 4 CHECKS
- NOT CHECKED: 6 BEHAVIOURS
- NEEDS YOU: 1 APPROVAL
The notice tells you the deadline. It does not tell you about your code.
A retirement notice says what will stop working and when. Someone on your team still has to find every place your application uses it, work out what behaviour must change, make the change, and decide how much proof is enough to ship. That work lands on a senior engineer, usually close to the deadline.
A review-ready migration, not another alert.
Exposure, with sources.
Every candidate call site in a pinned snapshot of your repository, linked to the line of code and the vendor notice. A candidate is not confirmed impact, and we label it that way.
A focused patch.
A proposed change that touches what the migration needs and leaves the rest of your code alone.
Evidence you can check.
The checks we ran, on which commit, in which environment, and the result of each: passed, failed, skipped or unverified.
The gaps, in writing.
What we did not or could not check, and the manual steps that remain. “No configured match found” never becomes “no impact”.
How it works
Free exposure assessment.
We inspect a commit you name, read-only, and show you where the retirement touches your code.
Agree the scope.
If the migration is worth doing, we write the acceptance specification together and quote it in writing.
We propose and verify.
Your baseline and the proposed change run against the same checks. A check that already fails on your baseline is reported as a baseline failure.
You review and decide.
A pull request is opened only after you approve it, and any change after approval needs approval again.
Supported today
[Vendor], [API change], [language and framework], [starting version] to [target version].
We support one migration type in depth before we add the next. If yours is not listed, tell us about it.
What we do not do
- We do not merge or deploy for you.
- We do not promise defect-free software. You get evidence and its limits, stated plainly.
- We are not a general coding assistant or a dependency-update bot.
Get a free exposure assessment
Leave a work email. We reply within [two working days] to agree a repository and a commit, and then send you the exposure report. If the migration is worth doing, we quote it in writing before any paid work starts.
Questions
Do you need write access to our repository?
Not to inspect. We work from a read-only snapshot at a commit you choose. Opening a pull request needs your explicit approval, tied to that exact change. [Security and access detail: to be written with Theo2]
What happens to our code?
[Retention, deletion and data-region terms: from the pilot SOW]
What if your checks pass and something still breaks?
A passed check means that check passed, on that commit, in that environment. We list what was not checked so your team can decide what else it needs.
What does the migration cost?
The assessment is free. A migration is quoted in writing for your scope before work starts. [Pricing: Tate's decision]