> ## Documentation Index
> Fetch the complete documentation index at: https://docs.vortexiq.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# DryRunPro, Adobe Commerce Cloud Multi-Project Staging Launcher

> DryRunPro is the multi-project Adobe Commerce Cloud staging launcher inside Vortex Apps. Spin up dryrun environments for any Magento Cloud project, manage Docker packages, assign teams, and launch tested code into production with confidence.

DryRunPro is the **Adobe Commerce Cloud staging launcher** inside [Vortex Apps](/vortex-apps/overview). One DryRunPro account holds many Adobe Commerce Cloud projects (one per merchant Magento environment) and gives every project a clean, isolated, on-demand dryrun staging surface that mirrors the production Magento topology. You spin a dryrun, you push a branch into it, you run smoke tests and a SWAT report, you merge with confidence. When the dryrun has done its job, you tear it down and the resources go back to the pool.

Live URL: [app.vortexiq.ai/v2/apps/dryrunpro](https://app.vortexiq.ai/v2/apps/dryrunpro/project)

This page is the section landing. It explains what DryRunPro is, who it is for, the multi-project architecture that distinguishes it from one-project staging tools, the seven top-tabs that make up the navigation, and the team-assignment model that keeps multi-customer agencies tidy.

## 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

1. **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.
2. **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.
3. **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.
4. **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.
5. **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.

If you only have a single Shopify store, DryRunPro is not the right Vortex App for you. The right pair for Shopify is [Vortex Staging](/vortex-apps/vortex-staging) plus [Vortex Backup](/vortex-apps/vortex-backup). For BigCommerce it is [StagingPro](/vortex-apps/staging-pro) plus [RollbackPro](/vortex-apps/rollback-pro). DryRunPro is purpose-built for the Adobe Commerce Cloud reality: many projects, many branches, many teams, all running in parallel.

## 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](/vortex-apps/dryrunpro/projects) 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](/vortex-apps/dryrunpro/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](/vortex-apps/dryrunpro/projects)           | The full list of Adobe Commerce Cloud projects this account manages, with per-project DryRun Pro stats.                                                                                         |
| [Dryrun Environments](/vortex-apps/dryrunpro/staging) | The list of every dryrun environment currently spun up across every project, with status, duration, and SWAT report links.                                                                      |
| [Docker packages](/vortex-apps/dryrunpro/docker)      | 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](/vortex-apps/dryrunpro/staging).                                                                     |
| User management (sub-menu)                            | [Roles](/vortex-apps/dryrunpro/roles), [Project Users](/vortex-apps/dryrunpro/users), [Permissions](/vortex-apps/dryrunpro/permissions), [Teams](/vortex-apps/dryrunpro/teams), and Audit Logs. |
| Settings (sub-menu)                                   | [Adobe Commerce Cloud](/vortex-apps/dryrunpro/projects/add-adobe-commerce-cloud-project) connection setup and [CDN](/vortex-apps/dryrunpro/settings/cdn) configuration.                         |
| User Alerts                                           | Per-user notification settings for staging job completion, SWAT report ready, and project events.                                                                                               |

A *Change password* link and a *Logout* link sit beneath the seven tabs.

The "Create your own" tab is worth calling out. It is the spin-up launcher that turns "I need a dryrun" into a running environment in the few minutes it takes for the Adobe Commerce Cloud build pipeline to finish. We document it as part of the [Dryrun Environments](/vortex-apps/dryrunpro/staging) section because the lifecycle starts there.

## 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](/vortex-apps/staging-pro) and [Vortex Staging](/vortex-apps/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](/vortex-apps/dryrunpro/projects)                                                          | The Projects tab, per-project cards, search, the Adobe Commerce Cloud + DryRun Pro split.      |
| [Project Overview](/vortex-apps/dryrunpro/projects/project-overview)                                 | The per-project detail page, environments, storage, users, recent staging activity, snapshots. |
| [Add Adobe Commerce Cloud Project](/vortex-apps/dryrunpro/projects/add-adobe-commerce-cloud-project) | The five-step add-project wizard with credentials, OAuth, project ID.                          |
| [Delete Project](/vortex-apps/dryrunpro/projects/delete-project)                                     | The teardown workflow, what is destroyed, what is preserved.                                   |
| [Dryrun Environments](/vortex-apps/dryrunpro/staging)                                                | The list of all dryrun environments, lifecycle states, the upgrade-to-Adobe-commerce flow.     |
| [Staging Detail](/vortex-apps/dryrunpro/staging/staging-detail)                                      | The per-environment detail page, SSH access, SWAT report, container control, CDN mode.         |
| [Docker Packages](/vortex-apps/dryrunpro/docker)                                                     | Staging package downloads (Docker snapshot + Warden package).                                  |
| [Roles](/vortex-apps/dryrunpro/roles)                                                                | The four roles (Admin, Team Leader, Developer, Tester) and what each can do.                   |
| [Project Users](/vortex-apps/dryrunpro/users)                                                        | Inviting users, assigning roles, project-scoped users vs platform-scoped users.                |
| [Permissions](/vortex-apps/dryrunpro/permissions)                                                    | The 38-permission grid, granular control over each module.                                     |
| [Teams](/vortex-apps/dryrunpro/teams)                                                                | The team model, creating organizations, assigning teams to projects (Cakebox, Blitz, BDFC).    |
| [Settings, CDN](/vortex-apps/dryrunpro/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](/integrations/connector-catalogue) 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](/vortex-mind/overview) 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](/ask-viq/overview) 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](/actions/overview) tied to Magento extension issues, code audit findings, or storefront regressions can route into a DryRunPro dryrun for verification before they ship.

## Frequently asked questions

**Is DryRunPro the same as Adobe Cloud Manager?**
No. Adobe Cloud Manager provisions and manages the three-tier integration / staging / production environment ladder for one Adobe Commerce Cloud project. DryRunPro is a multi-project dryrun fleet that overlays Adobe Commerce Cloud and gives you on-demand additional environments per project, with team-based access across many projects.

**Do I need an Adobe Commerce Cloud subscription to use DryRunPro?**
Yes. DryRunPro is the staging surface for Adobe Commerce Cloud. It does not work against Magento Open Source, on-premise Adobe Commerce, or Magento Commerce hosted elsewhere. You need at least one provisioned Adobe Commerce Cloud project with super-admin credentials.

**Can I run DryRunPro against multiple Adobe Commerce Cloud projects at once?**
Yes. That is the entire point of the multi-project model. The Projects tab routinely shows ten or more Adobe Commerce Cloud projects in one tenancy. Each project keeps its own environments, storage, users, and DryRun Pro fleet.

**How are users assigned to projects?**
Through the [Teams](/vortex-apps/dryrunpro/teams) model. You create teams (organizations) like "Cakebox", "Blitz", or "BDFC", you add users to those teams, and you assign teams to projects on the project card. A user's effective access to a project is the union of the teams they belong to and any direct project assignments.

**What happens when I delete a project from DryRunPro?**
DryRunPro disconnects from the Adobe Commerce Cloud project, terminates any running dryrun environments for it, and removes the project from your console. The Adobe Commerce Cloud project itself is untouched, the deletion is purely the DryRunPro overlay. See [Delete Project](/vortex-apps/dryrunpro/projects/delete-project).

**Where do staging packages live?**
Each completed dryrun produces downloadable artefacts: a Docker snapshot (the full container set as a tarball) and a Warden package (the local development bundle). Both are listed on the [Docker packages](/vortex-apps/dryrunpro/docker) tab and remain available for download until the dryrun is torn down.