UpgradePilot frequently asked questions

UpgradePilot is an open-source (Apache-2.0) multi-agent platform that upgrades ASP.NET Zero, ABP Framework, .NET, React and Next.js applications to newer framework versions while preserving your customizations. It analyzes the repository, merges template changes with Roslyn syntax trees, runs real builds and tests, and opens a pull request.

Yes. The open-source core is free forever under the Apache-2.0 license and runs locally through the CLI. You bring your own LLM API key and pay your LLM provider directly for what you use. UpgradePilot Cloud, the hosted multi-tenant plan for teams, is paid; pricing is custom, so contact us for a quote.

ASP.NET Zero, ABP Framework, plain .NET (NuGet packages, target frameworks, EF Core migrations), React, Next.js (Pages Router and App Router), and mixed repositories that combine a .NET backend with a React or Next.js frontend.

No. The Semantic Merge Engine only auto-propagates a template change when your code never touched that member. Anything you changed becomes an explicit conflict that is flagged in the pull request for a human to resolve. Nothing is silently overwritten.

It detects your current version, downloads the target version’s template, compares the template and your code using Roslyn syntax trees (not text diffs), runs a semantic three-way merge, applies package and API refactoring, checks database migrations, validates with a real build and test run, and opens a pull request with the conflicts called out.

It upgrades package.json dependencies and verifies them with a real npm install, applies the official react-codemod and @next/codemod transforms (chosen from each framework’s own release notes), then validates with npm run build and your Jest or Vitest suite. For Next.js it detects whether you use the Pages Router or the App Router.

In the self-hosted app, the pipeline and its SQLite session store run on your machine, and git and GitHub operations use your own credentials. Prompts are sent to the LLM provider whose API key you configure, so review that provider’s data policy. UpgradePilot Cloud runs the pipeline on hosted infrastructure.

No. It produces a pull request, a confidence score and explanation for each agent result, a list of flagged conflicts, and a rollback plan. A person still reviews and merges. Its job is to remove the repetitive merge-and-fix work, not the human sign-off.

Dependabot and Renovate open pull requests for dependency version bumps. Framework upgrades need more: merging template and code changes, running codemods, checking EF Core migrations, and validating the result. UpgradePilot covers those steps; you can still keep a dependency bot for day-to-day patch updates.

Hosted, multi-tenant infrastructure; team and organization management; scheduled and automated upgrades across many repositories; a dashboard to start, track and review sessions; metered LLM billing with no API key to manage; and priority support. Enterprise SSO/SAML, audit logs, usage analytics and additional Git connectors are on the roadmap.

GitHub today, through your own gh authentication in the open-source app. GitHub Enterprise, GitLab, Bitbucket and Azure DevOps connectors are on the Cloud roadmap.

Yes. A Rollback Planner agent produces a rollback plan for every upgrade, and because the result is delivered as a pull request, nothing reaches your main branch until you merge it.

It depends on how many versions you are behind, how much of the template you have customized, and how large the test suite is. Request a free upgrade assessment and we will tell you what to expect for your repository.

Clone the open-source repository from GitHub and follow the README. You need the .NET 10 SDK, plus Node.js if you are upgrading a React or Next.js frontend. If you would rather have a recommendation first, request a free upgrade assessment.

Yes. A real Model Context Protocol server (UpgradePilot.Core.Mcp) exposes repository, build and test tools that any MCP-compatible AI client can call.