Upgrade Radar · for Shopware 6 agencies — by Apeirion Labs
Know which plugins break a Shopware update — before you run it.
Upgrade Radar reads a shop's composer.lock and custom/plugins and tells you, per plugin, whether it will conflict with the target Shopware version — from declared constraints, with the excluding constraint quoted. No composer run, no vendor tree, no shop access. Run it over every client shop when you plan update windows.
Run it on your own shop right here — no install, nothing stored. The full tool, its CLI and price, live on the product page.
Upgrade Radar is live now — see the tool and the €9 price. The hosted check above stays free for anyone; this box is only for word on new checks we add. Email stored only to contact you about that — privacy.
New here? Read what Upgrade Radar is, who it's for and how it compares — a plain page, no marketing.
Why this doesn't exist yet
Today's tools act after the damage: rollback managers restore, monitors alert. The pre-update conflict check is an open Shopware feature request. Upgrade Radar is that check, built for fleet-wide use.
Honest scope
- Upgrade Radar evaluates declared constraints (a 15-rule composer-semantics engine, covered by a 38-case truth table).
composer update --dry-runremains the definitive gate at update time — Upgrade Radar is what you run over every client shop before booking windows. - UNKNOWN is reported as UNKNOWN. No guessing, no green-washing your fleet report.
- One run reads 1 shop. A whole fleet is a loop over shop directories, and the install guide ships the loop — there is no aggregated fleet roll-up, and we do not sell one.
- Shipped today: the release-availability lookup that says whether a target-compatible release exists for each conflict. Not built: an aggregated fleet roll-up and a sandboxed dry-run executor. No dates are promised.