Why people use UpgradePilot

Why people use UpgradePilot — and whether to choose the free app or Cloud

Quick answer. Use the free, self-hosted open-source app if you’re one developer or team upgrading a repo at a time and want full control. Choose UpgradePilot Cloud if you manage many repos, want scheduling, a shared dashboard and managed LLM billing, or need priority support. Both run the same agents.

Why teams use UpgradePilot at all

Customizations are safe

Template changes are only auto-applied where your code never touched the member; everything else is a flagged conflict.

It runs the real tools

Real dotnet, npm, git and codemod CLIs — versions and transforms are checked, not guessed.

You can see why

Each agent result has a confidence score, an explanation and citations.

No lock-in

Apache-2.0 open source. The free app and Cloud run the same agents.

It ends in a pull request

Normal code review, normal CI, plus a rollback plan.

It covers the whole stack

ASP.NET Zero, ABP, .NET, React, Next.js and mixed repos.

Which plan fits you?

The boundary is delivery mode, not capability — nothing is held back from the free tier.

Best fit: Free app

Solo developers & consultants

Upgrading a client’s or their own app now and then.

  • Free forever and fully featured — nothing is held back.
  • Bring your own LLM key and pay only for what you use.
  • Apache-2.0: read the code before you run it on someone else’s repo.
Best fit: Free app

Small product teams

One or two repos, a few engineers, upgrades a few times a year.

  • Run it in your own process, with local SQLite session storage.
  • Same agents Cloud uses.
  • Community support via GitHub Issues and Discussions.
Best fit: Free app

Security-conscious organizations

Policies that restrict where tooling runs.

  • Self-hosted: the pipeline and session store run on your machines.
  • You choose the LLM provider and credentials.
  • Auditable open-source code.
Best fit: Cloud

Agencies & software houses

Many client repos on different framework versions.

  • Upgrades scheduled and tracked across repositories.
  • Concurrent sessions rather than one run at a time.
  • Metered LLM billing — no per-client API key juggling.
Best fit: Cloud

Growing engineering orgs

Several teams, shared visibility, deadlines.

  • Multi-tenant organizations and roles.
  • A dashboard to start, track and review sessions.
  • Priority support. SSO/SAML, audit logs and extra Git connectors are on the roadmap.

See the detailed comparison table →

Start free, move to Cloud later

Because both plans run the same agents, there is no migration project: try the open-source CLI on one repo, and talk to us if you later want hosting, scheduling or team features.

Cloud’s enterprise SSO/SAML, audit logs, usage analytics and extra Git connectors (GitHub Enterprise, GitLab, Bitbucket, Azure DevOps) are on the roadmap, not shipped yet.

Read the open-core boundary for the precise split between open source and Cloud.

Want a second pair of eyes on your upgrade?

Tell us your stack and current version. We’ll reply with what’s involved and whether the free app or Cloud fits.