What DryRunPro does
Adobe Commerce Cloud (the enterprise SaaS edition of Magento, also known as Magento Cloud) ships with three environment tiers per project: integration, staging, and production. That is fine when you have one project and one feature in flight. The moment you have ten enterprise customers each running their own Adobe Commerce Cloud project, with several feature branches per project queued for QA at the same time, the three-environment ceiling becomes a bottleneck. Engineers wait. Code rots in branches. Releases ship blind. DryRunPro removes the bottleneck by giving every Adobe Commerce Cloud project an on-demand dryrun fleet. A dryrun is a fully composed, fully cached, Fastly-fronted clone of the production topology, spun up against any branch you point it at, with a full Docker stack underneath (PHP-FPM, MySQL, Redis, OpenSearch, RabbitMQ). It runs SWAT reports, Magento extension audits, code audits, and bin/sync against the canonical environment. When you are done, you tear it down with one click. Because everything sits inside one DryRunPro tenancy, one user account manages many Adobe Commerce Cloud projects at once. That is the foundational design decision that distinguishes DryRunPro from a per-project CI/CD plugin or from Adobe’s own Cloud CLI.Who DryRunPro is for
- Enterprise Adobe Commerce Cloud merchants running one or more Magento Cloud projects who want a fast, repeatable staging surface that does not collide with the integration environment.
- Adobe solution partners and Magento agencies who manage Adobe Commerce Cloud projects on behalf of multiple enterprise customers and need one console with per-customer team segregation.
- In-house Magento engineering teams that ship across several feature branches in parallel and need more dryrun environments than the three-tier Adobe ceiling allows.
- QA leads and release managers who need a SWAT report, a code audit, and a bin/sync run against a candidate branch before signing off a production deploy.
- Migration teams moving from Magento on-prem to Adobe Commerce Cloud, where dryruns let them rehearse a full production cutover without touching the live Cloud project.
The multi-project architecture
A normal staging tool assumes one tenant equals one storefront. DryRunPro assumes one tenant equals many Adobe Commerce Cloud projects. The screenshot of the Projects tab in a real DryRunPro tenancy shows eleven distinct enterprise merchants in one console: Ulster Weavers Ltd, Xupes Limited, Bahrain Duty Free Company WLL (Dublin), Soak and Sleep, Independent Buying Consortium, Eggfree Cake Box Limited Azure, Eggfree Cake Box Ambala, Boutinot Ltd, Blitz Corporation Ltd, Bahrain Duty Free Company W.L.L., and Krispy Kreme UK and Ireland. Each is a separately provisioned Adobe Commerce Cloud project with its own credentials, its own environments, and its own DryRun Pro fleet, and the same engineering team operates all of them from one login. Each project card on the Projects tab shows two columns of metadata side by side. On the left, the Adobe Commerce Cloud column reports the live cloud topology (Environments, Storage in MB, Users). On the right, the DryRun Pro column reports the DryRunPro overlay (Staging, Packages, Users). At the bottom of the card sits the Team assignment dropdown (“Cakebox”, “Blitz”, “BDFC”, or no team), then a red Delete Project button on the left and a blue View Details link on the right. The team assignment is what keeps the multi-project model from becoming chaos. A team is a group of users that gets assigned to one or more projects collectively, instead of you having to grant per-user access on every project. See Teams for the full model.The seven top-tabs
DryRunPro’s left-rail navigation has seven primary tabs plus a sub-grouped Settings menu. They are, top to bottom:| Tab | Purpose |
|---|---|
| Projects | The full list of Adobe Commerce Cloud projects this account manages, with per-project DryRun Pro stats. |
| Dryrun Environments | The list of every dryrun environment currently spun up across every project, with status, duration, and SWAT report links. |
| Docker packages | Staging package downloads (Docker snapshots and Warden packages) sourced from completed DRP staging jobs. |
| Create your own | The launcher for spinning up a new dryrun environment. Documented in Dryrun Environments. |
| User management (sub-menu) | Roles, Project Users, Permissions, Teams, and Audit Logs. |
| Settings (sub-menu) | Adobe Commerce Cloud connection setup and CDN configuration. |
| User Alerts | Per-user notification settings for staging job completion, SWAT report ready, and project events. |
Position vs other staging tools
The staging space has three classes of tool that each solve a slice of the problem. DryRunPro is the only one that solves all three at once for Adobe Commerce Cloud merchants. Adobe Cloud CLI and Cloud Manager. Adobe ships a command-line interface (magento-cloud) and a web console (Cloud Manager) for provisioning environments inside one project. They are excellent for the three-tier integration / staging / production flow. They do not give you on-demand dryrun fleets, they do not give you a multi-project console, they do not give you team-based access, and they do not run SWAT reports or code audits as part of the workflow.
Magento staging frameworks (Warden, Docker Magento, n98-magerun snapshots). Local Docker stacks let an engineer spin up a Magento environment on a laptop. They do not produce a Fastly-fronted public URL, they do not run against Adobe Commerce Cloud topology, and they do not coordinate work across a team of engineers. DryRunPro can produce a Warden package as a deliverable for laptop-side debugging, but the dryrun itself runs in the cloud, accessible by a URL anyone on the team can hit.
StagingPro (BigCommerce) and Vortex Staging (Shopify). These are the sister Vortex Apps for the SaaS storefront platforms. They solve the same problem class (preview a change before production) but the underlying architecture is different. BigCommerce and Shopify do not expose Docker, do not expose code-level Magento extensions, and do not have an Adobe Commerce Cloud-style multi-environment topology. So the UI is different and the lifecycle is different. Cross-link StagingPro and Vortex Staging for those platforms.
DryRunPro stitches the multi-project console, the on-demand fleet, the SWAT report, the code audit, the Docker snapshot, the Warden package, and the team-assignment model into one unified surface for Adobe Commerce Cloud. That combination is what the other tools do not offer.
Pages in this section
| Page | What it covers |
|---|---|
| Projects | The Projects tab, per-project cards, search, the Adobe Commerce Cloud + DryRun Pro split. |
| Project Overview | The per-project detail page, environments, storage, users, recent staging activity, snapshots. |
| Add Adobe Commerce Cloud Project | The five-step add-project wizard with credentials, OAuth, project ID. |
| Delete Project | The teardown workflow, what is destroyed, what is preserved. |
| Dryrun Environments | The list of all dryrun environments, lifecycle states, the upgrade-to-Adobe-commerce flow. |
| Staging Detail | The per-environment detail page, SSH access, SWAT report, container control, CDN mode. |
| Docker Packages | Staging package downloads (Docker snapshot + Warden package). |
| Roles | The four roles (Admin, Team Leader, Developer, Tester) and what each can do. |
| Project Users | Inviting users, assigning roles, project-scoped users vs platform-scoped users. |
| Permissions | The 38-permission grid, granular control over each module. |
| Teams | The team model, creating organizations, assigning teams to projects (Cakebox, Blitz, BDFC). |
| Settings, CDN | Fastly and Cloudflare configuration, edge DNS automation, CDN mode override. |
How DryRunPro connects to the rest of the AI OS
DryRunPro is one Vortex App. It does not stand alone. It is wired into the rest of the AI OS so that the staging surface is informed by, and informs, every other module:- The Adobe Commerce connector on Nerve Centre surfaces the same Cloud project that DryRunPro stages. KPIs you see on Nerve Centre (sales, conversion, page-load, error rate) are the production baseline against which a dryrun is compared.
- Vortex Mind reports such as Daily Revenue Leakage and Checkout Conversion Failure run against the production Adobe Commerce data. When Vortex Mind flags a regression, DryRunPro is where you reproduce the fix safely.
- Ask Viq can answer “which dryrun is currently green for project X?” and “which staging environment was used for the 4.2.0 release?” by reading DryRunPro state.
- Actions tied to Magento extension issues, code audit findings, or storefront regressions can route into a DryRunPro dryrun for verification before they ship.