Your upgrade backlog, gone.
Under $5 a fix.

TypeScript, JavaScript, Python, Go, Java and Kotlin repositories (npm, pnpm, yarn, bun, pip, uv, poetry, Go modules, Maven and Gradle), on GitHub or GitLab. Ruby, C#, PHP, Rust and Swift are next, and Bitbucket. Email us the language you need: the most requested ships first.

Versyka runs every check your repository defines: typecheck, build, and tests. The pull request lists which checks passed, and if there are none it clearly says the change is unverified, so reviewers know what was proven.

Yes. For connected repositories, a daily scan flags API SDKs that are major versions behind or deprecated, with links to the release notes. Starting a migration from an alert fetches the vendor's notes automatically.

Those tools bump version numbers. When a new version has breaking changes, the upgrade PR fails and someone still has to rewrite the code. Versyka does both: version bumps (several in one pull request) and the rewrite when an upgrade breaks your code, proven with your tests run before and after.

Yes. The daily scan checks your dependencies against known vulnerabilities (OSV.dev) and groups them into the upgrades that fix them. They show up as package upgrades in your dashboard: tick the ones you want and review them first. Version bumps go into one pull request per repository and use the plan's version-bump allowance (20 a month on Free, 100 on Starter, 500 on Team, 2,000 on Scale), not your migration pull requests; a breaking upgrade also updates your code and uses one of your monthly migration pull requests. Each one lists the advisories behind it.

Anthropic's Claude writes migration rules and code edits. Deterministic structural search (ast-grep), not the model, decides which files are touched.

Never to your default branch. Versyka opens a pull request on a separate branch, and nothing merges without your team's review.

Through our GitHub app: repository contents, pull requests, and metadata, only on the repositories you choose, plus read-only access to your email address when you sign in to the dashboard. Access tokens expire after about an hour, and you can uninstall the app at any time.

No. Your code is cloned into a disposable sandbox for each job and destroyed when the job ends. We keep metadata such as file paths, line numbers, status, and PR links.

No. It reads only package names and versions, looks them up on the public npm registry or PyPI, and stores nothing. A share link carries the file inside the link itself, so it is never sent to or stored by us.

After a check, you can ask for an email when those API SDKs get a new major version or are deprecated. Nothing is sent until you confirm from the first email. We store only your email and the package names and versions, and every alert has a link that stops alerts and deletes both. Unconfirmed requests are deleted after 7 days.

Design partners use Versyka free during the pilot. After it, plans are priced by migration pull requests a month: Free includes 2, Starter 10 for $49 a month, Team 60 for $249, Scale 200 for $749, and API provider plans start at $1,500 a month. Billed yearly, Starter, Team and Scale are $39, $199 and $599 a month. Anyone who subscribes in the first 6 months keeps their price.

Your plan covers up to 5, 25, 100 or 500 repositories at a time; you choose which ones in your dashboard. Most teams never reach the limit, because plans are priced by pull requests, not repositories. If you give the GitHub app access to more, nothing extra is charged: the others stay connected but aren't scanned or migrated. When you first connect, the most recently active repositories fill your plan, so it's worth choosing carefully.

Yes, anytime, in your dashboard: unselect one and select another, up to your plan's limit. Migrations only run on repositories covered at the time.

Every plan has the whole product: tested pull requests for outdated SDKs, vulnerable packages and retiring AI models, a daily scan, email and Slack alerts, a weekly summary and pull request commands. Starter is for you and 2 teammates. Team adds your whole team with no seat fees, Autopilot for version bumps, automatic rebuilds when a pull request gets conflicts, and a pull request schedule. Scale adds custom migrations for your own internal libraries, staged rollouts across many repositories, a shared Slack channel with our engineers, and invoices and security reviews. Bigger plans also cover more repositories and pull requests, at a lower price per pull request.

Each plan includes a number of migration pull requests per calendar month (2, 10, 60 or 200), counted across all your repositories and reset on the 1st (UTC). Migrations that don't open a pull request don't count, Package version bumps (upgrades with no code changes) have their own, larger allowance: 20, 100, 500 or 2,000 a month. A package upgrade that needs code changes counts as one migration pull request. When they're used up, finished migrations wait; we email you, and you can wait for the 1st, upgrade, or ask for extra pull requests at $5 each. We never open or charge for extra ones without your agreement.

Change plans from the pricing page or your dashboard; Stripe shows the prorated amount before you confirm. Upgrades apply immediately. Cancelling keeps your plan until the end of the period you paid for, then your account moves to Free. Nothing is deleted, and you get an email for every change.